Zugg Software :: View topic - [6.40

Wanderer Joined: 02 Jul 2002 Posts: 74 Location: USA

Ok, for some reason I am having problems with the mapper not picking up the room title now. I haven't tried mapping since the last beta versions before 6.40, but it worked fine then.
I've tried to reconfigure, tried a new config file, tried to use #tag to capture the name. No luck. My mud output looks like this:

< 705h/705H 134p/134P 162v/163V >
< >
The Dusk Road
This fifteen feet wide, stone paved road starts west from here,
where it meets a larger road, and runs towards the east. It looks
pretty ancient and the stone slabs, which pave the floor, have
rounded edges and scarred surfaces due the intense traffic they
have borne through the centuries. Lush green fields surround this
road and many tall bushes grow at its boundaries. Some grassy hills
rise north from here while a deep forest can be seen southward. The
road continues eastward, crossing a small village.
Room size: Large (L:75 ft W:30 ft H:500 ft)
Exits: - East - West

< 705h/705H 134p/134P 161v/163V >
< >

It captures the description like it should, the exits like it should, and the prompt like it should. It just refuses to capture the room name no matter what I try.
The trigger I was using to try to get the name was:
#trigger {^~<(*)~>$^(*)} {#TAG name %2}
problem with that is it was grabbing the first line of the description, still, totally missing the name of the room.
Trigger I had to tag the prompt was:
#trigger {^~<*~>} {#TAG prompt}
Also another thing, sometimes the room name will show up on the same line as the < >. So I can't trigger < > to #nomap.

In the configuration settings in the mapper, I have name paragraph set to 0, name line set to 0, match room name at start of line is checked, and room name uses proper-case is checked.

What I really don't understand is that the same config file worked fine before 6.40 without the need of tag triggers.

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

#trigger {^~<(*)~>$^(*)} {#TAG name %2}
#trigger {^~<*~>} {#TAG prompt}
If you compare the blue sections, you'll see that they are identical, aside from the parentheses. Being more specific would probably help immensely.

#TR {^~< ~>$(*)} {#TAG name %1}
#TR {^~< (%d)h/(%d)H (%d)/(%d)P (%d)v/(%d)V ~>} {#TAG prompt}

LightBulb
Advanced Member

Wanderer Joined: 02 Jul 2002 Posts: 74 Location: USA

Still no luck. I changed my tag triggers to the ones you gave, and reconfigured the mapper.
During the reconfigure, it still didn't pick up the room name. I figured maybe since it was tagged, that it wouldn't so I finished the reconfigure and tried mapping. The mapper is still grabbing the first line of the room description as the room name. Its like the whole room name line just doesn't exist to the mapper.
I don't have any gags set either.
Any other suggestions?

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

The only other suggestion I have is to see if you can reconfigure your MUD. For instance, you might eliminate the second line in your prompt (the < > one), or replace it with a blank line. Your MUD's output looks fairly standard, other than the second prompt line, so there's a good chance the mapper will autoconfigure without it.

LightBulb
Advanced Member

Wanderer Joined: 02 Jul 2002 Posts: 74 Location: USA

Tried that, sTill no luck.

I got to playing around with things. I have another char on that mud that I have never set up the mapper for. I made a new map, configured it, and it worked great. Loaded up my maps from the other char, and it still mapped fine except for the two or three seconds it took to make each room.
Soo.. I figured it must be one of my triggers on the original char. I disabled them all. Used the config file from the second char, and it still will not work.
What else does the mapper use other then the .ini, .mbm, and the .zfg file?
I'm thinking about exporting all my settings and remaking the char, but I don't see how that would help.