Our records show that you have outstanding author rewards points. Please confirm your latest payment information and redeem your points balance via the Author Reward Store.
After the latest update tonight I got the following error.
[2007/04/16 21:31:05-317-x1]: Chronometer-0.10\Core\Chronometer.lua:726: bad argument #1 to 'gmatch' (string expected, got nil)
<in C code>: ?
AceEvent-2.0-32527 (BigWigs):322: in function `TriggerEvent'
AceEvent-2.0-32527 (BigWigs):1009: in function <...ce\AddOns\BigWigs\Libs\AceEvent-2.0\AceEvent-2.0.lua:1002>
Okay, I think I fixed it, but I don't know how to duplicate what you were doing to test it. If it still happens, please let me know what exactly you're doing to cause it (spell you're using, etc.)
Okay, as far as all of the complaints about Fire and Shadow Vulnerability - I know about this, it has been a bug since this was AceTimer, and the fix for it doesn't fit well into the AceTimer architecture that Chronometer still uses (and even if I do implement it, it still wont' be perfect).
Now, about spells not being recognized, especially when cast in quick succession or in macros. This is hopefully fixed, since I have moved to SpellEventsLib for spellcast detection. However, I never really encountered this issue myself so I'll rely on those who have had this problem to verify that this fixes it.
It only displays the bar for the first target the spell is on, and then just displays it for 30s no matter where it jumps
Well unfortunately, as far as I know there's no way for me to keep track of the Prayer of Mending as it jumps around between people. The best I could possibly do would be to display the timer for the person you initially cast it on.
As for the other person mentioning Fire Vulnerability from Scorch... Well, there's a reason no other DoT timers even try to show stuff like Fire/Shadow Vulnerability, Inspiration, Ancestral Fortitude, etc. There is no way to accurately detect when buffs like these have been re-applied. I might just comment out the lines for all of those type of timers and let people comment them back in at their own discretion with the knowledge that they don't work well.
All right, I'm checking in some changes right now.
NONE OF THIS STUFF IS TESTED! I know that it at least loads without errors, but I don't have toons with any of the newly-added abilities, so that's as far as my testing could go.
Ghostly Strike
Prayer of Mending
Devastate (refreshes Sunder Armor)
Wrath of Air Totem
Totemic Call (removes all totem timers)
Once again, none of this has been tested to see if it works, so if y'all could verify it for me that'd be great. :)
Sorry I've been kinda inactive lately. I didn't play much at all until BC came out, and I've just now started back up again. I'll try to get all of the new abilities (Devastate, Totemic Call, etc.) in pretty soon...
I still haven't really decided how to handle event-based bars though, like warlock/priest Shadow Vulnerability, mage Fire Vulnerability and Winter's Chill, Ancestral Fortitude and Healing Way, Inspiration, etc. Most addons don't even bother trying to put up bars for these things because there's no really clean way to do it. I've pondered making an option to turn all of those bars off and making off be the default, so that people who want to turn them on will have to make the conscious decision to do so and will have to acknowledge somewhere in the process that those bars aren't that accurate... But I digress.
Wow, lots of posts since last I was able to access the forums.
For the couple of folks who said that Chrono wasn't working at all, or was crashing their WoW or what have you... Well, I think that enough other people (including myself) have it working that it would seem to be a problem on your end. I would guess a conflict with another addon perhaps. Try deleting your AddOns/Chronometer folder and your Chronometer SavedVariables, then download the latest Chronometer and start WoW with only Chronometer enabled. If you still have problems with it then, my next guess would be demons in your computer.
As far as the other issues (missing timers, incorrect timers, talent changes, etc.), I'll get them over the course of the next week or so as I have time to do so. Just continue to post here with what the missing/incorrect timer is and what it's proper duration should be (and what talents might affect it) and I'll get it in.
Is it possible, with Chronometer, to get vicinity CC spells to show up? For example, if a mage in your party sheeps a mob that you don't happen to have targeted, I'd still find it useful to see a timer for that sheep. Is it possible already or should I call it a feature request? :)
-k
I really don't want to get outside of the realm of monitoring your own spells' durations. I think that third-party CC duration monitoring would best be done as another addon.
Since SpellCacheLib and SpellStatusLib do not work at all with TBC, is there an alternative way to monitor spell times?
Well I got my beta key the other day and started a TBC branch of Chronometer. I don't need to use SpelLCacheLib anymore (and I never used SpellStatusLib) due to having the new UNIT_SPELLCAST_SENT and UNIT_SPELLCAST_SUCCEEDED events.
So yeah... Chronometer basically works in TBC now. There are plenty of timers that are incorrect or missing right now, but that'll get fixed eventually.
Downloaded the newest one, and permafrost doesn't seem to be fixed. I have Frostbolt Rank 4 currently and with 3/3 permafrost it should be a 10 second slow, it's still listed as 7 seconds. And in the mage.lua it still has winter's chill in the Frostbolt spell line.
Think I got it this time... Sorry, I don't have a mage to test this stuff with.
2006/11/13 19:31:13-227-x6]: ZugLoot\ZugLoot.lua:186: attempt to call a number value
<in C code>: ?
ZugLoot\ZugLoot.lua:186: in function `obj_method'
AceEvent\AceEvent-2.0.lua:312: in function `TriggerEvent'
AceEvent\AceEvent-2.0.lua:898: in function <...erface\AddOns\BugSack\Libs\AceEvent\AceEvent-2.0.lua:890>
---
german wow
Hehe... Yeah, I hadn't actually tested it in AQ yet. ;) Think I've fixed that one, but won't know for sure till my guild's next AQ run.
ZugLoot is a small AddOn I developed for my guild (the great ZugScouts of Dethecus!) to speed up our ZG runs.
Basically, you give ML for trash to someone with this addon, and whenever they open a body it will go through and automatically distribute coins, bijous, and BoE greens evenly and randomly throughout the raid.
It also has some minimal AQ20 loot stuff - you can set a person in the raid as the "aqlooter" who will receive all AQ idols and scarabs, and when the master looter with ZugLoot opens a body it will automatically give scarabs and idols to that person. After that, it's up to the guild bank to distribute them. The random distribution of BoE greens will continue to work in AQ20 - actually, it'll work anywhere that you're the master looter for a group.
I've been using this addon for awhile, however it doesn't seem to take mage talents into account for duration (primarily Frostbolt with 3/3 permafrost). Any chance of a fix for that?
0
Okay, I think I fixed it, but I don't know how to duplicate what you were doing to test it. If it still happens, please let me know what exactly you're doing to cause it (spell you're using, etc.)
0
Now, about spells not being recognized, especially when cast in quick succession or in macros. This is hopefully fixed, since I have moved to SpellEventsLib for spellcast detection. However, I never really encountered this issue myself so I'll rely on those who have had this problem to verify that this fixes it.
0
Well unfortunately, as far as I know there's no way for me to keep track of the Prayer of Mending as it jumps around between people. The best I could possibly do would be to display the timer for the person you initially cast it on.
As for the other person mentioning Fire Vulnerability from Scorch... Well, there's a reason no other DoT timers even try to show stuff like Fire/Shadow Vulnerability, Inspiration, Ancestral Fortitude, etc. There is no way to accurately detect when buffs like these have been re-applied. I might just comment out the lines for all of those type of timers and let people comment them back in at their own discretion with the knowledge that they don't work well.
0
NONE OF THIS STUFF IS TESTED! I know that it at least loads without errors, but I don't have toons with any of the newly-added abilities, so that's as far as my testing could go.
Once again, none of this has been tested to see if it works, so if y'all could verify it for me that'd be great. :)
0
I still haven't really decided how to handle event-based bars though, like warlock/priest Shadow Vulnerability, mage Fire Vulnerability and Winter's Chill, Ancestral Fortitude and Healing Way, Inspiration, etc. Most addons don't even bother trying to put up bars for these things because there's no really clean way to do it. I've pondered making an option to turn all of those bars off and making off be the default, so that people who want to turn them on will have to make the conscious decision to do so and will have to acknowledge somewhere in the process that those bars aren't that accurate... But I digress.
0
For the couple of folks who said that Chrono wasn't working at all, or was crashing their WoW or what have you... Well, I think that enough other people (including myself) have it working that it would seem to be a problem on your end. I would guess a conflict with another addon perhaps. Try deleting your AddOns/Chronometer folder and your Chronometer SavedVariables, then download the latest Chronometer and start WoW with only Chronometer enabled. If you still have problems with it then, my next guess would be demons in your computer.
As far as the other issues (missing timers, incorrect timers, talent changes, etc.), I'll get them over the course of the next week or so as I have time to do so. Just continue to post here with what the missing/incorrect timer is and what it's proper duration should be (and what talents might affect it) and I'll get it in.
0
I really don't want to get outside of the realm of monitoring your own spells' durations. I think that third-party CC duration monitoring would best be done as another addon.
0
Well I got my beta key the other day and started a TBC branch of Chronometer. I don't need to use SpelLCacheLib anymore (and I never used SpellStatusLib) due to having the new UNIT_SPELLCAST_SENT and UNIT_SPELLCAST_SUCCEEDED events.
So yeah... Chronometer basically works in TBC now. There are plenty of timers that are incorrect or missing right now, but that'll get fixed eventually.
0
Yeah, doesn't sound familiar. :( My 60s on Dethecus are Elemak, Bhattu, and Tezuman.
0
Think I got it this time... Sorry, I don't have a mage to test this stuff with.
0
There's another faction? ;)
0
Hehe... Yeah, I hadn't actually tested it in AQ yet. ;) Think I've fixed that one, but won't know for sure till my guild's next AQ run.
0
Basically, you give ML for trash to someone with this addon, and whenever they open a body it will go through and automatically distribute coins, bijous, and BoE greens evenly and randomly throughout the raid.
It also has some minimal AQ20 loot stuff - you can set a person in the raid as the "aqlooter" who will receive all AQ idols and scarabs, and when the master looter with ZugLoot opens a body it will automatically give scarabs and idols to that person. After that, it's up to the guild bank to distribute them. The random distribution of BoE greens will continue to work in AQ20 - actually, it'll work anywhere that you're the master looter for a group.
0
Permafrost should be fixed now. Any others?
0
Actually, I fixed that one about a month ago. :)