Zugg Software :: View topic

Novice Joined: 02 Nov 2010 Posts: 45

Hey guys!

My CMUD mapper for some reasons have some seriously annoying issue which I'm unable to fix by myself.

Since autoconfiguration and even manual configuration doesn't fit my mud (probably I'm too weak in cMUD scripting to fix it),
I was forced to turn off all mud-information catching. So name/exit/descriptions are turned off in my map configuration.
However still when I want to map some locations the mapper works weirdly. What I mean is that when i press direction,
it does not create room right after getting information from MUD (it should not even wait for these, since my config file).
This is creating sick situations when i wanna map se;se;sw;nw and mapper instead goes se;nw (since moving in map without creating does not wait).

I'd really appreciate solution for this issue.

Ok, second question (optional) - how to configure following MUD return into mapper:

(line that sometimes shows sometimes not, describing movement speed - ignore it for mapper)
(optional line - ignore it)
(Name line - starts with Capital letter, ends with '.', always one sentence, without multilines)
(Exit line - i can sub it to something like ==> N, W, E)
> (Prompt line, prompt is '>' that is always in newline and at start of that line, there can be text after prompt,
but usually there is none and MUD is waiting for another command)

Example:

You move quickly over the south-west. (It's not always here)
/disc/domain/catalogue/location (wiz info, not visible if mortal)
Merchant route. (name)
Here are two visible exits: north-east and south-west. (exits, can be subbed into ==> NE SW)
> (prompt)

Thanx guys!
Happy easter!

Wizard Joined: 22 Mar 2007 Posts: 2320

The key here will be to tell the mapper to ignore the "you move quickly" and the "/disc/domain..." stuff. The easy way to do this is to create a trigger that will fire on the line, and have the trigger execute the command #NOMAP. This tells the mapper that this line is not part of the mapping information it needs to capture. Make as many triggers as you need to deal with extraneous stuff that might accidentally get caught by the mapper. That should solve almost all of your problems. After you create these triggers, you can probably autoconfigure the mapper and have it work nicely.

Novice Joined: 02 Nov 2010 Posts: 45

Hey:

It helped, adding #NOMAP for first two lines and subbing exits made my mapping configuration work. However problem of 'long room creation time' still remains and is annoying as hell.

Thanx

Wizard Joined: 22 Mar 2007 Posts: 2320

Turning off the room name, description, and exits options does not significantly change how long it takes the mapper to create your room. All that does is change whether it tries to grab and store that information in the room database. It still has to figure out whether you have successfully moved, and create the new record in the database. That is what is taking the time. You can't change that, if you want it to be creating rooms for you. You may as well have it record at least the room name. This actually should solve some of your problems. If done right, it should avoid the problem you are seeing of having the mapper only go sw;ne.

How long is it taking to create new rooms? Do you have lots of triggers?

Novice Joined: 02 Nov 2010 Posts: 45

I have nearby 0 triggers right now, the ones i have are mapper - oriented and made my config work (it catches name of room and usually exits - however with exits sometimes mapper adds link that does not exist (always headed west, dunno why) and sometimes does not catch exit at all.

With zMUD mapper I didnt have this problem - i could turn on straight-way running script (on routes that have two exits, always go opposite site to which i've came) which in 5 seconds moves 60 locations and maps them successfuly without the problem I have now. Mapping in zMUD was waaay quickier.

Novice Joined: 02 Nov 2010 Posts: 45

One more thing.

I've made trigger: #trigger {^*.$} {#TAG name}. Then I reconfigure my map using a direction (let's say - E). Reconfiguration goes smoothly - it catches name and exit perfectly (via wizard). Then I go back W and remove the room I've just made using reconfiguration. When I go E with mapping on, _nothing_ happens - I mean the direction E is added to direction queue, but mapper does not create room and seems like it's waiting for some confirmation. I think that might be connected to long room creating issue.

Posted: Mon Apr 25, 2011 7:53 pm

try #TAGing the exit line, and if you have already... maybe add #OK to it

Novice Joined: 02 Nov 2010 Posts: 45

When I make #trigger {^==> (*)$} {#TAG exit} or #trigger {^(*).$} {#TAG name} the mapper stops mapping at all :)

#OK doesn't help (and it shouldn't since i have speedwalking fast?)

Sorcerer Joined: 15 Apr 2011 Posts: 809

After you made your #tag triggers, did you re-run the config wizard?

Novice Joined: 02 Nov 2010 Posts: 45

Yes, of course. It doesn't map afterwards (look 2 posts higher).

Novice Joined: 02 Nov 2010 Posts: 45

How to propertly mark prompt which seems like this:
"> "

Trigger patterns like {^>} or {^~>} don't seem to catch my prompt (f.e. #trigger {^>} {#SH ABC} will not work). Any idea how to fix it? I'm worring that this is the reason of weird behavior of mapper.

Posted: Tue Apr 26, 2011 3:09 pm

on your prompt trigger... did you check the 'fire on prompt' option and uncheck 'fire on newline'?

Using #OK only does one thing.
It tells the mapper you have successfully entered the new room.
Without knowing this, you will never have your location on the map kept up to date or be able to speedwalk at anything other than fast.

Novice Joined: 02 Nov 2010 Posts: 45

Doesn't work in any of the ways you described (either with trigger on newline and with trigger on prompt, i even checked ticking and unticking them both since it's not much work to do anyway).

Example of my MUD's prompt:
"> look"
"Room description."
"> "

Novice Joined: 02 Nov 2010 Posts: 45

Solved prompt issue - had to turn of GA/EOR for prompt in options.