Choadley

It makes it a shitload faster for figuring out the min/max and total damage numbers. I would never bother going through a log file adding the numbers myself. Great tool...period.

__________________
T7M is recruiting: Dirge, Wizard

"I am a COWBOY!!!"

Ishbu

I never personally have used ACT for timers at all and all I have ever used it for was parsing fights, speaking for myself and myself only.

All through multiple tiers I simply relyed on instincts and my amazing ability to count by 1's to tell when an AE would hit, its really not that hard. It wasnt even hard to figure out in my head when the AE would land when a rogue said they had traumatic swiped a mob. If you cant do these basic functions, go back to 1st grade.

So in short, ACT simplifies and already simply process. Its like making a macro button in game. You can do just fine without it, but many people use them just for that extra tiny ass convenience.

__________________
"We are looking into ways to reduce the feeling that you must always be pressing a button to contribute to the group or raid" - Aeralik, aka Chris Kozak.

"So standing around doing nothing makes you a better player and for a more satisfying game experience you dumb fucking idiot?" - Me

Manyak

ACT actually almost screwed us a few times with swipes.

If the rogue that swiped the mob dies to an AE, ACT assumes that swipe is still up when that AE hits, and for any ability for the next few seconds until when swipe SHOULD have droppped. So the AE ends up hitting way earlier than when ACT says it should.

Also, with the brigand's Tenure AA making swipe last 34 seconds, if an AE hits within those last 4 seconds, ACT will time it as if swipe was NOT up. So the AE ends up hitting way later than when ACT says it should.

Im necroing i know, but just figured id point this out.

__________________

killua_ncream

grep...Pinski, you're a man after my own heart aren't you?

__________________

Cupcake

Add me to the classic stopwatch list! Good times!

__________________