Unless you sell a tinyfugue system, buying your systems for xxx cr is not worth it. You'll probably use nifty zmud multi-line triggers or stateful stuff because it really would make this much easier, and I can't do that in tinyfugue.

Oh, and I'm an open source developer. I'm quite happy to spend more time reinventing the wheel and learning along the way than pay someone something for it.

Trouble with this is that the first line isn't anywhere near enough to tell me whether it hit me or someone else.

buy mine, i'll include a complimentary version of zmud!!!

Which won't work.

You'll never drive Morik away from TF, never. Trust me!

Cool. can you throw in a complimentary PC laptop? My silly mac laptop doesn't run Zmud too well.

(Yeah, I have zmud. It runs on my Windows machine. That thing I use for Java development, some Visual Basic crap, and guildwars. Yup, Guildwars.)

#tr {Flourishing a dragon-hilted claymore above} {#var knightposs 1}
#tr {you} {#if (@knightposs) {#t+ knight;#var knightposs 0}
And on prompt reset the knightposs variable is how i'd do it.

My method is similar to Laysus' Except instead of using a variable. I turn on the trigger on the primary messages, and turn it off again on prompt.



Then I just have a folder(parrycheck) holding all the body parts as seperate triggers, wrapped and not wrapped, which tell me which area to parry. Plus a seperate folder containing the wound afflictions(Wound_Afflictions) that pretty much does the same thing.

I haven't yet had a problem with missing a parry, other than due to my just not having the primary set right. There likely is better ways to do it, but I am happy.

That method never works for me. The folder always opens after the line is received, and by then, the knight attack is usually finished.

Yeah, I'm trying the same thing on JAVA with #if formulae (#group s seem to be broken), but the variables change too slowly for it to work. (I cut it down to two variables, and had to ignore those people with stupid long weapons that went over a whole freaking line for the strike message ( ) but it still didn't work.)

That's the one and only, best way to do it, using variables will have the exact same result, except much slower, since you have all these triggers active.

The reason for this is, as example:

some message:

"Oogle blah you and abloogle." ... now, if abloogle is the affliction, and the message class is only enabled after "Oogle blah".. the affliction won't get tracted.

Now if you use a variable that gets set to 1 when you see "Oogle blah".. and then only accept the affliction when said variable is set to 1, the affliction won't get tracted either. Which you can test for yourself if you like.

However, the second method always has all triggers active, resulting in slowe processing, the first method doesn't, and is therefor the preferable method.

*points at his post*

Yeah, but thats a really, really long function. I have this .. desire for elegance. I'll see what I can do.

But thanks though. I'll post what I determine.

This should be fixed if you make the trigger fire on 'prompt' instead of 'newline.' (This can be changed in a triggers Options in Zmud).

At least that's what I'm hoping. I was having the same problem, changed every to prompt last night but haven't had a chance to test it.

You called my work unelegant! I want you to show me this so-called elegant function of yours when you're done!!! NOTE: It has to be reliable, track atleast 40 different afflictions, echo alerts and be shorter than mine! *snort*

You missed the + after the pattern. It captures one or more of them, so you can have a space AND a newline. If you want to be even more specific, make it match on 1 or 2... (?: |\\n){1,2}

Cool. I'll patch tinyfugue. I've been wanting to implement proper multi-line regular expressions for a while..

Hah. crap. I should really concentrate on passing lingustics/psychology before I patch tinyfugue. Maybe next weekend.

But yeah. Multi-line regular expressions, even limited to the last 5 lines, would really, really make matching this stuff so much nicer.

(Where I say multi-line, I mean "consider the last 5 lines as one long line with no character returns. Yup, one long string. Now, match this regular expression on it.")