Zugg Software :: View topic

Beginner Joined: 04 Apr 2004 Posts: 17

perhaps i didnt give enough details last time, because i am using the latest version and there is no way this should be buggy. ill try to elaborate.
1 2 3 4
a 0-0-0-0
| | | |
b 0-x-0-0

so we have 8 rooms. in room b2 there is an orc. it looks like this:

The plains(w , n ,e)
An orc
~HP:50>

i make a trigger:
#trigger {orc} {#pause}
here is what happens if i fire #sl .senesen from room a1 (mapper is in slow mode)

1) s is sent to the mud. i get moved s on the mapper
2) e is sent to the mud. i get moved e on the mapper. Slow walk is paused. i do my stuff. i type #step
3) n is sent to the mud. i get moved n on the mapper
4) e is sent to the mud. the mapper doesnt move me
then the whole thing freezes up
can anyone help?

SubAdmin Joined: 18 Nov 2001 Posts: 5182

By "the thing freezes up" do you mean all of zMud freezes/locks or just the mapper? If it is just the mapper then you may want to do some testing to find out what state it is in. The main functions to test this are %walkactive, %walkconfirm, %inwalk, and %lastdir. I found it very useful when building some of my more complex door scripts to have the status of these functions displayed onroomenter, with my prompt, and even at different points in the triggers. The results of such tests should be beneficial since the use of the #SLOW command with the mapper also active was a small concern during the latest updates to the mapper. I am unsure how many beta-testers actually use that combination so it is possible a bug slipped by.

Beginner Joined: 04 Apr 2004 Posts: 17

the walk stops because the room name doesnt get confirmed and the mapper keeps me in a2
the statuses are as follows:
a1: nextdir = s
lastdir = s
walkconfirm = 1
inwalk = 1
walkactive = 1
b1:nextdir = s
lastdir = s
walkconfirm = 1
inwalk = 1
walkactive = 1
b2:nextdir = e
lastdir = e
walkconfirm = 0
inwalk = 1
walkactive = 0
a2:nextdir = n
lastdir = n
walkconfirm = 1
inwalk = 1
walkactive = 1
a3(mapper thinks i am still in a2):
nextdir = e
lastdir = e
walkconfirm = 0
inwalk = 1
walkactive = 1

typing #ok when the walk stops (when i am in a3, or as the mapper thinks it a2) takes me back to b2 on the mapper.

Beginner Joined: 04 Apr 2004 Posts: 17

basically the way i get around it is by triggering on the orc not #pause, but #show %walkconfirm(0) and when i finish my buisiness in the room {#show %walkconfirm(1);#step}. but i dont really understand why #pause which is designated for this purpose isnt working