PitBull Unit Frames 4.0
PitBull Unit Frames 4.0
Woof. Arf. Yip.
Getting Started:
You can help translate PitBull for your language with the localization tool.
Classic
PitBull works with WoW Classic! Classic Era/Vanilla is supported in
v4.3.x-vanilla
releases. Cataclysm Classic is supported in v4.2.x
releases
(the same releases retail use).
Classic Era caveats:
- Aura duration is not available from the API, so PitBull uses LibClassicDurations to show them. The duration can be inaccurate if it's affected by rank or talents.
- Cast info is only available for your spells from the API. PitBull uses LibClassicCasterino to show cast bars for other units, but this can be inaccurate since there is a lot of guess-work involved.
Download
CurseForge: https://www.curseforge.com/wow/addons/pitbull-unit-frames-4-0
Wago: https://addons.wago.io/addons/pitbull4
WoWInterface: https://www.wowinterface.com/downloads/info20021
In the options menu, choose Layout Editor on the left. Choose your current layout you are working with. Choose the Texts tab below that. On the drop down menu for Current Text choose Lua: Health. Make sure it's enabled (it should be). On the Attach To drop down make sure it's attached to the Health Bar (default). Next to it you can choose the it's location on the bar. Two lines down, there is a drop down labeled Code. You'll want to choose Health: Absolute and ... That ... is supposed to be %. You'll get the result you're looking for.
It's entirely possible I've missed something, but after downloading, I've noticed that dogtags are not supported initially. I'm wondering what I would need to do to be able to use dogtags for my text customization again?
tahum, choose something other than Smart for the health text under the Texts tab of your layout(s).
I dont know if this has been asked earlier, but i couldnt seem to find it. I want to see the max health of friendly targets as well as enemies, how can i do that? Thanks.
But this removes the target indicator.
local cast_data = CastData(unit)
if cast_data then
local spell,stop_message = cast_data.spell,cast_data.stop_message
local stop_time,stop_duration = cast_data.stop_time
if stop_time then
stop_duration = GetTime() - stop_time
end
Alpha(-(stop_duration or 0) + 1)
if stop_message then
return stop_message
else
return spell
end
end
return ConfigMode()
P.S. You should add this code Shefki.
chocozurean, CastBar tracks the casting info for all valid units that we receive events for. It then updates the actual bars on a timer. The timer is necessary for smooth updates of the cast bar itself. Health and Power bars are updated based on events only there's no smooth movement of them so no need for a timer. Blizzard code actually handles the spinners for aura durations, the text we use timers for. The big difference here is that the CastBar isn't doing several things it should: a) The casting events should only register when a frame is shown that has a CastBar enabled on it. b) The casting data tracker should ignore events for units whose frame does not have a CastBar enabled on it. c) The timer should turn off if there is no casting data.
I sorta have changes in progress to resolve these things but it's complicated by the design of the CastBar module as a bar module. This abstracts some things out that would make it easier to do if I had them. But I'll get it done anyway. It's just gonna take some time.
One option I'm missing though is the option to color the health bar (for pets) by happiness. Or maybe I'm blind and just can't find out which option can enable it? :X
Also is there any way to disable the frames from snapping onto each other?
You can hold down shift while moving to stop frames from snapping.
Hmm ok, so I take it that CastBar updates on a very frequent timer? Are other status bars (health, power, aura durations...) not as frequent? You mentioned that CastBar might be updating for all units, even those that don't have frames. Would having it be used only for frames that exist help any?
I don't use TinyTip btw, but if interaction with other addons is a possible reason, I do run plenty of other stuff. I'll do some more testing tomorrow with only Pitbull enabled and try out modules in isolation.
Ah, ok, thanks for the tip. That means it may have nothing to do with Pitbull at all; most of my addons are Ace3 based so Pitbull is possibly getting tagged for all their usages. I can even test that out by trying to force the libraries load separately.
Guess I'll have to find a new explanation for my my frame rate goes to crap while raiding :/