Authors CurseForge

Yeah I've been having this problem for a few days too.

 

PaladinPowerBar has a similar problem to the priest bar, and should only be hidden and not reparented. Blizzard_CombatText uses PaladinPowerBar:GetParent().unit for its holy power display (see Blizzard_CombatText.lua:266).

The reason why the bars are sticking is that sometimes (mostly with death runes I believe) NewTimerBar is getting called with a 0 remaining time, which LibBars-1.0 seems not to cope with.

I've fixed it by changing Heatsink:StartBar() inside Heatsink.lua around line 773:

function Heatsink:StartBar(name, start, duration, icon, track)
  for k,v in pairs(self.active) do
    if v == name then
      return
    end
  end

  local remaining = duration - (GetTime() - (start or 0))

  if remaining <= 0 then return end

  if track then table.insert(self.active, name) end

  self.cooldown:NewTimerBar(name, name, remaining, duration, icon)
  local bar = self.cooldown:GetBar(name)

  if self.db.profile.emphasize then
    if bar then
      bar:RegisterTimeLeftTrigger((self.db.profile.emphasizeTime or 5), Heatsink.Emphasize)
    end
  end
end

This doesn't help with all the DK abilities appearing (that need some magic in ScanSpells) but at least it stops them bugging out.

Fix two pet spell bugs.

Heatsink.lua:1083 in function Heatsink:ScanPetSpells()
BOOKTYPE_SPELL -> BOOKTYPE_PET

Heatsink.lua:933 in function Heatsink:PET_BAR_UPDATE_COOLDOWN()
startTime -> start

Yeah whoever has been doing the LibBabble-3.0 changes botched it here.

The line should be

<Include file="Libs\LibBabble-Spell-3.0\lib.xml"/>

and directly after that it should have

<Include file="Libs\LibBabble-Boss-3.0\lib.xml"/>

And needs a copy of LibBabble-Boss-3.0 unpacked in the Libs dir (it's a dependency of Threat-1.0 now).