Zugg Software :: View topic

Novice Joined: 20 Dec 2001 Posts: 39 Location: USA

I'm having a problem with the mapper not detecting a room. When in map mode, it just queues up the down command. When I try to use the autoconfigure on that particular room, the room description is not detected, though the exits are. Here is a cut-and paste of the log of both rooms, including ansi codes.
Detected room:
[37mThis small shack appears to have been thrown together using parts of various ships,[0m
[37msalvaged from the decaying vessels scattered over the dock. A large sign has been posted[0m
[37mjust outside the shack, written in basic. A small hard packed trail leads back to the[0m
[37mdock to the west. You see a set of stairs that lead down.[0m
[37m [0m
[36mThere are two obvious exits: down and west.[0m
[0m
[1;37mA squat Ugnaught[0m

The following room, down from the above one, is not detected:
[37mThis is the Crseih Merchant's Guild. A small out of the way office where Merchants come to[0m
[37mlearn merchant skills. To join the guild, type <join>. To advance your merchant level,[0m
[37mtype <advance>. Panic experience for amounts of experience required to advance.[0m
[0m
[37m [0m
[36mThe only obvious exit is up.[0m

Anyone have any ideas/suggestions?

SubAdmin Joined: 18 Nov 2001 Posts: 5182

First thing to check is that you have up and down configured as directions. I believe they are by default.

Next you might wish to preform the autoconfigure with the offensive room so you can see something of what is going wrong.

I suspect the problem lies with the use of <> in the room description. Overcoming this would be quite simple:
#TR {{~<|~>}} {#SUB {`}}
If the problem is what I think then that trigger should do it. No reconfigure is required with it.

Posted: Wed Dec 26, 2001 10:51 am

You haven't set 'exits' as a keyword for the exit line, have you? As this won't recognise rooms with only one exit, like the one you have here...

Lady C.

Novice Joined: 20 Dec 2001 Posts: 39 Location: USA

Ok... here are the mapper helper triggers I've created, because of some problems with detection due to the ansi codes...

#CLASS {mapper}


#TRIGGER {%e[1;33m} {#nomap} "" {color}


#TRIGGER {%e[1;36m%w tells} {#nomap} "" {color}


#TRIGGER {%e[1;36m%w replies} {#nomap} "" {color}


#TRIGGER {The door opens, revealing a transparent screen which will slide aside as you go east.} {#nomap}


#TRIGGER {^%e[36m* {exit is|exits:}(*).} {#tag exit {%1}} "" {color}


#TRIGGER {%e[1;35mrebel} {#nomap} "" {color}


#TRIGGER {%e[1;35mshout} {#nomap} "" {color}


#TRIGGER {^%e[1;37m} {#nomap} "" {color}


#TRIGGER {^You wave your voucher in front of the camera.} {#nomap}


#TRIGGER {A metallic voice says: Enter.} {#nomap}


#TRIGGER {The door opens, revealing a transparent screen which will slide aside as you go %w.} {#nomap}


#CLASS 0

quote:
First thing to check is that you have up and down configured as directions. I believe they are by default.

They are.

quote:
Next you might wish to preform the autoconfigure with the offensive room so you can see something of what is going wrong.

As I stated in my first post, I did try using autoconfigure going down from the detected room to the non-detected room... it detected nothing for the room description, but did detect the exits... I have room name detection turned off since this is an lpmud with no room name except in brief mode. I did consider making a room desc tag trigger for esc[37m, but that particular ascii code is used often.

And, as stated above, my room exit trigger is set to allow for both exit line possibilities... and I did autoconfigure after all of the above triggers were defined. Any other suggestions? Oh, the behavior of the mapper when I do go down... the down gets put into the mapper command queue, and stays.

Bob, Kayd on SWMud and a few others.