Zugg Software :: View topic - [BUG/Feature Request] Getting mapper to work correctly in safe/slow on Aardwolf

Novice Joined: 25 Aug 2009 Posts: 38

This bit is solved:

Just a major annoyance of mine... the AutoMapper hi-jacks the "Del" key here.

So I end up with this alot:

cats 'natures touch' self [home] [right right] [delete] ..... Would you like to remove room X? [NO] [NO!!] [STOP ASKING ME!!!]

Can't find the option to re-hijack my delete key... *tear*.

Now, at the bottom, I have listed my Aardwolf mapper class with all of the over-rides to hopefully get it working

Posted: Sat Sep 19, 2009 2:28 pm

what you do is take the map out of edit mode when your in combat and whatnot

or just make sure your main session window has focus

Posted: Sat Sep 19, 2009 5:07 pm

This is already fixed in the 3.10 beta version.

Novice Joined: 25 Aug 2009 Posts: 38

Is the beta worth it?
Kinda leery after the last round before my HD died and I had to re-install... the beta crashed alot last time :(

Posted: Sat Sep 19, 2009 5:56 pm

I've never had an unworkaroundable issue with it myself.
At least not for long, Zugg is on top of his game.

Novice Joined: 25 Aug 2009 Posts: 38

Upgraded :P I'm happier with the map load times, the map not jacking keys...

but now, no follow mode works other than fastwalk. No safe or slow walking now.

Of course, I play Aardwolf, with all the tags on, and room-names, room-descs, and exits are all tagged. Had some quirks before but now slow and safe are completely fubar :(

Posted: Sun Sep 20, 2009 12:49 am

make your own #OK trigger for the room exits line, or something else that shows up every room, and you should be able to slow walk fine

Novice Joined: 25 Aug 2009 Posts: 38

speedwalkign seems to work okay with that fix but one thing that still bugs out is that if you're making the map (in mapping mode) and you do a few steps at once and in more than one direction, the mapper flips out. I end up with the mapper not picking up directions/rooms, room names/descs/exits being wrong, etc. What really kills me is that I have triggers to capture each part of a room, and they always fire correctly. (really, they do, aardwolf uses tags [which when on the mapper doesn't work at all])

I end up with rooms called everything from the message from a spell running out, to parts of room's descriptions. I imagine it has something do do with the way the mapper pulls information from the mud window. I wish I could just turn off the built-in detection completely, and have it use exactly what I tell it and nothing else :P

Posted: Mon Sep 21, 2009 4:30 pm

Make sure you have reconfigured the mapper in the Beta (Config/Reconfig menu item). I use SAFE speedwalking all the time when playing Aardwolf and the 3.10 beta works fine for me here.

You might also want to post your full tag scripts. You shouldn't need to tag *everything*. In my Aardwolf settings, I only tag the room name just because sometimes there is a (G) at the end of a room name (for grafitti) that can mess up the mapper.

But if Safe/Slow do not work, that means your mapper configuration is not set up correctly. Fast mode ignores the mapper configuration.

Novice Joined: 25 Aug 2009 Posts: 38

Cool-beans on the re-write.

Here is my whole "Mapper" class (btw, where did automapper/automapperall go?)

Posted: Thu Sep 24, 2009 3:58 pm

I haven't played with the full set of {} tags turned on in Aardwolf, but I'll still try to give some feedback on this.

Rather than trying to completely override the mapper at this time, try to let the mapper handle as much as it can. The mapper actually excels at parsing room exit information. Specifically, the "#TAG exit" command is already set up to handle multiple exit names within a single string separated by any delimiter. For example, you can use:

#TAG exit "Exits: n, w, s, e"

and the mapper will properly parse it. The #TAG command currently works best if you only use it once per room. So, remove the loop for your Exit tagging and just send the entire string from the MUD using "#TAG exit $roomExits". You don't even need to replace the spaces with | characters or remove the Exits: text or brackets.

