some nights/fights it works just fine, but sometimes it keeps removing the bars representing my dots for no reason.
i see bars of a just casted corruption disappear (fade, go into ghost mode, anyway you get what i mean) right after 1 second, or maybe 4 seconds before their expected end
i thought that this could be correct in two circumstances: the raid boss dispells, which wasnt, or 40 debuff slot limit was reached, which wasnt too.
It's been mentioned a couple times in this thread previously, actually. Chronometer only parses your combat log and displays information that the combat log gives. It doesn't track per your target or focus (that was just added in 2.1 and other mods do do that). If a mob with the same name as the mob you have a dot on or have poly'ed DIES, then the bar for that DoT or debuff will disappear. It's either be inaccurate one way (bar disappears too soon) or the other (bar stays up for full duration even if mob dies or poly broken, etc).
It's been mentioned a couple times in this thread previously, actually. Chronometer only parses your combat log and displays information that the combat log gives. It doesn't track per your target or focus (that was just added in 2.1 and other mods do do that). If a mob with the same name as the mob you have a dot on or have poly'ed DIES, then the bar for that DoT or debuff will disappear. It's either be inaccurate one way (bar disappears too soon) or the other (bar stays up for full duration even if mob dies or poly broken, etc).
that is not the case tho, since it happens on raid bosses with 90% hp left
That happens because someone else's Corruption fades, for example.
Could be fixable though, just when there's a "Corruption ends" in the log, check the Blizzard info on how long your DoTs on your current target still have to go.
That happens because someone else's Corruption fades, for example.
Could be fixable though, just when there's a "Corruption ends" in the log, check the Blizzard info on how long your DoTs on your current target still have to go.
At least for Bossfights, it'd be accurate then.
i thought about it, what i dont get is that sometimes a whole night seems to go perfect, and some other nights/bosses it happens every second.
so i can expect this to be fixed with next version hopefully?
I've noticed that Chronometer is showing triggered hunter traps again(yay!). However, it doesn't seem to account for the Clever Traps talent as my Freezing Trap bar lasts only 20 seconds instead of 26. I've checked the Hunter.lua file in the Data folder, and I would assume that it would be handled in this line:
I have also noticed when i use Swiftmend ... the Rejuvenation bar doesn't disappear.
Swiftmend consumes a Rejuvenation when it is on the target, so it should be removed.
If you need any input regarding this ... or my post above due too Lifebloom stacking, pls say so or send me a PM :)
Other then this ... great addon, and works perfectly :D
I like Chronometer though. This new Blizzard-supported way just doesn't work for me, I need an overview of how long my DoTs last on what, not only on my current target.
There are not many AddOns to choose from. Chronometer or NECB, those two I know. And NECB is fugly and big. :) Does anyone know if Antagonist and / or DoTimer can track DoTs and HoTs on multiple targets?
Antagonist shows enemy casts, buffs, and cooldowns. It's what you combine with Chronometer (or at least used to) to get close to the functionality of necb.
There are not many AddOns to choose from. Chronometer or NECB, those two I know. And NECB is fugly and big. :) Does anyone know if Antagonist and / or DoTimer can track DoTs and HoTs on multiple targets?
DoTimer (still) has some of the best multi-target tracking out there. Unfortunately it's not the most efficiently coded addon, but hey, not everything can have Ace-quality performance. :P
At times, Chronometer is driving me nuts. When I am healing on my Druid, It is absolutely great to track HoTs. But when I am soloing, it is a very rare event that the bleed, mangle and fairy fire bars actually disappear when a mob dies. Classtimer for example does that job much better. So far I have been too lazy to use two addons for this, or to use some addon manager, but I may look into that in the future...
Actually... back to chronometer... is there a way to make it only show HoTs?
If you want something to *only* show HoTs, you may as well get something like HoTCandy.
Tried it just now ... but the same issue as with Chronometer :(
1) Rejuvenation doesn't disappear when i use Swiftmend on that person.
2) No number how many times Lifebloom has been stacked.
This prolly doesn't belong into the Chronometer-thread, but: I tried Classtimers + HoTCandy now, and that definately works better for me. I do not need to track stuff on multiple targets except for HoTs, so I'll stick to this combination. Except for the points that Brigid mentioned. I saw a HoT and DoT timer for druids in WAU, tho. Tried that yet? Name is Hotman or so. Stackable HoTs and using up running HoTs is mostly a druid problem, I think.
Well, depends. If you do use embedded libraries, you will get an update each time one of the libraries that chronometer depends on is updated. Check the changelog if you update with WAU to see what was changed, and who did it. I see 5 changes in the last 5 days... looks like people are working on this, still. :) Mebbe it is just bugfixes and localizations. And mebbe the people updating just ain't posting much on forum. *shrug* Sometimes people go crazy and scream ABANDONED! as soon as the OP of a thread takes a 2-day break. ;)
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Yeah just replaced NECB for Antagonist and Chronometer, but realy miss the amounts of times it has been applied :(
Could you add this pls ?
some nights/fights it works just fine, but sometimes it keeps removing the bars representing my dots for no reason.
i see bars of a just casted corruption disappear (fade, go into ghost mode, anyway you get what i mean) right after 1 second, or maybe 4 seconds before their expected end
i thought that this could be correct in two circumstances: the raid boss dispells, which wasnt, or 40 debuff slot limit was reached, which wasnt too.
anyone can help me figure this out?
thanks,
tyler
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumthat is not the case tho, since it happens on raid bosses with 90% hp left
Could be fixable though, just when there's a "Corruption ends" in the log, check the Blizzard info on how long your DoTs on your current target still have to go.
At least for Bossfights, it'd be accurate then.
i thought about it, what i dont get is that sometimes a whole night seems to go perfect, and some other nights/bosses it happens every second.
so i can expect this to be fixed with next version hopefully?
self:AddTimer(self.EVENT, BS["Freezing Trap Effect"], 10, 1,0,1, { gr=1, d={rs=5, tn=BS["Clever Traps"], tb=0.15, tp=1}, xn=BS["Freezing Trap"] })However, I'm not familiar with LUA at all and haven't the foggiest idea how to fix it.
Swiftmend consumes a Rejuvenation when it is on the target, so it should be removed.
If you need any input regarding this ... or my post above due too Lifebloom stacking, pls say so or send me a PM :)
Other then this ... great addon, and works perfectly :D
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumDoTimer (still) has some of the best multi-target tracking out there. Unfortunately it's not the most efficiently coded addon, but hey, not everything can have Ace-quality performance. :P
Actually... back to chronometer... is there a way to make it only show HoTs?
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumTried it just now ... but the same issue as with Chronometer :(
1) Rejuvenation doesn't disappear when i use Swiftmend on that person.
2) No number how many times Lifebloom has been stacked.