RotLatency
RotLatency tracks the delay between action cooldown and the next activation. In other words, it tracks how fast you respond to cooldown expiration.
You can display your averages either from the command line (/rotlatency stats) or via tooltip on a LibDatabroker display, such as Chocolate Bars.
Each ability/action is tracked separately and an overall average is displayed.
Configuration is done through Options->Interface->Addons or just click RotCooldown on your LDB display.
Configuration Help
"GCD Spell" is an ability that only uses the GCD -- i.e. it doesn't have its own cooldown. Find Herbs is an example.
"Time Gap" is the gap in time you want RotLatency to stop tracking cooldowns after you've finished casting your abilities. This is useful when there's down time in your rotation, or between pulls, so that this gap in time doesn't taint the latency data.
Add a spell under "Spells To Track."
Check "Track GCD" if the ability only uses the GCD. In other words, the ability has no cooldown of its own.
You can display your averages either from the command line (/rotlatency stats) or via tooltip on a LibDatabroker display, such as Chocolate Bars.
Each ability/action is tracked separately and an overall average is displayed.
Configuration is done through Options->Interface->Addons or just click RotCooldown on your LDB display.
Configuration Help
"GCD Spell" is an ability that only uses the GCD -- i.e. it doesn't have its own cooldown. Find Herbs is an example.
"Time Gap" is the gap in time you want RotLatency to stop tracking cooldowns after you've finished casting your abilities. This is useful when there's down time in your rotation, or between pulls, so that this gap in time doesn't taint the latency data.
Add a spell under "Spells To Track."
Check "Track GCD" if the ability only uses the GCD. In other words, the ability has no cooldown of its own.
Comments
-
_ForgeUser189254 Owner
-
View User Profile
-
Send Message
Posted Jul 18, 2011Note that this is broken. My approach doesn't consider that global cooldown will activate each current "timer," meaning it updates the next "latency" erroneously for every spell you're tracking. So we only hesitantly reassign every "latency" as an "average latency across global cooldown." Will see about fixing this somehow. There may still be a race condition or two from the looks of it, but hopefully rotations don't tread there.