Time auto attack with ACT

[Gummby8]

For all those classes that want to learn how to time their auto attack, the parser ACT can be used as training wheels. Simply mimic the settings found in the picture below and ACT will beep everytime you auto attack, critically or not.

[EQAditu]

I think the triggers are case-sensitive, so the capitalized C in critical may cause that one not to work. Furthermore, you will not detect when you miss. That trigger would be harder to create as CA misses follow the same pattern for more than half.

There's a plugin that wasn't made specifically for this purpose, but I point people towards it anyways.
Advanced Combat Tracker :: View topic - Single/Double Attack detection/notification v1.0.1.2

[Flec]

ACT triggers are very simple RegEx, so I don't see why you couldn't use:

^YOU hit (.+) for (.+) (slashing|crushing) damage.$
^YOU try to (slash|crush) (.+), but miss.$

[the_mo]

well.. ive considered using such a thing some times now.

the reason i didnt touch it so far was that ACT does not work real-time, so its possible when theres high cpu-load (generated from eq2), that you get the beep a whole second after it happened, so the whole autoattack-timing wont work as precise as it had to to be useful :/

[EQAditu]

Originally Posted by Flec

ACT triggers are very simple RegEx, so I don't see why you couldn't use:

^YOU hit (.+) for (.+) (slashing|crushing) damage.$
^YOU try to (slash|crush) (.+), but miss.$

I guess you don't like people with piercing.
Anyhow, the second Regex will still pickup CAs that miss as they follow the same format as your pattern. Furthermore you will not detect auto-attacks that are parried/riposted/etc.

PS. A period is a reserved regex character, so you should be using "\." in your examples.

Originally Posted by the_mo

well.. ive considered using such a thing some times now.

the reason i didnt touch it so far was that ACT does not work real-time, so its possible when theres high cpu-load (generated from eq2), that you get the beep a whole second after it happened, so the whole autoattack-timing wont work as precise as it had to to be useful :/

ACT by default(at least recently) has the parsing engine running at "Above Normal" CPU priority. ACT's GUI and EQ2 both run at "Normal" priority and will be pushed aside. ACT checks for new log data every 100ms, so the timing resolution should be about that.

[Flec]

Originally Posted by EQAditu

PS. A period is a reserved regex character, so you should be using "\." in your examples.

A period in RegEx means 'match any one single character', and the + means 'match one or more of the previous pattern'.

So the two together work like * does in Windows, and matches one or more anythings which, because of the parenthesis, get saved and returned at completion.

The second (.+) could have been (/d+) for digits since I'm only matching a number, but they will both match properly.

EDIT: Anyway, that's just a minor thing. I'm sure your right about combat arts and such, I just wrote that on the fly when I saw the OP.

[Johnathon]

What would be the regex to find out if anyone dispatched?

I know a lot of mages want to know when i dispatched and it would make my life easier if they did it by themselves.

[EQAditu]

Originally Posted by Flec

A period in RegEx means 'match any one single character', and the + means 'match one or more of the previous pattern'.

So the two together work like * does in Windows, and matches one or more anythings which, because of the parenthesis, get saved and returned at completion.

The second (.+) could have been (/d+) for digits since I'm only matching a number, but they will both match properly.

EDIT: Anyway, that's just a minor thing. I'm sure your right about combat arts and such, I just wrote that on the fly when I saw the OP.

Yes, yes... I did not mean those. I meant at the end of your examples you used a period before the end-of-line character, $. You meant to match a period, but you told it to match any character instead.

Originally Posted by Johnathon

What would be the regex to find out if anyone dispatched?

I know a lot of mages want to know when i dispatched and it would make my life easier if they did it by themselves.

.+? (?:Debilitate|Debilitating Blow|Dispatch)(?: critically)? hits.+

I half stole this from a Regex I used to warn when mobs used skills on players. Should work otherwise.

[Flec]

Originally Posted by EQAditu

Yes, yes... I did not mean those. I meant at the end of your examples you used a period before the end-of-line character, $. You meant to match a period, but you told it to match any character instead.

You're right, forgive my smartass tone. I completely missed that.

I toyed around with making my autoattacks beep after reading this, and it seemed to be on time with the display in the game window. But this is a t5 character doing 1 group heroics, so my computer wasn't exactly bogged down with processing.

[EQAditu]

The easiest way to find out if ACT is keeping up is to actually look at the log file position in the About tab. It will tell you how many bytes the parsing engine is behind the end of the file.