Zugg Software :: View topic

Apprentice Joined: 23 Aug 2013 Posts: 175

HP: 1971/1671 SP: 642/642 STS: 0/63% (V) (B) (P:A) Enemy: 93%

HP: 1971/1671 SP: 642/642 STS: 0/63% (V) (B) (P:A) (STS) Enemy: 93%

HP: 1971/1671 SP: 642/642 STS: 0/63% Enemy: 93%

Is there a way to make 1 trigger for all 3 of these? The (V) (B) (STS) show up as the skill; is used, so it disapears and i've had to make 3 different triggers to make sure i have variables going for hp's etc...

Posted: Sat Jul 25, 2020 9:07 pm

Anonymous variables with a null member are your friend:

#TR {HP: (%d)/(%d) SP: (%d)/(%d) STS: (%d)/(%d)% ({~(V~) |})({~(B~) |})({~(P:A~) |})({~(STS~) |}) Enemy: (%d)%} {stuff}

Apprentice Joined: 23 Aug 2013 Posts: 175

It didn't work, not sure why, i do see what you mean by anonymous variables however...

({blah|blah|blah|blah})

Apprentice Joined: 23 Aug 2013 Posts: 175

Also: how would i create a trigger (multi-state?) to capture sequential instances of same pattern, and record them seperately?

CS: Vr: 3043 Tl: 1891

CS~:%s~[~[(*)~]~]

(multi-state)---> within lines

(%w)~:%s(%d) <---- but it only captures the first one in the capture, and i need to capture all instances, and then record them seperatly

vr: 3043 AND Tl: 1891 so i can call them up as they reach a certain point....

i sort of got this to work with clicking the within line portion in trigger, however "loop lines" is picking up stuff from other lines i dont want....isn't there a way to set #cond for it to expand to state 1 etc and then close? i dont remember all this

Adept Joined: 18 Jun 2019 Posts: 279

As with the documentation, you are supposed to be able to use a temporary trigger. However, I have had nothing but trouble with temporary triggers from day one.

In theory, the primary trigger should have a #TEMP {pattern} {commands;#STATE <state>}, and the condition would reset the state upon firing.

But all I seem to get is that the temporary trigger makes a permanent version of the pattern and commands...for as many times as it fires. Shalimar suggested naming TEMP triggers but that has had mixed results for me. Only 10 mins ago I had to delete 20 triggers that were made by a temp one, even though it was named.

Apprentice Joined: 23 Aug 2013 Posts: 175

yup, im having the same issues.... it will endlessly produce the "state" as a new multi-state each time it finds that pattern... i just need a way to as many times as i need to find that pattern AFTER the original pattern is seen, then stop looking for it. i guess i could use several triggers to #T+ and #T- but that would absurd as i need the variables to update each round..:|

Posted: Mon Jul 27, 2020 6:04 pm

#TEMP triggers are rarely #STATE based triggers.
Do not conflate the two.

#TR {pattern one} {do stuff} //this is #STATE 0
#COND {pattern two} {do more stuff} //this is #STATE 1
#COND {pattern three} {etcetera} //this is #STATE 2

The #STATE command is used within a #TRIGGER, to change which #STATE is currently active and waiting to fire.
Triggers usually only progress in a state when it fires, though trigger options can change this behavior.

Here is an example I use to get rid of server-side word-wrapping in my tells:

Apprentice Joined: 23 Aug 2013 Posts: 175

Posted: Wed Jul 29, 2020 8:27 pm

It might be easier to just reparse the contents of that double bracket via script:

Apprentice Joined: 23 Aug 2013 Posts: 175

that didnt #call anything up btw, and i tested with #print as well...

#IF %match(%1, "Vr: (%d)") {}

and your example, how do i capture the %d inside the match?!

Posted: Wed Jul 29, 2020 11:51 pm

Well you did not fully copy my %match function:

%match(%1, "Vr: (%d)", $vr)

all the #CALL does is evaluate the function, which in turn assigns the value %d to the variable $vr

Apprentice Joined: 23 Aug 2013 Posts: 175

Apprentice Joined: 09 Apr 2008 Posts: 168

I know you can do that with REGEX but not sure how it's done via zscript

CS: (?:|Vr:\s\d+)

will capture with or without the Vr: 1234 ... but assigning it as a variable if detected would mess with things

You would have to have some method of checking IF (%1 == Vr: %d) THEN {do blah} ELSE {shift %1 to next item and do blah}

Posted: Mon Aug 03, 2020 3:12 am

Yes, that should work.

Newbie Joined: 06 Oct 2021 Posts: 1

the primary trigger should have a #TEMP {pattern} {commands;#STATE <state>}, and the condition would reset the state upon firing.