Zugg Software :: Search

if the value for those increments is 0, they don't show
this is expected behavior

Stand-alone antivirus software is often more trouble than it's worth these days, so yes, it well could be.

I would just insert the carriage return client side instead.

Something like this should work:

<trigger priority="10" newline="false" prompt="true" id="10&qu ...

That adds no new information.
You are overcomplicating things.

There is no need for you to use both %ismember and %match here.
One or the other will get the results you seek.

also, remember to ...

or give it an ID and toggle it on and off as needed with
#T+ ID
#T- ID

ditch all the quote marks, you only need those when passing a string, you want these values to evaluate
also, you only need %ismember, %match essentially expects a trigger pattern, which you arent pr ...

Could just toss the pipes back in as literal characters, might need to escape them out ~|

Unless you have a table with a similar output, you might be able to simplify to a single trigger state

<trigger priority="544960" repeat="true" id="54496">
&l ...

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