Zugg Software :: View topic - [3.34] Pattern Matching String List Priority?

Novice Joined: 16 Apr 2008 Posts: 37

I've got one trigger that I'm trying to use to capture every attack message with and parse out the mob name. Here are the 2 relevant message that it cannot parse correctly.

You obliterate A Dragon Warrior with your pierce.
You massacre A Dragon Warrior to small fragments with your pierce.

I've tried a few triggers...

Posted: Tue May 24, 2011 4:51 pm

All the examples you have included always have "with your" although I see one of the lines in the string lists says "from your", I'd be inclined to test the following:

^You {miss|utterly annihilate|remove chunks of flesh from|obliterate|massacre|make} (*){to small fragments|see stars with a terrific wallop|} {from|with} your {slice|pierce|hit|slash|crush|hack}.$

This assumes each line always has a with your or from your in it which itself follows the multi word mob name with either nothing or an extra phrase.

You obliterate A Dragon Warrior with your pierce.
You massacre A Dragon Warrior to small fragments with your pierce.
You make A Dragon Warrior see stars with a terrific wallop from your slash.

All the above examples tested as working with the given pattern, note the lack of space between (*) and the following string list in the pattern, meaning you will have to process %1 with a trim so use something along the lines of #var mobname %trim(%1) in the script portion of the trigger.

If this fails other combat lines then provide those as examples so the trigger pattern can be refined.

Novice Joined: 16 Apr 2008 Posts: 37

Ah, didn't even think to split up "from" and "your", good thinking.

Although I'm not sure all possible messages can be lumped together into one trigger, here they are, in case you can think of a way..

Your tremendous pierce sends gouts of blood and gore showering from A Dragon Warrior.
A Dragon Warrior's bones crumble under your terrific pierce.
Your pierce makes A Bushi Guard think twice about his continued existence.
You make An Elite Guard see stars with a terrific wallop from your pierce.
You remove chunks of flesh from A Dragon Warrior with your pierce.
You obliterate A Dragon Warrior with your pierce.
You massacre A Dragon Warrior to small fragments with your pierce.

That isn't all of them, but it covers the range I'm capable of hitting, so it should suffice.

Posted: Tue May 24, 2011 5:02 pm

Does this pattern work?

Posted: Tue May 24, 2011 5:04 pm

and no, those will not easily fit into one trigger... not easily, you have three basic sentance structures though.

Novice Joined: 16 Apr 2008 Posts: 37

Posted: Tue May 24, 2011 7:02 pm

Sorry about that I forgot about the * being greedy and grabbing what it can until it no longer matches, that whole string list can be removed from the pattern.

Trigger Pattern: ^You {miss|utterly annihilate|remove chunks of flesh from|obliterate|massacre|make} (*) {from|with} your {slice|pierce|hit|slash|crush|hack}.$
Trigger Code: #print %remove("see stars with a terrific wallop",%remove("to small fragments",%1))

It isn't particularly pretty but if you are solely after the mob name then that is what you get. If there are many more of these to match then put them in a variable and do a #FORALL.

Novice Joined: 16 Apr 2008 Posts: 37

Yeah, that's essentially what I've got it doing now, I'm just using %replace instead, but I guess that is cleaner. Still, not pretty, stupid greedy *. I'm guessing there really is no way around it when you've got a string list with a blank value following an *.

Posted: Wed May 25, 2011 1:08 am

not without breaking down and doing a true regex pattern... but i am no good at those.... have you thought about just having multiple triggers?

Beginner Joined: 27 Dec 2008 Posts: 14

Yeah, multiple triggers would be easier, I'm just trying to combine as much as possible, where possible, to cut down on performance issues, which I've got more than enough of. It's more of an issue of principle than anything, it seems like I _should_ be able to do it in one trigger, except for the fact that * in a pattern makes it grab as much as possible, which in this case is simply counter-productive. I guess a second trigger is no more of a performance hit than processing multiple %remove functions when it does trigger.

Posted: Wed May 25, 2011 2:57 pm

In regex:

Beginner Joined: 27 Dec 2008 Posts: 14

Beginner Joined: 27 Dec 2008 Posts: 14

Seems like I figured it out....

Posted: Wed May 25, 2011 5:20 pm

For starters, you can change the You? in my trigger to just You (since I thought it could contain 'Your', but I was mistaken in the syntax anyway).

Second, your code definitely is messier than it needs to be, but you're attempting to learn, which is what I started out with. I had messy codes for a while myself, then I learned how to make them more efficient. I'm a bit busy right now (read, in excruciating pain right now...) so I'll have to help rewrite the regex later. Look up the program regexr. It's what I use when testing my regular expressions, and it's quite a handy tool, not to mention it teaches you a bit. Also, look up regex cheat sheets.

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

Posted: Wed May 25, 2011 8:15 pm

Yea, i have taken the route of using several single line patterns that all run the same event.

Usually different damage messages = different ammount of damage, and i have been known to want to track those as well... lots easier when they are seperated.