Zugg Software :: View topic - How to update current room exits programmatically?

Beginner Joined: 06 Jul 2007 Posts: 27

I submitted a problem, "Down Exit added to every room", a little over a week ago and am still getting the problem. Rooms are showing a 'down' exit when there is no real exit down.

It's not every room that Automapping creates, but maybe 50% of the rooms created while automapping. This problem started when I changed the Aetolia CONFIG WRAPWIDTH to 0 to shut off the CRLF's that were being added at or around 80 characters. I did not change the CMUD word wrapping options.

Where I used to see a single, very long, line from the MUD displayed as
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

I now see the same line (using CMUD word wrapping) displayed as
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXX

Sometimes the Aetolia MUD sends the exits on its own line, other times it may be tagged onto the end of the (last )description line.

I am not using the #tag functionality. It appears to be a bug in the Automapper.
----------------------------------------------------------------------------------------------
Since I still have the problem with the random down exits, I've tried to create an alias to remove the down exit from the current room as follows (pseudocode):

exit list = %roomexit [ initially l|n|k|d ]
generate new exit list with '|d' removed [ now l|n|k ]

I've tried to set the new exits using

#call %roomexit(room number,new exit list)
OR
#call %roomexit(,new exit list)

but nothing happened. The documentation says you can set or get the room exits - there was no example given for setting using %roomexit but I saw other functions that used the #call command to set a value.

I was using local variables to hold the roomnum and roomexit arguments.

What am I doing wrong?

Beginner Joined: 06 Jul 2007 Posts: 27

I discovered a pattern on the stray down exits (XXX = Description; yyy = Exit sentence)

If the MUD sends back the Exit sentence as a separate line, then the phantom down exit doesn't seem to happen:
XXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXX
yyyyyyyyyyyyyyyyyyyyyyyy

If the MUD attaches the Exit sentence to the last description line, the phantom down exit seems to occur:
XXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXX. yyyyyyyyyyy
yyyyyyyyyyyyy

Thanks

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

Here is something I have found can help in this case. As with everything it may need tweeking in your mud.

If the description and the exit line have two distinct colors make an ansi trigger for a line that has both colors in it.

^(%e[colorcode1*)(%e[colorcode2*)$

#nomap
#gag
#say %1
#sayp %2" "