I wouldn't worry about trying to tag the Description of the room. The mapper will normally capture the text between the room name and the exit line as description text, and it doesn't really need to match the MUD {roomdesc} stuff exactly.

Finally, when using #tag, it's also important to tag the MUD prompt. The mapper will create the new room based upon your #TAG commands when it has a Name and Exit information and then you tag a MUD prompt. The prompt detection in the mapper is pretty good and you can already set up a trigger pattern for the prompt in the "MUD Prompt" tag of the Mapper Configuration properties.

And remember that when ever you use #TAG commands, you still *MUST* re-configure the mapper after creating the tag triggers. The mapper will use the values from #TAG in place of it's auto-detection, but the mapper needs the re-configuration to detect that you are using the #TAG commands.

When trying to get SAFE mode to work, go into your Map configuration preferences page and look at the Room Name tab. You should make sure the "Match Room Name at Start" and "Match Room Name at End" are turned off. SAFE mode depends upon the room name from the MUD matching the name stored in the mapper, then receiving a MUD prompt. In the "MUD Prompt" tab you can also play with some of the settings, such as the "Allow blank line to trigger speedwalking".

Novice Joined: 25 Aug 2009 Posts: 38

well, that works a little bit better, but still, the only issue I have is if I enter several commands for movement at the same time.
If I move .22x (where x is n, s, e, w) then it usually is fine... but!!
If I do something like .newsnews then it ALWAYS wiggs out and makes room more like .neesewns or something.

Posted: Fri Sep 25, 2009 12:55 pm

I have seen that happen before. Usually it happens because there is just one room on my map that doesn't have exactly the right room name. In fact, I used to have this problem with the rooms that had (G) in their name, but your script seems like it should be handling that.

Anyway, see if you can pin down the problem to a specific room or set of rooms.

On Aardwolf, I do speedwalking all the time to get to various zones to do quests quickly. I'm not in front of the computer that has my Aardwolf settings right now, but I'll post one of my useful scripts later. What it does is to find the first room in a named zone, then send a speedwalk #WALK command to send me there.

So from anywhere on the MUD, I can type "go zonename" and speedwalk to the name zone. And I haven't had this fail for a long time now, although early on when I was making the map I definitely had some rooms that caused trouble sometimes. Usually just going to the problem room and typing #LOOK to recapture the map info was enough to fix it.

Novice Joined: 25 Aug 2009 Posts: 38

This also happens when making the map, when I'm in mapping mode. I would think that with the triggers it should be capturing each room correctly.

Just an odd thing I've noticed is that I really think it has something to do with #GAG. I've noticed that when I have my roomobjs and roomchars tags on and those triggers fire it makes it worse.

Just to test it, I tried replacing 'south' in the default mapper autoconfig with multiple directions just to see what happened, and it seemed to me that in the places with more "#gag"s it looked like the mapper was capturing the text, then the mapper would have information really weird, like it was capturing exits *before* the exit line, and such.

I'll see if I can get a screenie and email it to you.

I got several, actually. I've found that generally speaking the results window shows what the mapper is detecting. And so far, its WAY off. Works one room at a time, so where its getting stupid is when multiple moves are made in succession.

I emailed you a few screenies of the reconfigure process, and what happened when I sent a command (the same I used in the autoconfigure screen)

Novice Joined: 25 Aug 2009 Posts: 38

Hopefully you got that set of screenies. If you want I could just upload you my whole package file. maybe you can figure out why it isn't working properly. I've reconfigured the map till it is probably sick of me, and I've tried turning that roomdesc trigger back on and it seems like it help swith safe/slow walking, but it still utterly screws up on speedwalks and multiple directions while I map.
Thing that kills me is that were it trips up is not if I go *one* direction. its only if I go multiple directions. (Though lately it wont even do that)
I used to be able to go say, .22w and it would map 22 rooms. That doesn't even work now... probably due to all of the 'fixxing' and forcing i've been trying to get it to not be retarded.

Btw, worlds worst room for the mapper so far... the recall room. I always had issues with that room... somethign with the description. end up with the room called "game)." or something along those lines.