Authors CurseForge

I updated Grid last night, and GridStatusLifebloom seems to not work any more. It doesn't appear in the Debugging list or anything.

This makes me sad, because it was the best option for tracking lifeblooms. GridStatusHots works, but it doesn't change colour as you add more stacks, or offer a decimal countdown.

Is any fix expected?

fixed in GridStatusLifebloom-r61910

Hi I am currently trying to move from SRaidframes to Grid. First I missed a counter how may stacks of my lifebloom a chars has. Than I found this addon for Grid, but when I tested it yesterday in a raid I noticed, that even if I only had one lifebloom up on a tank, if another druid also has lifebloom stacks up on the same tank, then GridStatusLifebloom was not showing the correct stack number of my lifeblooms.

Is this a known issue?

I could not find a better thread to post this in.
Anyways a change in 3.0 broke this addon I changed one of its functions to keep mine working:

function GridStatusLifebloom:CountHOTs(unitid)
    local maxbuffs = 40
    local currentTime = GetTime()
    if unitid then
        for i = 1, maxbuffs do
            local buffName, rank, texture, applications, debuffType, duration, expiryTime, isMine = UnitBuff(unitid,i)
            if buffName and expiryTime then            
                local timeLeft = expiryTime-currentTime
                if self:isLifebloom(buffName) then
                    return applications, timeLeft
                end
            end
        end
    end
    return 0,0
end

the patch broke this i think.... my counter just stays at max now =(

hi calico0, would your code fix this addon for 3.0.2? where would i copy/paste it?

I made a backup of the file, tried it out, and that worked for me! Starting on line number 310 of GridStatusLifebloom r63661 replace the entire function with the one supplied by calico0. Now I just need LibHealComm-3.0 fixed to catch interrupts.

Thanks calico0 and nurdc0re! The code worked but was a little bit buggy. I was in BT with another resto druid and it would sometimes pick up his lifebloom. I noticed this because the other druid had Natures Splendor so his LBs were counting down from 9 seconds.

Quote from wanny

Thanks calico0 and nurdc0re! The code worked but was a little bit buggy. I was in BT with another resto druid and it would sometimes pick up his lifebloom. I noticed this because the other druid had Natures Splendor so his LBs were counting down from 9 seconds.

Replace:
if buffName and expiryTime then
With:
if buffName and expiryTime and isMine then

can someone just post the a link with the new lua needed. thank you

Am I the only one who made these changes and still see no signs of GridStatusLifebloom in the Grid options?

not showing up for me either now. was showing up on the PTR, non-functional as described above. grid doesnt seem to recognize the module at all.

EDIT: fixed. be aware of double-byte chars in that file. something wierd around line 280 for some reason...

Mind hosting your .lua somewhere? I can't see anything out of place. :\

http://www.lukerobi.com/GridStatusLifebloom.zip

there you go.

Quote from luke2kz71

http://www.lukerobi.com/GridStatusLifebloom.zip

there you go.

Thanks a ton :D

Quote from OrionShock

looks like Azethoth fixed this, maybe..

r33:
Doh, I should have looked here b4 fixing it from scratch. Anyway, the currently checked in version R33 fixes everything reported below. Also it removes a bogus dependency on BabbleSpell and makes the buff check inline instead of a function.

EDIT: Doh. Wrong thread.

Anyone else getting a somewhat inaccurate timer using both Azethoth and Luke's .lua?

My timer will start at 4.3 and count down slowly to 0, instead of beginning at 7. While the timer expires the same time lifebloom does, it's just kind of odd watching it count down from 4.3 instead of the appropriate time. '-'

Quote from Reiginsei

Anyone else getting a somewhat inaccurate timer using both Azethoth and Luke's .lua?

My timer will start at 4.3 and count down slowly to 0, instead of beginning at 7. While the timer expires the same time lifebloom does, it's just kind of odd watching it count down from 4.3 instead of the appropriate time. '-'

You may have it in GCD mode, and it's counting down how many are left?