Unknown2004-11-03 08:44:27
OK, a few things about the Mapper here:
1) When I move about with the mapper on in "Map Creation mode", it usually doesn't follow the direction I move in, and in the corner of the mapper it says "Queue:". How can I stop this and what is queuing?
2) For some reason I can't tag the room's name with this ANSI trigger:
1) When I move about with the mapper on in "Map Creation mode", it usually doesn't follow the direction I move in, and in the corner of the mapper it says "Queue:
2) For some reason I can't tag the room's name with this ANSI trigger:
CODE
#TRIGGER {^%e
Savash2004-11-03 10:04:24
Certain versions of Zmud have a broken #tag command. The latest works just fine.
Unknown2004-11-03 12:49:10
I still have the problem with the queue not clearing when I move. What I did was make it move when I'm in follow mode, and in mapping mode, I just have to watch the queue and hit the ESC key to clear it manually before mapping further.
Unknown2004-11-04 00:32:41
Don't forget #NODIR.
Set up triggers for when you try to go a direction but don't.
#TRIGGER {There is no exit in that direction.} {#NODIR}
Or something like that, should help a little in clearing that last direction.
What the queue does is remember the last direction you typed then wait for the mud output to show you have entered a new room then creates the room in the direction that is queued.
The problem arises usually when you "try" to go in a direction that you can't. For example, you try to go east, but there is a wall there. The mapper queues "east" and waits for the new room, but instead of a room it gets "There is no exit in that direction". So instead you try west. The mapper adds "west" to the queue and continues to wait for the room. Now, when you move into that room to the west it sees the room and the mapper creates a room from the queue.
The first direction in the queue is: east. That is where it will create the room on the map.
If you had had a trigger like the one above, when you tried to go east initially it would execute the #NODIR (no direction) command and clear that east from the queue.
Hope that explains things for you a little better.
Set up triggers for when you try to go a direction but don't.
#TRIGGER {There is no exit in that direction.} {#NODIR}
Or something like that, should help a little in clearing that last direction.
What the queue does is remember the last direction you typed then wait for the mud output to show you have entered a new room then creates the room in the direction that is queued.
The problem arises usually when you "try" to go in a direction that you can't. For example, you try to go east, but there is a wall there. The mapper queues "east" and waits for the new room, but instead of a room it gets "There is no exit in that direction". So instead you try west. The mapper adds "west" to the queue and continues to wait for the room. Now, when you move into that room to the west it sees the room and the mapper creates a room from the queue.
The first direction in the queue is: east. That is where it will create the room on the map.
If you had had a trigger like the one above, when you tried to go east initially it would execute the #NODIR (no direction) command and clear that east from the queue.
Hope that explains things for you a little better.
Unknown2004-11-04 00:48:15
Any idea why mine wont pick up rooms connecting sometimes, as in it creates a room overtop of the actual room it connects to.
Unknown2004-11-04 00:54:00
Possibly, it is picking up people/mobs/objects in the room description. If you leave the room and re-enter it, some of these things may have changed causing the mapper to think it is a different/new room.
Try going into the mapper configuration properties (I think, I am at work atm and don't have zmud in front of me) and checking the box that says: Room description changes.
This may solve some of the problems, mine still does it very occasionally.
Try going into the mapper configuration properties (I think, I am at work atm and don't have zmud in front of me) and checking the box that says: Room description changes.
This may solve some of the problems, mine still does it very occasionally.
Unknown2004-11-04 08:26:45
But how can I make the tagging work properly?
Like, when I enter this into my command line:
#TAG name {Sombre Lane}
it does not name the room at all. Any reason why this might be happening?
Like, when I enter this into my command line:
#TAG name {Sombre Lane}
it does not name the room at all. Any reason why this might be happening?
Unknown2004-11-07 02:52:53
QUOTE (Zarquan @ Nov 4 2004, 01:49 AM)
I still have the problem with the queue not clearing when I move. What I did was make it move when I'm in follow mode, and in mapping mode, I just have to watch the queue and hit the ESC key to clear it manually before mapping further.
I just made this simple trigger which works for me (using the darkish yellow colour for the room name):
CODE
#TRIGGER {^%e
Azazel2004-11-07 03:52:28
i cant for the life of me figure out how to get slowwalking working. Even with that colour trigger it just doesnt seem to OK the movements. Any help would be greatly appreciated
Unknown2004-11-07 04:02:01
Hey you two, post some info will yah? what version of zmud? what colors are you using for your rooms? we need some specific info to work with here.
Azazel2004-11-07 05:18:47
heh sorry. 7.05 of course. However i think ive fixed it.
CODE
#TRIGGER {^%e
Unknown2004-11-07 08:23:11
QUOTE (Azazel @ Nov 7 2004, 06:18 PM)
heh sorry. 7.05 of course. However i think ive fixed it.
CODE
#TRIGGER {^%e
Unknown2004-11-07 08:50:05
Wait, hang on. The configuration only seems to work (tag the names etc.) when I go 'Reconfigure', otherwise, it does nothing at all. Why would this be happening?
Unknown2004-11-07 22:28:36
Acck... arg.. damn Automapper.. Zugg what have you unleashed upon mankind?
Took me forever and a half at first to configure my mapper on achaea.. took me like an hour on lusternia..
but heres my stuff for yall to look at.
Version: 211
Name Start: 0
Desc Start: -1
Desc End: 0
Exit Start: 1
Exit End: 1
Exit in Prompt: 0
Exit in Name: 0
Exit contains key: 1
Name paragraph: 0
Desc paragraph: 0
Exit paragraph: 0
Bracket prompt: 0
Short exit names: 0
vNum in Name: 0
Exit keyword: exit
Exit after keyword: 0
Match room name mode: 1
Use Descriptions: 0
Entire exit paragraph: 0
Single char exit: 0
Autoprompt detect: 1
Complex prompt: 1
Prompt char:
Name ends in period: 1
Number prompt: 0
No MUD Prompt: 0
Room Name Propercase: 0
Prompt trigger: ^\\d+\\w+\\, \\d+\\w+\\, \\d+\\w+\\, \\d+\\w+ \\-
Prompt Regex: 1
Description changes: 0
#TRIGGER {%e
Took me forever and a half at first to configure my mapper on achaea.. took me like an hour on lusternia..
but heres my stuff for yall to look at.
Version: 211
Name Start: 0
Desc Start: -1
Desc End: 0
Exit Start: 1
Exit End: 1
Exit in Prompt: 0
Exit in Name: 0
Exit contains key: 1
Name paragraph: 0
Desc paragraph: 0
Exit paragraph: 0
Bracket prompt: 0
Short exit names: 0
vNum in Name: 0
Exit keyword: exit
Exit after keyword: 0
Match room name mode: 1
Use Descriptions: 0
Entire exit paragraph: 0
Single char exit: 0
Autoprompt detect: 1
Complex prompt: 1
Prompt char:
Name ends in period: 1
Number prompt: 0
No MUD Prompt: 0
Room Name Propercase: 0
Prompt trigger: ^\\d+\\w+\\, \\d+\\w+\\, \\d+\\w+\\, \\d+\\w+ \\-
Prompt Regex: 1
Description changes: 0
#TRIGGER {%e
Unknown2004-11-08 03:28:43
Try to avoid using %* in patterns. Zugg said something about it allowing someone to execute commands in your client, though I can't find the post or article because I can't search for a wildcard on his forums. Using * works just fine, anyhow.
Unknown2004-11-08 09:35:08
QUOTE (Lodin @ Nov 8 2004, 11:28 AM)
What ones are these? Are the ones like the Name Start Line or Paragraph #? If so, I can't seem to get the negative value for Desc Start.
Unknown2004-11-08 17:06:32
the settings for the mapper themselves werent manually configured.. i am just posting what the auto config did once i got the room names to match up.
Unknown2004-11-09 03:24:26
But, is what you call "Name Start" fully Map Preferences > Configuration > Room Name > Name Start Line?
Unknown2004-11-09 04:47:49
nothing else in there that seemed to have anything to do with a "name start" so yeah i guess.. i dont think you need to worry about the mapper configurations as much as you need to work out the room names using those triggers though.. cause all i did was work out the trigs to get the roomname captured correctly and hit autoconfig.
Drago2004-11-15 04:47:18
I'm surprised at how many people have problems with zmud's automapper.. everytime i've used it, its worked fine (especially when i've switched to verbose before mapping) and I made maps of everything except the planes beyond earth and water..
The only problem I've had is that it refuses to show up unless its maximised..
The only problem I've had is that it refuses to show up unless its maximised..
Privacy Overview
This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.
Strictly Necessary Cookies
Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.
If you disable this cookie, we will not be able to save your preferences. This means that every time you visit this website you will need to enable or disable cookies again.