Zugg Software :: Search

Is the OS registered in the same name as CMUD?
Not sure why that would matter, but that's what it sounds like might be the issue.

The numeric ID is actually the priority in which settings execute, should any given thing cause several settings to go off simultaneously. (lower goes first)
I have no idea why it isn't labeled as su ...

The ID needs to start with a letter is the issue here, fully numeric IDs are not supported.

zMUD is truly ancient and was never guaranteed backwards compatibility at this point in time.
You might be able to get it run in an emulation of older Windows OS.

CMUD, however, is known to work o ...

There is a link to all the wildcard characters in #HELP #TRIGGER

You can either edit the xml directly, id="PartyChecker"

Or you can click the 'More' button at the bottom of the package editor window and just fill in the panel labeled ID.

General speaking, there is no real 'best' way to do things, just a bunch of tools in the toolbox

The #HELP command can be used with any command or function to read the help files

#HELP #MATH
#H ...

The #MATH command has been officially deprecated and made redundant, any equation in parentheses will try to evaluate itself, use nested parenthesis when you need to force order of operations.

usin ...

You can do that.
You need to give the trigger an ID of "PartyChecker"
then your button will do the following:

#SWITCH (%trigger(PartyChecker))
(0) {#T+ PartyChecke ...

Correct, it never saved the changes you made cause it didnt have write permissions to write it from local memory to the HD.

#CONDITION on its own will attach to the last defined #TRIGGER, therefore it is recommended to only be used from the command line when first creating a trigger.
It should never be in the body of a tr ...

Ah yes, you need to run CMUD 'as an administrator' at least once to give it write permissions.
Just right-click on the icon and you should see the option.

Are you sure you have the correct address/port info where you are trying to connect?
Might have edited it by mistake when checking settings.

You need to have made a separate session for each character for it to work best.
And even then, each session will be its own window or tab.

If it's just a matter of layout, you can drag each separ ...

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 ...