Zugg Software :: Search

So the key word "travel" is a portal command, so "travel klevnone" will travel to room 394. In the mud these portals are set up all over the place. So other then there being a portal in 394 with the v ...

Script Debug >< This is the main instance where everything fails. This zone is entered through another zone. I issued the command l to look, then move one south, then attempt to move to the ques ...

Sorry for the delayed response, I was out of town this weekend for my birthday.The room trigger in 339 looks at the value of a quest timer, if that value is ! the command to complete the quest is issu ...

I am using v 3.31

So there is only one room trigger, there is a lock surrounding the ability for the trigger to fire normally (used to prevent never ending loops), but I have removed it for this e ...

I have been combating movement errors for a long time now, and I am starting to get a bit frustrated; I need some help.

1. When I double click a room on the map some time the path generated by cmu ...

Personally have uninstalled and reinstalled the packages, and the program a few times now; the problem persists Crying or Very sad

. I have sort of given up on this problem and its cousin #step sending all the ...

This bug has been around for a while, I run into it a few times a day. There is no know fix, as it seems only a few people seem to have the problem. I have noticed that if I avoid clicking on the map, ...

Weird, considering the type is Database record. Oh well sorry.

This command works for me.

#show %match(@drMobs,"A giant centipede is here.")

@drMods is the name of the data record variable that holds the desired information
"A giant centipede is here." is ...

Sure the command you are looking for is #walk roomnumber

<alias name="whatEver" id="188">
<value>#walk 999</value>
</alias>

Just replace the w ...

Thank you for the suggestion.

In slow mode on the map:
#slow .20n20s;#pause
The first step is one north, then when #step is sent the second time 2-8 n's are sent to the client before pausing ...

Maybe I asked to much #STEP n2es
sets "n2es" as the current path, then sends the North command to the MUD as the first step. The next #STEP command would send "east", and so on. "
This is ...

Currently I am working on a script that relies heavily on a walking bot, however I am running into a real issues with how to approach this correctly, if there is a correct way.

The basic idea here ...

I have the same problem, I have had to use #STEP;#PAUSE

Is there a way to clear a queued path, for example if is queue a path like #64e, but then I need to clear out the path at 4e and queue a new path of sew, I have played with #STOP but this does not emp ...

Yes I am using a variable as a bool named pathBool, and it is either 1 or 0. The script compiles now thank you! But it does not work as intended. When I am standing in the room if I enter

#STEP 2s ...

So I have a script that should fire when ever I enter a room

#IF (@pathBool) {@pathBool=0
#STEP 2sl5e4nwe2n3e4s6w4n2e2w4s3u4n6e3wsw2ewn3w4s3d3e2s5wh2n
#PAUSE} {
@pathBoo ...

That worked... Shocked

I swear I tried that. Embarassed

To resolve an earlier issues I added a carriage return after the last character in my prompt. However now the trigger that captures and stores my gauge variables no longer functions. To be clear the p ...

Turns out it was not the mappers fault at all, there was a missing carriage return which would sometimes cause the name of the room to be on the same line as the prompt.

I have my whole mud mapped, but I have never been able to make the mapper work with any setting other the fast walk. A script I am working on requires room triggers to work correctly, and to do that I ...

No I have not had to.

After a lot of testing I have made a little progress.

In the mapper if "disable automatic confirmation" radio is selected, the mapper is set on fast walk mode, the path is sent in as #STEP n2e5w, a ...

Got it.

I am in follow mode, and have tested fast, safe, slow, and toggle the map on and off. Currently I am using 3.30; should this be taken over to the beta forums. I did not think there was a bug, just tha ...