Hey there. I'm wondering if there's plans to update Auras to include the new time left information?
I deleted all my buff-parsing code when I found Auras, and I'm not liking the prospect of re-writing it all, and since I use Grid and some other mods that use Auras, it'd be a waste of CPU/memory for me to loop through all the buffs again and store them all just for timing information.
Right now I'm just going to do the following, but having Auras updated would be nice and cleaner/etc., so I figured I'd check if there's plans for it.
I just started poking at it, and it occurred to me that we could give duration, expires instead of duration, timeLeft. Thoughts?
I suppose that would be less overhead -- one calculation when updating instead of a calculation at every request for the information.
Don't you need "start time" and "duration" to set a cooldown timer, though? Or is there some new cooldown stuff that I'm unaware of? 'cause quite frankly, knowing duration and time left means I have to do a lot of extra steps to set a cooldown timer, and BLizz usually doesn't do that. They usually give you exactly what they needed to make their UI. :)
duration, expires makes more sense than duration, timeleft, for a local storage system, though. definitely.
-- Handle cooldowns
cooldown = getglobal("TargetFrameBuff"..i.."Cooldown");
if ( duration ) then
if ( duration > 0 ) then
startCooldownTime = GetTime()-(duration-timeLeft);
CooldownFrame_SetTimer(cooldown, startCooldownTime, duration, 1);
-- Set the buff to be big if the buff is cast by the player and the target is not the player
if ( not playerIsTarget ) then
largeBuffList[i] = 1;
Edit: drycoded the duration, expires changes. Attached.