This is really only useful for monks to know about that are as dumb as I am.

^(%n)h, (%n)m, (%n)e, (%n)p, (%n)en, (%n)w (*)-

That was the original trigger, which I couldn't get working (the problem was for an auto-sipper), and it was because I had forgotten about momentum appearing in the prompt while fighting/bashing, which was causing the prompt trigger to not work.

I'm unsure if this is the ideal solution (probably not), but it works to just do this:

^(%n)h, (%n)m, (%n)e, (%n)p, (%n)en, (%n)w* (*)-

Actually I do have a question...for some reason, the prompt trigger doesn't work until something appears -after- it. So, if I get hit and then nothing happens, I won't sip until I QL or another line pops up after the last prompt. Any way to fix this and make it so the prompt trigger always goes off? (I'm on Zmud)

Edit: Yaaaay thanks Ardmore

You've removed the code already (no idea why, since it might help others to read this stuff later, but whatever), and I just wanted to point out that you want (%d) instead of (%n). The %n is used for matching numbers with commas (i.e., 1,234,567).

Check the "prompt" checkbox on the trigger's options.

Ah, didn't think it might help someone else. I'll edit the original post back. Also seem to have been given some wrong information a while back, I was told %n was for all numbers. Thanks!


And completely forgot that existed, much obliged!

I think I'm just going to use this as my 'oh god help' topic.

So because deaf/truehearing aren't differentiated in any way besides on def, which I'm not about to do every time I diagnose and my system sees 'deaf', I put in my queue {#if (@deaf=1 AND @truehearing=0) {cure_deaf}}

The problem? Deaf=1 because of diagnose/prompt trigger. But truehearing=1. And yet it's still trying to cure deafness, even though truehearing=1 and not 0. It's confusing the hell out of me.

{#if (@deaf==1 AND @truehearing==0) {cure_deaf}}

Try that?

Oh lordie, I'm a newb.

It was trying to cure something else.

NOTHING TO SEE HERE. AGAIN. D:

That did work though!

What exactly is the difference between #REGEX and just putting it in as a normal trigger?

For some reason:

^With a quick spin, you kick * with your right foot.
^Slashing viciously at *, you rend {him|her|it} with an iron nekai.

These triggers did not work when put in from a script using #REGEX, but when just putting them into the system as a regular trigger (just hitting triggers, new, then typing all the stuff in) made them work perfectly fine.

It's to do with the type of matching your client is using. I don't use zmud, but I'm guessing from the look of it that the default for your triggers is "glob" matching, where the "*" character matches any number of characters. But in regular expression matching, "*" matches any 1 character. You'd need "(.*)" in the regexp version.

Syntax, and REGEX is a fair bit more accurate, I think.

Each of those * needs to be replaced with (\\w+) in order for regex to catch a word. Likewise, the choice part should be "...,you rend (him|her|it) with (\\w+?)" I believe. Otherwise when you change nekai it's going to stop working altogether.

EDIT: or what he said.

Actually, Aerotan's syntax may be better than the one I listed. I'm just lazy and use (.*) for lots of things, but (\\w+?) is more specific and less greedy!

Big thanks for all the answers! Much appreciated.

How do you correctly use #add for variables?

Specifically, trying to make an abashing counter. So triggering siphon message to add 1, death message to subtract one.

I thought it was just #add @variable 1/-1, but that's not working.

Edit: Nevermind, not supposed to use the @.