Zugg Software :: View topic - [3.27] #look isn't creating exit stubs for non-standard exits

Posted: Sun Sep 19, 2010 7:37 pm

In a room that had a new 'in' (non-standard, but defined) exit, I executed '#look' to update the exits. It didn't properly create an exit stub for the missing 'in' exit.

There is clearly an 'i' exit in the data from the server:
Data from GMCP: exits="e=636|d=634|i=6614"

I've defined the direction "i" below:

Apprentice Joined: 10 Apr 2009 Posts: 145

I've never managed to get that to work in any version. No GMCP here though.

Posted: Sun Sep 19, 2010 9:16 pm

This should have been fixed already, a while ago when Zugg addressed it from this post:

http://forums.zuggsoft.com/forums/viewtopic.php?t=33697

But the link above is for newly created rooms and I can't do that in the 3.27 version with the current room creation bug... However if the #look and new room creation code is operating differently from one another then that should be addressed. I'm tired of running into bugs with non-standard exits.

Posted: Mon Sep 20, 2010 5:22 pm

Please show me the full GMCP record for the room that you are in so I can test this here.

Posted: Mon Sep 20, 2010 5:29 pm

%gmcp.room.info =

Posted: Mon Sep 20, 2010 5:40 pm

No, I mean can you go to the Script Debugger and turn on the Raw Input/Output messages and then paste the exact GMCP data record being sent by the MUD. I need the original JSON record data to test this.

Posted: Mon Sep 20, 2010 6:18 pm

Posted: Mon Sep 20, 2010 6:41 pm

Thanks, I'll look into it. This is different than the previous bug that was reported and fixed a while back. This is a new bug related to how CMUD is sending the GMCP exit data to the mapper.

Posted: Mon Sep 20, 2010 9:24 pm

This is the same as the issue with your custom "i" direction that I posted in a different thread. The Exits sent from the MUD via GMCP needs to match one of the *commands* defined for the exit. The MUD doesn't care what speedwalk direction character you assign to this direction. So again, you need to add "i" to the list of valid commands for your "i" custom direction. Then CMUD will create the proper stub exits.

Posted: Mon Sep 20, 2010 10:33 pm

Yep, that was definitely it. I never had 'i' or 'o' defined originally because I always used 'in' and 'out' before Achaea started specifying them as 'i' and 'o' in GMCP. Even if I had been staring at my direction definitions I wouldn't have guessed this as the reason because I would have thought the speedwalking portion would have been sufficient to let the mapper know that 'i' and 'o' were directions.