Authors CurseForge

Quote from Mazzlefizz »

• I think the power of the timers really shine when doing things like: tracking DOTS/HOTS across multiple targets, tracking the duration of a CCs like sheeps/saps, tracking immobilization stuff like frost novas. In all those cases, you'll probably switch targets after applying the effect. I'm guessing the dot/buff timer, etc. do not remain after switching a target is also b/c new API just gives information for effect linked to certain unit types. If so, I wanted to suggest the following:
• Perhaps, whenever the user switches targets, you can create replacement candybar timers for the effect on the target you just had. These timers could be shifted up to a list of bars right above the current ones, with the name of the mob it was applied to right next to it (ala DoTimers). The bottom of the block of timers would always be the current target's timers.
• When the user switches to a target, you could also compare the name of the new target and the durations of the new targets buffs/dots with the values of the faux timers you made when the user switched from previous targets. If the name of the unit and one of the timers matches closely enough, you could consolidate the two groups of timers, i.e. delete the faux timers for that unit.
• I wouldn't even worry about doing some of the fancy things that CEnemyCastBars of DoTimers do to monitor effects that randomly break expire early or become subject to diminishing returns. If you ignore that aspect, this solution could be pretty seamless and maintain the simplicity of your current scheme.

Quote from Adelea »

I dont have to do that - do you have delete before updating checked ?

I don't - and the contents of the SkinMe folder are preserved, and checked and commented as appropriate when updated.

Quote from Grayhoof »

I dont understand why you dont like this merge approach, but it's a shame you won't add such a nice feature. It's the only way aoe'ers can see how much damage they do per 'tick'

First off, I don't like stealing things from other mods. MSBT came up with it, and to "steal" it just goes totally against who I am. The fact MSBT doesn't mind stealing from SCT doesn't change my stance on it.

Second, its a not a great way of handling it. From my understanding, MSBT basically delays every event by like .3 seconds to wait and see if another "similar" event comes across. This not only adds additional overheard/delay for every single event, its doesn't work properly for a lot of things. Melee classes are a prime example. It incorrectly merges events that aren't AOE, for example when dual wielding, or getting a extra attack (windfury, etc...).

As I said before I am open to other ideas on how to display AoE better, but I'm not going to use the merged approach for a number of reasons. Feel free to suggest other ideas.