Zugg Software :: Search

A minor bug that's been around since we gained the ability to put wildcards in triggers of the type {a|b|c}:
Even though it's acceptable syntax for a trigger to be, say, #TR {^You see a {red|blue|% ...

You might also try EACCESS.PLAY.NET|GS3. For a while, |GS4 was going to the beta test server (no longer active), while |GS3 was going to the actual Gemstone server.

I don't know if that is still t ...

> #TRIGGER {{a|b|c|d|e|f|g|h|i|j|k|l|m|n|o|p|q|r|s|t|u|v|w|x|y|z|A|B|C|D|E|F|G|H|J|K|L|M|N|O|P|Q|R|S|T|U|V|W|X|Y|Z}} {#WIN GSL {%1 %gsl( %1)}} "" {gsl|case}

Is there a reason not to just use som ...

%ismember is for items in lists, not portions of strings. You want %pos, e.g.,
#TRIGGER {P} {#IF (%pos( N, %gsl( P))) {#VAR stalk 1} {#VAR stalk 0}} "" {gsl|case}

There's a fairly comprehensive ...

There are a couple of different ways you can do this.

One is to split the triggers up into different classes. Another is to set variables for each character, and check them during execution of a t ...

There is the #wait command, e.g.,
#SAY First line
#WAIT 5000
#SAY Second line
will pause five seconds between those two commands.

However, #WAIT has its own set of problems, and is generally ...

Sure, but the problem is that there's not *always* a prompt before or after the gagged line--if there's a lot going on, there might be a few lines of text sent between prompts, in which case I don't w ...

> does your prompt contain the ">" ?

Let me explain further:

The text displayed without any gagging:

* Joe just joined the adventure
>
* John returns home from a hard day of adve ...

If you have other triggers which change the statequilibrium variable as needed, you could use a #TEMP trigger, e.g.:

#ALIAS sh {#IF (@statequilibrium) {get arrow from quiver;nock arrow on bow;shoot ...

My dilemma is one that I'm sure has come up before, but after trying a number of different methods without solving it, I'd thought I see if I were overlooking something basic.

The problem is gaggin ...

As a separate issue, I recommend generally naming temp triggers. Why? It stops you from potentially ending up with multiple temp triggers all going off at once.

For example, in the above situat ...

#STOP is broken in 6.67.

If you're looking to slow down the movement, I'd suggest using alarms, e.g., instead of #TR {You see exits} {#OK} try #TR {You see exits} {#ALARM +0.5 {#OK}}

If you need ...

I ran into a similar problem, where the culprit was Zmud running out of memory.

This could occur in at least one of two ways: A faulty process taking up 99% of system resources, leaving nothing for ...

Try:

#TRIGGER {HP:%s&%dHP} {#IF (@HP<45) {get @food;eat @food}} "" {nocr|prompt}

The last set of options defines this as a prompt trigger, not waiting for a newline character.

Depending on ...

> also if I just want the right most word in each string item, is this possible as well?

One way to do so would be this, though there are likely more elegant ways out there:
#LOOP %numitems( @l ...

This seems the longest way possible. Is there a reason not to use something like:

#TRIG {Roundtime: (%d)} {#CO red,bold;#VAR blah %1;#ALARM +@blah {a1}}
#AL a1 {#IF (@countwaiting < 1) {#VAR c ...

You might find the section on advanced triggers helpful <http://www.zuggsoft.com/library/trigadv.htm>

What you're looking for is something along the lines of:
#TRIG invTrig {backpack ~(used~ ...

Text wrapped by Zmud is not considered multiple lines, i.e., assuming appropriate settings, the mud is likely to send "You look ... towards you!" all as one line, which is then word-wrapped by Zmud.
...

Without knowing where these variables come from, or what is triggering the above, it's tough to say.

I'm also not sure of what the problem is. An alarm of the type #ALARM +X {blah} is *supposed* t ...

This looks like I'm just not finding the right syntax instead of being a bug, so posting this here instead of the beta forum.

I'm trying to use %match for a trigger pattern involving a list variabl ...

In Gemstone, I'm having a problem with lines not always being preceded with line feeds, which means that I get text occasionally appearing on the same line as my prompt, e.g.,

>
Joe just arrive ...

Any suggestions on an alternate way to accomplish this?

Here's my attempt, but it seems a bit inelegant:
#TRIGGER "pulseTrig" {r} {#T+ pulsefailsafeTrig} {gsl}
#COND {r} {#T- pulsefailsafeTrig} { ...

I can't seem to find a way to use trigger type options with gsl triggers, and was hoping someone could suggest a way.

Here's the issue:
In Gemstone, the GSr code is sent at two types: when field e ...

> Valint, is your alias actually working?

Yes. The alias does, however, have some added linefeeds for readability, so you will have to edit it slightly to remove those extra spaces before cutti ...

Occasionally, I will want to sort numbers as numbers, rather than alphabetically as text, e.g., I want the sorted list to be 1|3|10 not 1|10|3. While I created an alias to do so, this seems a bit clu ...