Zugg Software :: View topic - My thoughts/complaints concerning Cmud as a player and long time user/tester.

Wizard Joined: 17 Jun 2006 Posts: 1201

Firstly, I really enjoy Cmud. I have, over the course of time, gotten a lot of other people to use it as well. However, I am going to list some of the complaints I have and the complaints I hear.

My number one and biggest complaint is trying to use the mapper. In fact this is the largest complaint I hear from other people as well. I don't want to sound rude, but I thought all these changes and stuff were to get the mapper working better. It seems like that just got thrown on the back burner somehow? I know there are reasons for adding JSON and such. However, every mud I try to use it on I have nothing but problems either trying to extract the room data because the mud is not sending it or Cmud is not handling it or something. See my Midkemia post that only one person even responded to so far.

Secondly, it is almost impossible to use the built in walk commands because these muds implement restrictions on how fast you can walk. YET there is NO place in Cmud that you can add a delay between each walk that I can find. Even in slow walk mode it walks too fast. Therefore, you have to end up creating an entire script just to do what the internal commands already do! This makes no sense at all and is very frustrating to myself and most of the people that talk to me. They just give up trying to use it because their walk is always aborted after walking a few rooms. It seems to me this entire problem would be solved by simply including somewhere a delay timer for slow walking.

I actually asked someone in the game earlier about the speed walking problem. Their response was oh well I use Mudlet and I just set the delay in Mudlet for walking. I can't believe Mudlet is even able to compete with Cmud already. Now I know all of the people involved with it, and going back to the complaints I hear, their usual complaint is they couldn't use the mapper that was available from the guy involved with Mudlet with Cmud.

I realize that with the new GMCP protocol the mapping will be much easier, but some of the IRE Muds don't even use it yet. In fact the mud I am playing now, Midkemia, doesn't even send the ATCP room info and if it does, then Cmud is perhaps stripping it before I can view it in the debugger? Because I sure don't see it.

Other than this I really have no problems other than the bugs that have been created by adding JSON. In fact I use the beta to help test and play at the same time and really have no problems at all. Most complaints people make to me are usually because they messed up their scripts. Yet when it comes to the mapper even I don't understand why I can't even walk 5 rooms without screwing it all up. Granted I am myself not used to using it because I have always just went by memory. However, BECAUSE I am relatively new to using it I thought I would provide my opinion on it and where I am having problems.

Wizard Joined: 17 Jun 2006 Posts: 1201

Example of the slow walk problem:

Wizard Joined: 22 Mar 2007 Posts: 2320

So in this mud, you cannot even type the next direction even after arriving in a room? Odd. I've never seen another mud do that. How long do you have to wait? In your previous messages about having problems with slowwalk, you did not make that clear. Or, at least, it was not clear to me.

[edit] And does this time restriction apply to other commands?

Posted: Wed Jul 14, 2010 5:40 pm

Apprentice Joined: 15 Jun 2010 Posts: 121

For your second problem: I don't know if this applies to your mud, but this is what I do with Achaea, setup a variable called wdelay and tune it to how much you want to spam the commands after getting a too hasty message (I use 0.2). Also set your slow walking abort timeout in the settings to very high (like 20 seconds):

Wizard Joined: 17 Jun 2006 Posts: 1201

@dbosst there is just one problem. That does not work. It didn't work in Achaea and doesn't work in Midkemia. I did the same thing and after the delay when it entered #step it would only send 1 direction and never finish walking the path. I've never been able to get something like that to work. Also with Midkemia they don't have GMCP yet apparently and I'm not seeing ATCP room info either.

Apprentice Joined: 15 Jun 2010 Posts: 121

Hmm I think I mentioned this bug in another post about the mapper, but I don't remember:

when you double click on a room, it does not setup a slow walk correctly, because I never have problems with #SLOW but I tend to have problems with double clicking on a room, the reason for this is #nodir or #nomap do not work when you double click on a room, but they do work perfectly if you use #slow ...

Also right now in Achaea, there is a small mxp bug I believe, it worked at one time perfectly but now it doesn't seem to load mxp settings for the player for me at start (so I have to send config mxp off, and then on to force it to send mxp)

I imported only my mapper stuff from a brand new session and package, and made sure it worked fine and tested it after setting these settings:

map preferences
configuration
disable roomname,description,roomexits
mudprompt, uncheck everything

speedwalking: slow, disable automatic confirmation

main options
mxp> force remote mxp
session->emulation->disable ATCP
make sure GMCP and MXP is enabled

my colour scheme in Achaea (need it for picking up room_desc at least):
config colour Room_Title 15 6
config colour Room_Desc 11 6
config colour Things 6 0
config colour Plants 14 6
config colour Players 14 0
config colour Exits 10 0

The room description parsing is for 0 screenwidth, since that's the simplest

Here is the xml file for the whole package:

http://www.mediafire.com/?4nnj1zbmgziqln1

I generally use the "wz" or "wr" aliases to walk to a zone or a room key, then if I get lost or something I use "tc" alias to try to set me to the right room

If you have a good map you generally have short room names for most of your places,.. so you can just do wr shallamherbs to goto your favorite shallam herb shop or something, this pretty much makes double clicking on the map mostly useless (although it would be nice if it got fixed eventually)