Zugg Software :: Search

The button variable has nothing to do with the state, by default anyway.
So this is expected behavior.

Usually that is a display value, for gauges and what have you.

If you are wanting to refer ...

If you set the ID field of the button you can do:

#STATE ID 2

Here is a cleaner version, that only suppresses matching data for 10 seconds

#ALIAS scroll($pattern) {
#WAIT 0
#IF ($pattern) {
scrollPattern=$pattern
#SCR ...

There was an issue with emails months ago that has since been resolved.
I would not be at all surprised if your last email was lost to oblivion, but if you try now, I presume you would get better res ...

P.S.
Indefinitely long aliases are likely just as against the spirit of your game's anti-trigger rules as literal triggers are.
Just like an auto-clicker on a button would be.
The concept applie ...

This is actually a legacy problem.
Display technology as progressed very quickly since CMUD was last in development, and the real issue is with the resolution of a given monitor. Or more precisely, h ...

You could try something like:

#C+ windowname
#GAGON
#SC pattern
#WAIT 10000
#GAGOFF
#C-

The wait time might need adjusting, that is only 10 seconds.

Perhaps you need to reorganize how you approach botting.
Rather then a single script that runs indefinately performing actions every 10 seconds....
Make a script that randomly performs a single acti ...

Highlighting the route in red (#PATHHIGH) is normal expected behavior when speedwalking.
This can be disabled in the mapper configuration.

I cannot think of how you got to the state you are in, th ...

Identifying it is tricky.
There is no real fix besides reinstaling.
You might be able to save your settings with an XML export.
It's in the file menu of the settings editor.

DB variables are great, however, there is an issue with using DB variables in the headings of buttons and gauges where the updated value doesn't always update in the display.

Think of them as more ...

1.
Have you ever run CMUD as an administrator?
I suspect that lack of write permissions is why some settings arent being saved.

2.
You can turn of some of these things from the advanced tab of ...

#TELEPORT works if you just need to update the 'you are here' dot on the map.

Sounds more like an issue from opening CMUD before windows had finished loading.
Try simply closing and restarting CMUD, or rebooting.

Its usually more a matter of sending the right command to the mud so it knows to send those codes for CMUD to process.

You can just use a small resolution to bypass that, which is fine if you have a monitor that you can dedicate to sub- 4k or even HD graphics.

To use a variable in the pattern just wrap the variable in an extra set of curly brackets.

#TR {test pattern looking for a member of ({@stringList})} {#SAY %1 is the specific item in the list}

...

If that is the actual disired result, your original trigger will work with my script body.
It looked like a potential error is why i separated them.

If i am understanding right, that may have thrown off your count.
Do both lines display when your skill improves?

If so you should be using something like:
#TR {^You concentrate and constric ...

Not in CMUD natively.
But if you have a means to fire one in lua, or some other installed language on your system... potentially.

I will let Chiara know.

It is possible, but you need to insert an anonymous variable ({str1 | str2}) in the brackets.

#WAITFOR {{str1 | str2}} 3000 {do something if found} {do something if not found}

I logged into the game to see for myself.
Several of the exits are bugged in that they sometimes skip over rooms.

For example, you are going east through rooms 1-2-3.
Yet, going west from room ...

Usually the #FIND command will try and figure out where you are, short of that, you have to manually select a room, and then click the blue pushpin button to set that as your current location.
So lon ...

you can always manually set it if the TAG wont take
#NOOP %roomvnum(, %2)