Zugg Software :: View topic - Mapping

Novice Joined: 17 Nov 2008 Posts: 30

Hi,
Could you help me configure the mapper ?
I'm using Mutlimud : www.multimud.net
and i've difficulties with map preferences :

i've checked multiline descriptions
i've configured
exit line keyword : exits :
It recognizes rooms exits (in blue with wizard)

but i can't grab the room name wich is in middle of the line with <( )>
Furthermore, i think i will be annoyed with Weather (Daylight, Night...)
or with lines like : "You enter..."

Could you give me some advice ?
Thanks,

Posted: Mon Nov 17, 2008 2:25 pm

Shouldn't be too hard actually. Try:

#trig {^<~(---} {}
#cond {^ \<\(\s+(.+?)\s+\)\>} {#tag name %1} {regex|within|param=1}
#cond {^[ Exits: ([NESWUD ]+) ]} {#tag exit %2} {regex|within|param=20}

Enter this on the command line and reconfigure the mapper (remember to uncheck the Room Description box) and hopefully it'll start working. You might need to adjust the param=20 to something higher if you have room descriptions longer than 20 lines.

Novice Joined: 17 Nov 2008 Posts: 30

Thanks for your answer but i still have problems :)
I've entered the trigger in the command line (line by line) but it is not "triggered" i think :o
Here is the trigger thing (states tab):

Posted: Mon Nov 17, 2008 11:19 pm

A character, >, has disappeared from the end of the second pattern. Put it back.

Novice Joined: 17 Nov 2008 Posts: 30

Thanks, i've corrected and i've just changed the pattern for the exits :

Posted: Wed Nov 19, 2008 1:07 am

Ahh, balls, the quotes disappeared from the pattern in my post above - the forums ate them. Quote my post to see what I actually meant.

The trouble with doing the description is that you need to trigger on all those lines separately, so it's more difficult (read: unreliable) than just doing the name and exits. Do you really need the description for something? The mapper will work just fine with it unchecked.

Novice Joined: 17 Nov 2008 Posts: 30

Sure it will work fine and that's great ^^

But, i would like some descriptions because some names are rather obscure : "dark home", "dark cavern"... and i know i will not remember the content (description) in a month or so. Furthermore, i would like to research the description of the room : if someone (maybe a mission produced by the bot) tells me "hey go to the cavern where you see a red sign on the wall, dig, and you'll find the red pearl then...", i would be crazy

So, maybe i've an idea, can't we say with a pattern : take all the signs
between the blank line (line with nothing on it (just after the title)
and the line with [ E on it
and store it with tag desc ?

Thanks

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

Something I have done on one mud I play is to capture everything between the prompts.
Here is a list of the general steps required.
I'm not going to elaborate this into an actual script someone else might though.

These triggers can generate HUGE amounts of lag as well as eat memory so they should turn themselves on and off using trigger Ids and #T- #T+

The room name trigger should use %maplocked() to determine if the map is in mapping mode or not. If it IS then it should do the following.

The trick is remembering that the mapper really does not care if the information appears on screen or not, or even when. So long as the information it needs is provided within the number of seconds that you tell it to wait during the configuration.
Good Luck

Posted: Thu Nov 20, 2008 1:47 am

Actually, this shouldn't be very difficult at all to write since we already know where the description begins and ends:

#trig {^<~(---} {}
#cond {^ \<\(\s+(.+?)\s+\)\>} {#tag name %1;#t+ DescTrig;Desc=""} {regex|within|param=1}
#cond {^[ Exits: ([NESWUD ]+) ]} {#t- DescTrig;#tag desc @Desc;#tag exit %1} {regex|within|param=20}

#trig "DescTrig" {*} {desc=%concat(@desc," ",%line)} "" {disable}

Should capture the descriptions as well. Only trouble is that all the descriptions will have the line of hyphens under the name at the start - if that bothers you, you can use replace or %subregex to remove it.

EDIT: And quote this post to see what I really meant with the pattern.

Novice Joined: 17 Nov 2008 Posts: 30

Thanks Fang it is really working great. I will tell you if i encounter a problem but that works perfect :o) Very Happy

Thanks Arminas too for your ideas :) Maybe a little difficult but that should work too :)

Thanks for your help Wink