Zugg Software :: View topic

Wanderer Joined: 03 Jan 2002 Posts: 66

Why does:

* HP:Healthy MV:Full > Braem Wood
Although there are plenty of stout, tall trees in view, some have fallen
over, and now lie on their side, creating a natural cover for ferns and
bracken to grow under. To the north are leagues upon leagues of forest,
although it cannot be reached from here. The Braem Wood continues to the
south and west.
[ obvious exits: S W ]

not work for finding the room on the map but:

* HP:Healthy MV:Full >
Braem Wood
Although there are plenty of stout, tall trees in view, some have fallen
over, and now lie on their side, creating a natural cover for ferns and
bracken to grow under. To the north are leagues upon leagues of forest,
although it cannot be reached from here. The Braem Wood continues to the
south and west.
[ obvious exits: S W ]

does? Only difference I see is that room name follows prompt instead of on newline. I have the match name at start of line box unchecked and walking in rooms I have already mapped works fine in both of the above cases.

Wizard Joined: 15 Jan 2002 Posts: 1644 Location: USA

check the rooms names at end of line see if that helps

Wanderer Joined: 03 Jan 2002 Posts: 66

Nope...forgot to mention but I already tried that one.

SubAdmin Joined: 18 Nov 2001 Posts: 5182

You have to uncheck the 'Room names at start of line' in the config as well as checking the EOL option.

Also since your mud has a problem with placing things seperate from the prompt you should be very careful when mapping to assure that your prompt did not become part of the room name when that room was mapped. The best way to do this is with an automated onroomcreate alias that checks for the prompt in the detected name by way of the %roomname function. It should then fix it whenever found. If you find you have rooms where this problem occurred and need an example alias I will be happy to write on for you.

Wanderer Joined: 03 Jan 2002 Posts: 66

Thank for the alias offer (it doesn't hapen too often so I just go through and edit them by hand) but checking the end of line box and unchecking the start of line box doesn't work. This problem only occurs when I am doing something really fast (lots of commands at once like running for my life, which unfortunately is when I really need it to work.) there is a similar topic to this where some people were trying to #tag the room name and I have this:

#TRIGGER {(*)%e[36m(*)%e[0m$(*)} {
#TAG name %2
room = %2
#ECHO @room
} "" {color}

(which was inactive for the above tests)

which properly gets the room name based on the color, but also fails to help the program #find the room on the map. I really appreciate all the help with this.

Newbie Joined: 08 Apr 2004 Posts: 4 Location: Sweden

Or you could make a substitute trigger that always places text recived from the mud on a new line.

#trigger {^prompt} {#substitute {prompt%cr""}}

You might need a second substitute trigger for this to work 100%

#trigger {^prompt (%*)} {#substitute {prompt%cr%1}}

You have to change the wildcards to include the varying conditions for HP, and MV

I've managed to get this working on wotmud.org I belive that is the mud you play.

(I am not at home just now, so I am not 100% sure that these triggers will work, but you got the idea for how to fix this. Also good to for being able to use ^ in triggers}

Wanderer Joined: 03 Jan 2002 Posts: 66

Alright I used the trigger:

#TRIGGER {^(*)>} {#SUBSTITUTE {%trimleft(%1>%cr)}}

and it places the room name on a new line every time...but there is usually a space before the name like:

o HP:Hurt MV:Fresh >
[space]Sleeping Chamber
The devastation here is overwhelming.

and it won't locate on the map...I added trimleft and it still has the space. any new ideas? (and yes I play WOTmud) Thnaks again.

MASTER Joined: 28 Nov 2000 Posts: 4817 Location: USA

If you don't want the space on the next line, include it in your pattern.

Wanderer Joined: 03 Jan 2002 Posts: 66

Wow lightbulb they should give you one of those Official ZMud Guru stickers ;-) That worked although it still won't locate on mapper when I spam commands before hand.

Wanderer Joined: 03 Jan 2002 Posts: 66

Wow lightbulb they should give you one of those Official ZMud Guru stickers ;-) That worked although it still won't locate on mapper when I spam commands before hand.

MASTER Joined: 28 Nov 2000 Posts: 4817 Location: USA

Thanks, they've tried.

Wanderer Joined: 03 Jan 2002 Posts: 66

Double post at different times...strange...it seems that I am going about this the wrong way...or I don't understand exactly how the #find command works internally...giving up on this one for now unless any other Guru's have more suggestions. ;)
Thanks for all your help.