Zugg Software :: View topic

Adept Joined: 18 Jun 2019 Posts: 279

Here's an example:-

Posted: Tue Aug 18, 2020 9:27 pm

Well, there is no way to tell which items are containers, that I can tell.
I mean sure, we know that pouches and bags are containers, but we have to tell code somehow.

#TR {{~( ($num:%d)~)|}%s{~(Magic~) |}{~(Glow~) |}{~(Hum~) |}{~(Invis~) }|}($item:*) ~(($level:%d)~)} {Do stuff with $num $item and $level}

If it has the (K) it should not match this trigger.
(Invis) may be in the wrong order if it can appear with other tags.

Adept Joined: 18 Jun 2019 Posts: 279

I think the order is fine...however, not all items invis are humming, not all items that hum are invis, not all items that are either glow.

The containers part is not THAT important as I factored a trigger for "you cannot put <a> into <b>"

However, the documentation stipulates that negated patterns can be used although I am not sure how that works in a trigger.

So, is it not possible to

#TR {search pattern {^sub-pattern} rest of pattern} {actions}

in the trigger?

Posted: Wed Aug 19, 2020 11:11 am

Those are all optional tags via:

{~(Glow~) |}

That is an anonymous variable with a null member. It will match weather "(Glow) " is there (with the trailing space), or not.

And yes, negated subpatterns can be used, if you are having an issue with too many matches.
For example:

#TR {"[^"]"} {#CW aqua}

That tells it to look for two quotes, without any quotes between them, to properly match speech and color what was said.