Register to post in forums, or Log in to your existing account
 

Play RetroMUD
Post new topic  Reply to topic     Home » Forums » zMUD General Discussion
randell
Newbie


Joined: 30 Jul 2004
Posts: 2

PostPosted: Fri Jul 30, 2004 12:52 am   

Mapper Question
 
I have the mapper setup and it's working ok, except when there is a door.

I need to send "open door south" and then "s", but when it does that, I get something like:

<621/674H 181/181M 166/166V -74A 18848329 7am>open door south
s
But it's currently open!

<621/674H 181/181M 166/166V -74A 18848329 7am>Central Entrance
Cobwebs hang from the dust-covered columns of this great hall, illuminated
by torches fluttering in iron sconces. The dust and webs cast strange, moving
shadows across the faces of stone gargoyles squatting motionlessly on the rim
of the domed ceiling. Cracked and faded ceiling frescoes are covered by
centuries of decay. Two doors of bronze stand closed to the north. To the
west, a wide staircase climbs into darkness. All the while, sad and majestic
organ tones float about you from a lit hallway to the east.
[ Exits: n e s w ]

The problem is that the mapper does not detect the move and on the map I go no where (whereas I actually moved)

I also get the prompt&name problem if I type on the command line n;n;n;n the first one works, but then the rest of the output I get back is prompt&name on one line.

Any idea on how to correct this?
_________________
Randell
Reply with quote
Danlo
Magician


Joined: 28 Nov 2003
Posts: 313
Location: Australia

PostPosted: Fri Jul 30, 2004 1:17 am   
 
This should fix it:
#trigger {But it's currently open!} {#ok}
Reply with quote
randell
Newbie


Joined: 30 Jul 2004
Posts: 2

PostPosted: Sun Aug 22, 2004 4:11 am   
 
I have this problem on other things, not just mapper. It's at the point where I cannot anchor the beginning of my trigger text because sometimes it's on it's own line, sometimes, it's right at the end of my prompt.

This isn't the mud that is causing the problem, something with how zmud parses the lines.

The easiest way for me to duplicate it, is to type n. When you go north, you'll find the the room name is on it's own line. If I put in n;n;n (or something like that, all on the command line), hit enter, the room names start showing up at the end of my prompt. (if I just did north, enter, north, enter, north, enter, the room names will all be on their own line).

Any idea? Is this a bug, or perhaps I'm missing a setting or something?
_________________
Randell
Reply with quote
Silencer
Newbie


Joined: 23 Aug 2004
Posts: 8
Location: Tamworth, Australia

PostPosted: Mon Aug 23, 2004 8:54 pm   
 
Several servers have implementation of sending information catered to zMUD to fix this problem (varied success rates). So I at least am thinking old issue with zMUD.
Reply with quote
nexela
Wizard


Joined: 15 Jan 2002
Posts: 1644
Location: USA

PostPosted: Mon Aug 23, 2004 11:21 pm   
 
Quote:
I have this problem on other things, not just mapper. It's at the point where I cannot anchor the beginning of my trigger text because sometimes it's on it's own line, sometimes, it's right at the end of my prompt.........This isn't the mud that is causing the problem, something with how zmud parses the lines.


Well actually its more the fault of the mud, with bad coding style (IMO) on the part of the mud. but Im not going into details

open up your mapper->config->configration settings->roomname and check the room name on end of line option and uncheck the rest.

Also you don't need the #OK trigger you need a #NOMAP trigger (You may have to RELOAD the room name/desc if the mapper mistook that as the Room name/desc)
#TRIGGER {But it's currently open!} {#NOMAP}

As an added benifit lemme give you a quick break down of #NOMAP and #NODIR *tailor to your muds output

#NOMAP The mapper WILL not parse this line, Ideal for lines like

#TR {You fly through the air.} {#NOMAP}
#TR {It is too dark to see.} (#NOMAP;#OK //OK used to force mapper to move in dark)

#NODIR the mapper will REMOVE the last direction entered from the stack when you fail a move, Ideal for lines like
#TR {You can't go that way.} {#NODIR}
#TR {You need a boat to go there} {#nodir}

#OK tells the mapper you have moved successfully, #STEP executes next Dir in stack Read the Understanding speedwalking guide in the support library of this website for more details.
_________________
Zmud Support Library
Zmud Knowledge Base
Reply with quote
Display posts from previous:   
Post new topic   Reply to topic     Home » Forums » zMUD General Discussion All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

© 2009 Zugg Software. Hosted by Wolfpaw.net