Zugg Software :: View topic

Novice Joined: 27 Jul 2004 Posts: 35

Having a really really hard time getting the mapper to configure here. Autoconfig doesn't work for this MUD. Any pointers? Desc length lines change, and therefore the Exits line changes as well.

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

Use #tag triggers. When you are done writing those, run the config wizard again to activate the #tag commands.

Wanderer Joined: 24 Aug 2012 Posts: 70

If Automapping is new to you, you may want to look at this post as I just got through addressing as much helpful information as I could there.

Novice Joined: 27 Jul 2004 Posts: 35

Wanderer Joined: 24 Aug 2012 Posts: 70

Try this:

#TRIGGER {-=~( &RoomName ~)=- } {#TAG name @RoomName}

Take note of the "ADVANCED: Extracting data from a line" in #TRIGGER
It explains the usage of the ~ to tell cMUD not to parse special characters like the parenthesis
that would normally denote a Predefined Variable pattern matching string for parameter usage.
(at bottom of Predefined list)

Also take note of the List of Keywords to use with the #TAG listed in first paragraph of the page.
name the name of the room
desc the room description
exit the room exit information
vnum the virtual room number
flags flag settings for the room
prompt the MUD prompt
descpara the entire paragraph is the room description
exitpara the entire paragraph is the exit information

Wanderer Joined: 24 Aug 2012 Posts: 70

For your Exits trigger I would say go with:

#TRIGGER {Exits: &RoomExits.} {#TAG exit %replace(@RoomExits,",","");#OK}

Wanderer Joined: 24 Aug 2012 Posts: 70

Might as well set the prompt too...

#TRIGGER {HP:%d/%d MV: %d/%d} {#TAG prompt} "" "nocr|prompt"

And if your lucky, once you reconfigure it should pick up the room description on it's own.

Beginner Joined: 09 Oct 2012 Posts: 18

Man, with it this complex, no wonder us newbies have trouble!

I spent a few hours just figuring out how to tag my prompt. Had to use the Trigger editor for it, and run some tests (replaced "#TAG prompt" with "#ECHO Hi").

The MUD's prompt is simply an asterisk in ansi-blue:

*

so the trigger is basically:

#TRIGGER {^%e[1;34m~*%e[0m} {#TAG prompt} "" "nocr|prompt|ansi"

But I reran the Automapper configurator, and it still included the * in the room text, so I'm not yet sure if it's tagging right even though I know the trigger recognises it. But if I get this right, the room names might be easier because they're in ansi-light-green, room descriptions are ansi-darker-green, exits are ansi-white with a ":" delimiter.

Do non-standard exits also have to be defined (e.g. "Out"), even if I never use them?

Posted: Thu Oct 11, 2012 8:07 pm

#TR {^~*$} {#NOMAP;#TAG prompt} "" "prompt"

should do it... unless you get single asterisks on a line by themself for others reasons, there is no reason to match the color.

I tend to map the non standard exits to an unused cardinal exit and use the name field to supply the command

Beginner Joined: 09 Oct 2012 Posts: 18

Posted: Thu Oct 11, 2012 9:39 pm

that anchors it to the end of the line, its the opposite of the carot ^

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA