Zugg Software :: Search

The magnifying glass will send a #LOOK command, to reset the room description (if the map is in mapping mode).

The binoculars send the #FIND command, which will try to match the output of a 'look' ...

Try using %cr instead of <BR>?

Not crazy at all, you can even do it in-line:

#TR {(your special phrase)} {#SUB {<send 'default command|command2|command3' 'mouseOver|titles|are shorter'>%1</send>}}

I'm not sure how that is adding anything new to the problem?

Where the other variables get declared, doesn't matter, so long as the values are correct at runtime. (which you can test with #PRINT)
...

right click in the main window
window options
show command line

skxprd=(@skxprd+@gxprd)

Would be doing what you expect.

If you add two static values, the sum will stay the same every time.

Are the two values supposed to be changing?
You didnt give any triggers to show how.

Not enough information to go on.

Honestly, i think thats just a quirk of the ansi coloring system.

Have you tried migrating to MXP?

#SAY <color gray>This is gray</color> <color green> This is some green with a ...

#TR {~((%d)~) a quest chit} {questChit=%1}

then you can edit your #STW object to use @questChit

Local variables get flushes automatically with the closing curly brace.
but for a standard variable list:

itemList=%null
will clear it, or you can use #UNVAR to delete it

You can also give the ...

<trigger priority="539480" id="53948">
<pattern>You are currently holding:</pattern>
<value>//Reset stuff goes here, if needed</value>
&l ...

okay, so $var indicates a #LOCAL @var
i.e, a variable that only exists within the {brackets} it is defined in

very handy for data you don't need to save past the now and is only being defined for ...

The trigger type of within lines, along with param, tell it that the condition is active until x lines have printed to the screen before the trigger state updates.
The #STATE command is playing off t ...

Here is the XML of a trigger:
<trigger priority="539480" id="53948">
<pattern>You are currently holding:</pattern>
<trigger type="Within Lines& ...

Basically, you wanna convert both dates into pure seconds, do basic math on the seconds, then convert the sum, back into an easy read span.
The latter of which i helped do in a [url=http://forums.zug ...

I think you are just missing a closing brcket for the while?

Did you use the check syntax (ctrl+k) option under the Editor menu?

#SAY %time
defaults to:
Monday April 7, 2025 11:07:56 am

or you can make ity output according to your needs

#FORALL {a|d|m|y|e|c|t|h|n|s|z} {#SH %i: %time(%i) | %time(%i%i) | %time(%i%i%i) | % ...

Yea, that is unlikely to give a false match.
Doesn't really change how I would approach the problem, though.

Whether you use a bunch of if statements, or a database variable, you are still working ...

But I would design a trigger like this off of a variable.
In this case it would be key=value pairs, which we can preload with your known values like so:

#ADDKEY mobList {A spiral Gun=gun|A Groma=g ...

I am guessing this could do with a better pattern then just *, then you could use the repeat within line checkbox, or perhaps use the comma delineation to better establish your count.

Can you show ...

%time can spit out the current time in a number of ways
#HELP %time

once you have the two times, then you have to do time math

You need to wrap the equation in parentheses for it to evaluate.
This is also true of the #IF statement for best results

$monsters = ($monsters+1)

#IF (%ismember(@monster, "Galga|Zamuza|Balba|B ...

#TR {^>> } {#CAPTURE Familiar;#GAG}

That should redirect the familiar content to another window.

there is a map conversion tool for this very purpose [url="http://forums.zuggsoft.com/forums/viewtopic.php?p=153634#153634"]pinned in the CMUD beta section

No, i had left another typo in