Zugg Software :: View topic

Apprentice Joined: 18 Feb 2007 Posts: 190

i previously messed up safe with slow here, anyhow edited repeat:
since i upgraded to 3.12 (been away since cmud 3.03, which btw had no such issues) when speedwalking by using doubleclick on map mapper in 99% does not follow the speedwalk (which is generated and sent correctly) - mostly just moves one room from start position
this happens only in SAFE mode, SLOW mode seem to work fine. also when entering path like .uene3s etc it will follow fine as well, problem occurs only when using mouse in safe mode

now, i probably posted (most of) this before...
#pause does not confirm slowwalk step (does not update the mapper) -- since zmud
%walkconfirm does nothing
#path output 'path behind' shows directions doubled -- (since zmud)
direct access to path ahead and (fixed) path behind would be mighty useful
using #step .xxxx during paused/stopped slowwalk messes it up, it will add and process them, but when it should resume old path it will send directions without confirmation -- (since zmud)
#tag prompt should be interpreted as actual prompt, not aid the mapper pattern detection, or special command for that purpose should be added (for all those who play or would like to play with gagged prompts), i would really, really appreciate this one Very Happy

example1: #slo .ne3w;#STO
#path:
Path Ahead: ne3w
Path Behind: .n

example2: #slo .ne3w;#PAU
#path
Path Ahead: e3w
Path Behind: .2n

neither updates the mapper, neither makes much sense...
master z, these can actually be useful Smile

Apprentice Joined: 18 Feb 2007 Posts: 190

bump due to edit

Posted: Tue Jan 19, 2010 12:05 am

If SAFE mode is not working, that means CMUD cannot detect any matching room name being sent from the MUD. Go into your Mapper configuration and check some of the options such as whether the room name is required to be at the beginning of the line, or the end of a line, etc. We need to see more of your mapper configuration to help more with this. In general it doesn't sound like the mapper is properly configured for your MUD and that is causing many of your problems.

The #tag prompt should be working as you desired and tells the mapper to go ahead and process any pending map information that it has detected, or to use any other #tag command results. However, there are additional options in the mapper configuration, such as waiting for a newline that could also impact this.

Apprentice Joined: 18 Feb 2007 Posts: 190

all modes are working when moving manually, with #slow or by .path input, but safe does not - ONLY WHEN USING MOUSE, indeed location trigger is updated incorrectly, (it is being set 2 rooms ahead, yet never triggers, but mapper updates position to first step when last room is received from mud... )

hmm, i tested #tag some more and it seems to do so, however not when in room creation mode...
all this is mighty hard and tiring to debug, it would be great to have script debugger option to display only things affecting mapper

further testing in debugger shows SECOND step immediately gets confirmed upon matching roomname with wait for prompt enabled

fe. #slo n3w
sends n
before #tag prompt it receives #pause
now i manually issue #step
w is sent and as soon as location trigger fires next w is sent without waiting for #tag prompt

Posted: Tue Jan 19, 2010 6:00 pm

Does using the #WALK command work? Double-clicking on a room should be the same as using the #WALK command unless the Track Location between the map window and your #location object is somehow messed up.

A lot of this stuff with #tag and map configurations and putting map info into the debugger is planned for the Phase 2 of the mapper work, so you'll probably need to wait for that before we can make real progress on this. Right now my focus is on bugs that are common between CMUD and TeSSH.

Apprentice Joined: 18 Feb 2007 Posts: 190

nope, it doesnt, #WALK behaves in exactly same way

cheers, i hope they aint many to go Cool