Zugg Software :: View topic - CMUD mapper

Wanderer Joined: 23 Apr 2005 Posts: 57

Okay, the problem I'm having is that #LOOK simply isn't working for me - that's to say it sends the 'look' command to the MUD, but fails to load the resultant information (room name, room description etc) into the mapper. I'm confident I've got the mapper itself configured correctly, and indeed it's working perfectly when I'm just walking from room to room, so I was wondering whether this was a known problem, something that's unique to me, or whether the #LOOK command itself had become depreciated in CMUD? Thanks.

Wizard Joined: 11 Jul 2002 Posts: 1265 Location: USA

In my experience the configuration between walking from room to room and typing the look command in some MUDS is different enough that C/ZMUD has problems.

To that end perhaps if you tell us what mud you are playing and or give us some text of you walking into a room, and of you typing look in the room maybe we can help.

Personally I don't use #look at all as I've written a script to find my location based on a glance command.
There are other scripts for finding yourself on a map posted here and there as well.

Vijilante's ToolBox in the package library has some stuff for finding yourself on the map. I've not played with it in a while. Mostly because I already have my own system.
But I suggest you try to use his package and request help back here for problems you have along the way.

Wanderer Joined: 23 Apr 2005 Posts: 57

Well that's the thing - it's one of the Iron Realms MUDs, Lusternia, and the description seen upon using the #LOOK command is exactly the same as that seen when walking from room to room; please bear in mind though that I'm referring specifically to #LOOK, which reloads information for the current room, rather than #FIND, which attempts to locate your position on the map.

I really do think this is a glitch rather than a configuration issue though... I know of course it's easy to say that, but from reading the forums I believe I'm right in saying that the mapper in CMUD is pretty much identical to that in zMUD; I've configured them both identically (literally gone through setting by setting to make sure they're the same), and it's working fine in one and not in the other.

Wizard Joined: 11 Jul 2002 Posts: 1265 Location: USA

Right, my bad. There could still be a difference though.

Also, if you are playing a mud with ATCP *think I have the letters in correct order* Lusternia being one that has it.
The mapper tries to automatically configure itself to use ATCP.
That IS a difference from the original Zmud mapper as it doesn't have that feature.

You may have a look at the raw output using #debugfile and see if they are really the same.

Wanderer Joined: 23 Apr 2005 Posts: 57

Well I disabled ATCP specifically because it precludes the actual room description (capturing instead only the room-name and exits), and I tend to find the description itself very useful.

What I have noticed is that although #LOOK enables the 'Reload Room Name', 'Reload Room Description' and 'Reload Room Exits' options within a room's properties, none of these are actually getting reloaded - neither during the sending of the look command nor upon walking out of and back into the room. It's as if the mapper simply isn't aware that it's meant to be reloading that information.

Wizard Joined: 11 Jul 2002 Posts: 1265 Location: USA

I'm not at home, so I cannot give you my triggers. But I THINK I've managed to get the mapper to use the room name and Exit lines from the ATCP
And the description from a regular trigger.

Here is what I attempted to do.

Load all of the information from the ATCP triggers into variables then when the next prompt hits I've used #TAG in the prompt to fill in the information.

You could give that approach a try and see if it helps or hurts. At any rate short of being able to use CMUD at the moment; thats the extent of my possible help, sorry.

Wanderer Joined: 23 Apr 2005 Posts: 57

Alright, after a -lot- of testing I believe I've found the cause of this problem. For whatever reason, if the 'Echo Commands' option is left enabled under Preferences/Scripting/General Scripting then the reloading of room information into the mapper (via the #LOOK command etc.) works normally - however, when 'Echo Commands' is disabled it does not.

Ironically, my first thought was to simply leave 'Echo Commands' enabled and then to #GAG commands manually via a command input trigger - however it seems that exactly the same problem occurs whenever a trigger based upon general command input exists (even, oddly, if that trigger is disabled.)

Posted: Mon Jun 02, 2008 5:42 pm

Thanks for posting the solution. I'll admit that most of my testing is done with Echo Commands turned on. Not sure how this could be different between CMUD and zMUD, but I'll post it to the bug list and look into it when I start working on the mapper stuff.

Enchanter Joined: 10 Oct 2000 Posts: 698

I believe I remember this issue occurring in zmud at some point too. I specifically remember not being able to use the automapper when Echo Commands were turned off. After the Echo Commands were mentioned in this thread I remembered that was also the cause/issue in zmud.

Okay, not the exact issue but possibly related...

7.03 26-Feb-04 (PUBLIC version)
Fixed bug with #LOOK sometimes ignoring the next line from the MUD (when Echo Commands is turned off)