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.
rev. 64007 update:
Number of LB stacks should now be counted in Total Hots, however I'm not able to test this.
Not sure what is preferred for hot timers when it comes to LB, the countdown or your stack number (text are limited to the square) and I don't play druid. (not counting my lvl 4 druid).
name, rank, iconTexture, count, duration, timeLeft = UnitBuff(unit, buffIndex[, castable])
...
duration
Number - Full duration of a buff you cast, in seconds; nil if you did not cast this buff.
timeLeft
Number - Time left before a buff expires, in seconds; nil if you did not cast this buff.
Hello...since patch the time remaining on my renews on other players doesn't show anymore...i still get how many are on each character, but no time remaining. Strangely enough though...i still get the countdown on my character's grid box just not everyone elses. I hope this makes sense. Please help.
It might have to do with this, "As of 2.2, UnitName is confirmed to be bugged. UnitName is returning "Unknown" if not applicable, or nil if the unit code itself is invalid (such as "xyz"). This will be fixed in 2.3."
"Since the 2.2 patch, I've been having problems with the addon, GridStatusHots. It doesn't show hots on people from other servers in BGs. If the person is from my server it works great, otherwise it won't show a hot on them at all. I looked through the code, and added some debug statements, and it appears GridStatusHots is getting the right hot count, but somehow it gets lost before it triggers a status change in Grid. Any ideas?"
I hardly play any BG's so I dont know where to debug this.
If you find any soloutions, let me know and I'll update GridStatusHots.
I did an instance run of blood furnace last night with my warlock and it was working perfectly. Smooth frame rates and I was even playing mp3 at the same time. Thank you for your help.
Hi
I've optmized the code, updating status on schedulerepeatingevent every second instead of on UNIT_MANA and UNIT_HEALTH events (i know it was stupid, but im no expert :) ) which would be very often and could casue these lockups.
I did a 4 hour run in Shadow Labyrinth and started out with 30Mb at the end I was at 31,5mb (no lockups for me)
I hope it works out better now, grab it from the SVN and let me know.
[2007/03/02 22:54:31-721-x1]: Grid-26909\GridFrame.lua:355: attempt to index local 'text' (a number value)
GridStatusHotStack\GridStatusHotStack.lua:276: in function `UpdateUnit'
GridStatusHotStack\GridStatusHotStack.lua:238: in function <...ace\AddOns\GridStatusHotStack\GridStatusHotStack.lua:235>
<in C code>: ?
AceEvent-2.0-25921 (Ace2):320: in function `TriggerEvent'
SpecialEvents-Aura-2.0-28987:412: in function `AuraScan'
SpecialEvents-Aura-2.0-28987:84: in function `?'
AceEvent-2.0-25921 (Ace2):757: in function <Interface\AddOns\Ace2\AceEvent-2.0\AceEvent-2.0.lua:751>
<in C code>: ?
AceEvent-2.0-25921 (Ace2):427: in function <Interface\AddOns\Ace2\AceEvent-2.0\AceEvent-2.0.lua:403>
0
Number of LB stacks should now be counted in Total Hots, however I'm not able to test this.
Not sure what is preferred for hot timers when it comes to LB, the countdown or your stack number (text are limited to the square) and I don't play druid. (not counting my lvl 4 druid).
0
The new features are 2 ekstra customizable colors for all hots.
Defaults are yellow on 4 sec left and red on 2 sec left.
I've been thinking about adding Earthshield stacks and maybe Lifebloom stacks aswell but there already is a statusmodule for Lifebloom stacks.
EDIT: thx kunda, I slacked on the Druid testing, my usual druid tester quit wow, and I'm to busy to lvl a druid myself. It was copy&paste indeed :)
0
0
0
This is actually great, if it works like this.
This could track dispels of hots and if it were you casting it, and I can now remove the hardcoded countdowns in GridStatushots.
0
- You can change the duration of HoTs (ex Tier 5 priest gear adds 3 sec to renew)
EDIT : Thanks DannyG, your code snip workaround for the BG problems also added...
0
http://forums.worldofwarcraft.com/thread.html?topicId=102909678&sid=1&pageNo=12#221
Will be fixed in 2.3 I guess.
0
/ty
0
I hardly play any BG's so I dont know where to debug this.
If you find any soloutions, let me know and I'll update GridStatusHots.
0
0
I'll have another look at the nil problem. I got it too yesterday.
0
Please test run and give me feedback.
Shad
0
Hi
I've optmized the code, updating status on schedulerepeatingevent every second instead of on UNIT_MANA and UNIT_HEALTH events (i know it was stupid, but im no expert :) ) which would be very often and could casue these lockups.
I did a 4 hour run in Shadow Labyrinth and started out with 30Mb at the end I was at 31,5mb (no lockups for me)
I hope it works out better now, grab it from the SVN and let me know.
0
Yes I know this might happend if someone leaves your party. I will fix it in a new release.
0
Hi
I'm not author of gridstatushotSTACK