What version of Ovale are you using?
What class and specialization were you playing when the problem occurred?
Which script were you using when the problem occurred? If possible, please provide the smallest script that demonstrates the problem.
Modified Leafkiller's script
What steps will reproduce the problem?
Refreshing a dot towards the end of a buff has a chance of not counting that buff's stats
Please provide any additional information below.
I'm not sure I like how the addon currently updates the stats for debuffs. Currently the way I have my ovale script setup it prevents me from trying to do a bleed for 300ms before any trinket/self buff is about to expire. Sometimes even that far out, I'll put up a rake at like 300 ms remaining on Rune and then ovale will "update" the stats to say that the bleed doesn't have the rune buff but when i check the damage it very clearly does. This is far more devastating than the problem of not catching it at the start of the buff (or the very rare occasion that it will not catch a buff falling off) because now it will suggest that I overwrite a superior bleed with a weaker one where as at least the other way I was putting up an equivalent bleed or better 95%+ of the time (and it occurs far less frequently on buff gain vs buff fade with the exception of Tiger's Fury because it gives energy and is off the gcd).
A couple ways you might tackle this:
An option as to whether or not to use the snapshot updating code. Some classes might get better use out of one method over the other (I've found it to be far worse than just using whatever the character sheet says at the moment since that was at least consistent).
Only try to pick up updated stats on aura gain and not aura fade.
Some combination of those two.
Something else I haven't thought of.
Given the limits of what we're given, I don't think we will ever have perfect stat snapshots. We just need to figure out what works best.
- 7 comments