Zugg Software :: View topic - Mapping Primordiax, some rooms don't consume the map direction queue

Newbie Joined: 06 Jul 2008 Posts: 4

Observed in zMud 7.something or other and CMud 3.32

I autoconfigured my mapper, and for the most part it worked well. It's detecting room names and exits very reliably, and doing a reasonable job with room descriptions (some descriptions have more than one paragraph, and for those only the last paragraph is recorded, but I can live with that).

However, some rooms don't trigger the automapper: when I try to move into them, my location in the mapper doesn't change and the command I typed stays in the direction queue. I can create rooms with #makeroom and move into those, but #look doesn't load any description for them. I can fill in their names and descriptions with copy/paste and get a working map that way, but it's awfully tedious.

Prompt detection appears to be working fine; my test trigger with #tag prompt fired at all the right times. There doesn't seem to be anything unusual about the rooms themselves. Wireshark doesn't show any unusual network activity in or around the broken rooms.

Ideas? Other things I could investigate that might lead to ideas?

Posted: Wed Nov 17, 2010 4:34 am

Do the rooms that don't get mapped have punctuation at the end of the name line by any chance?

Posted: Wed Nov 17, 2010 4:37 am

I suggest you make yourself some triggers that make use of the #TAG command.
Perhaps your own confirmation of movement when the room description is not normal (or not displayed) in #OK.
You might want to mark failed moves with #NODIR.
And you can exclude the mapper from looking at some text with #NOMAP.

Newbie Joined: 06 Jul 2008 Posts: 4

Thanks guys.

Fizgar: Sadly, no; all the room names, whether mapped or no, end with non-punctuation (and then CRLF).

shalimar: The #OK command doesn't do anything; my last movement command just sits in the queue. Refreshing the room description with l or #look also has no effect. I think I'll ultimately have to take your advice and just do everything myself with #TAG. I'm going to need to match something of the form:

Posted: Wed Nov 17, 2010 6:52 am

usually just tagging the room name and the exit is enough in my experiance, then run the configuration wizard for the mapper again.

Wizard Joined: 22 Mar 2007 Posts: 2320

Possible issues:
The rooms that the mapper is not catching might have a different style of description that does not match the one you used to configure the mapper. Sometimes, reconfiguring using one of these rooms will work for both the problem rooms and the other rooms that didn't have a problem.

The problem rooms might have a sufficiently different style of description that you need to use #tag commands to make it work.

The problem rooms might have a varying room name or description which does not always match when you enter it. Again, #tag may be the solution for this. Another possibility is to manually create the room and turn on the "Force Room Entry" option for that specific room, which will cause Cmud to assume movement works ignoring the room name and description completely.

[edit]Another solution I once used was to write a trigger that dealt with a specific style of room description, and changed the output to match what the map configuration was expecting.