Zugg Software :: View topic

Adept Joined: 18 Dec 2005 Posts: 246

I try autoconfig for the mapper moving west into this room:
Stone Path
[Exits: north east west]
To the northwest, you notice a large, run-down stone building. It looks
mildly like a large tomb, except that it almost appears pleasant, so fully do
the various vines and shrubs surround it. Maybe it is just the over-growth.
To the east you see a brick-lined path. To the north, you can walk around the
building. An archway opens to the west.

It keeps picking up stone path as room name as it should, but it picks up the line " To the northwest you notice a large..." rather than the "[Exits:xxx]" Line. In the past the autoconfig has worked well, this is the first time I've had this issue... Has it changed recently?
I've also tried this on other rooms, particularly ones that dont have a direction (i.e. northwest) in the first line, with the same response.

Enchanter Joined: 11 Feb 2003 Posts: 511 Location: USA

You may just need to use tags to get it to work right.

Adept Joined: 18 Dec 2005 Posts: 246

Grrrrr.
I've just been messing around with this for 3 hours. bleh I can't get it to work
I go through the reconfigure, or new configuration with the autoconfig wizard, it sets some things correctly. When I go through it, it shows what has been detected. Blue is the room name. It is detected correctly and says paragraph 0 line 0. It then leaves the exts line in black, and shows the first line of the description in red which should be the exits. The config settins indicate the exits are paragraph 0 line 0. It then highlights the rest of the description in green as it should but in the config settings it says the room description paragraph is 0 and line is 2.
Seems to me if the name is paragraph 0 line 0, the exits (which are the next line from the mud) should be paragraph 0 line 1 or paragraph 1 line 0. the description should then be paragrph 0 line 2 or maybe paragraph 2 line 0.

The odd thing is I have another character that I use the same package with, and it works just fine.

This does not seem to me as though it is a difficult description to pick up, and it has worked many times before. I reaaly think something is broken here.

Enchanter Joined: 11 Feb 2003 Posts: 511 Location: USA

which mud is this?

Adept Joined: 18 Dec 2005 Posts: 246

Foxmud.com 4848
address 72.189.77.163

Adept Joined: 18 Dec 2005 Posts: 246

Is there any way to see what the mapper picks up for each room as the name exits and description? Please note I am not referring to the room name, exits, and description that are in the map database. I'm referring to what the mapper tries to compare against that data to identify where i'm at.
i.e. im in a room called "Dragon's Eye" with exits of south and north. My map shows that room as Dragon's Eye with exits of South and North. However when I enter a room or do a #find, somehow the mapper is going to try to identify a room name to match against "Dragon's Eye" to see where I'm at. That's what I'm interested in. Thanks again for the help.

Enchanter Joined: 11 Feb 2003 Posts: 511 Location: USA

okay, for your situation, can you reconfigure into another room that doesn't have a cardinal direction in the description?

Adept Joined: 18 Dec 2005 Posts: 246

I just tried that again (for about the 600th time). This time, when I did the auto configure, the room name was highlighted appropriately, (blue), the exits were highlighted appropriately (red) and the description was highlighted appropriately (green). However it still doesn't track me. Even if I put it in fast walk mode and turn on "disable automatic confirmation" from the speedwalking menu in the config settings menu.

The #find command is now starting to work a bit. But it is sporatic.

Adept Joined: 18 Dec 2005 Posts: 246

hmm another thing that doesn't appear to be working, if I enter #move n from the command line, nothing happens.

Enchanter Joined: 11 Feb 2003 Posts: 511 Location: USA

for the speedwalking, check what your config is trying to detect (description, room name, etc). Sometimes this gets set to description when you don't want it to be. Also, check to be sure the mud prompt line is correct in the config.

Adept Joined: 18 Dec 2005 Posts: 246

In looking at my map in the spreadsheet view, after filtering for all, I've found a bunch of rooms tith a refnum set to zero.... it appears to me that most rooms have a refnum that matches the objid field. What is the difference between the two?

Enchanter Joined: 11 Feb 2003 Posts: 511 Location: USA

Not entirely sure why you are having issues with the automapper following. The only time it didn't follow me was when I had to go through a door that was on the mapper already. The room name then would be appended to the prompt instead of on a newline and thus the mapper wouldn't detect it.

I had speedwalking on SLOW, with Match Room Name as the comparison.

Adept Joined: 18 Dec 2005 Posts: 246

Well, I figured out the first part of my problem. It turns out, on order for the mapper to work, you HAVE TO HAVE DIRECTIONS DEFINED. Somewhere along the way, probably in an effort to clean up my scripts, I must have unloaded the English Directions and English Keypad packages that are defaults. The net result was (hopefully was.) that when I would try to even use a "#move w" command, the mapper didn't even know what w meant. Along those lines, when I would try to move one direction, the mapper could not follow me because it did not know what direction I was going. Even though I don't think this has fixed all of my detection problems, it at least has given me the ability to move around my mud and be tracked by the automapper in fast mode. I just wish this was a bit easier to diagnose. Seems to me maybe the mapper could have some sort of quick syntax error indicating "no direction defined" or similar so that it somehow checks to see at list minimal directions are defined. Thanks the help Dumas

Posted: Tue Apr 07, 2009 5:07 pm

I'll add something to the wish-list for the future for the mapper to try and detect if you don't have any directions defined. Some other people have run into this problem in the past as well, and it's not something we typically think about when trying to diagnose mapper issues.

Also, in your specific MUD case, go into the Exit Configuration screen and enter "[Exits:" into the exit keyword field and enable the option that says "exit on same line as keyword" (or something like that). This will ensure that the auto-config will ignore the exit names in the description and just look at the exit line.