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 reply to Icytroll:
Having the exact same issues. Auras gone on all frames... Works fine on PTR with same build for some reason.
One of the many Lua Errors i get. (the only one that spams)
-----------------------------------------------------------------------------------------
Message: Interface\AddOns\PitBull4\ModuleHandling\Module.lua:292: attempt to index field 'db' (a nil value)
Time: Thu May 20 18:44:17 2021
Count: 1003
Stack: Interface\AddOns\PitBull4\ModuleHandling\Module.lua:292: attempt to index field 'db' (a nil value)
[string "=[C]"]: ?
[string "@Interface\AddOns\PitBull4\ModuleHandling\Module.lua"]:292: in function `GetLayoutDB'
[string "@Interface\AddOns\PitBull4\Modules\Aura\Update.lua"]:951: in function `OnUpdate'
[string "@Interface\AddOns\PitBull4\Modules\Aura\Aura.lua"]:21: in function <Interface\AddOns\PitBull4\Modules\Aura\Aura.lua:18>
Locals:
_---------------------------------------------------------------------------------------------------------------
Message: Interface\AddOns\PitBull4\Modules\Aura\Filter.lua:15: attempt to index field 'db' (a nil value)
Time: Thu May 20 18:44:05 2021
Count: 2
Stack: Interface\AddOns\PitBull4\Modules\Aura\Filter.lua:15: attempt to index field 'db' (a nil value)
[string "=(tail call)"]: ?
[string "@Interface\AddOns\PitBull4\Modules\Aura\Filter.lua"]:15: in function `GetFilterDB'
[string "@Interface\AddOns\PitBull4\Modules\Aura\Filter.lua"]:96: in function `?'
[string "@Interface\AddOns\AngryAssignments\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua"]:119: in function <...nts\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:119>
[string "=[C]"]: ?
[string "@Interface\AddOns\AngryAssignments\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua"]:29: in function <...nts\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:25>
[string "@Interface\AddOns\AngryAssignments\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua"]:64: in function `Fire'
[string "@Interface\AddOns\AngryAssignments\libs\AceEvent-3.0\AceEvent-3.0.lua"]:120: in function <...\AngryAssignments\libs\AceEvent-3.0\AceEvent-3.0.lua:119>
Locals: <none>
Message: Interface\AddOns\PitBull4\Main.lua:1579: attempt to index field 'db' (a nil value)
Time: Thu May 20 18:43:57 2021
Count: 1
Stack: Interface\AddOns\PitBull4\Main.lua:1579: attempt to index field 'db' (a nil value)
[string "=(tail call)"]: ?
[string "@Interface\AddOns\PitBull4\Main.lua"]:1579: in function `OnProfileChanged'
[string "@Interface\AddOns\PitBull4\Main.lua"]:1645: in function <Interface\AddOns\PitBull4\Main.lua:1615>
[string "=[C]"]: ?
[string "@Interface\AddOns\AngryAssignments\libs\AceAddon-3.0\AceAddon-3.0.lua"]:70: in function <...\AngryAssignments\libs\AceAddon-3.0\AceAddon-3.0.lua:65>
[string "@Interface\AddOns\AngryAssignments\libs\AceAddon-3.0\AceAddon-3.0.lua"]:527: in function `EnableAddon'
[string "@Interface\AddOns\AngryAssignments\libs\AceAddon-3.0\AceAddon-3.0.lua"]:630: in function <...\AngryAssignments\libs\AceAddon-3.0\AceAddon-3.0.lua:615>
Locals: <none>
In reply to TFKBront:
I had issues today, too. For me it was the addOn "OmniBar" that is causing lua errors for Pitbull Unit Frames. For me, no unitframes was shown until I disabled Omnibar.
If you don't use Omnibar, disable all other addons and check if the error persists.
edit: While testing I also had that slow loading texts, dont know what was causing that...maybe an outdated addon...
In reply to Aur0r491:
Good tip, I disabled Omnibar and got my auras back, seems like the slow loading text was fixed as well, ty!
In reply to Aur0r491:
Yup. Disabling Omnibar did the trick. thanks!
Didn't have that addon on PTR which is why the issue didn't occur there.
Is this an omnibar issue or a pitbull issue tho? i kinda want to use omnibar^^
Probably mine, every now and again some addon comes along and causes PB module loading to break for whatever reason
Feature Request:
I would like for shields, rather than being tacked on to the end of my health bar, to occlude the health bar... preferably with a diagonal striped texture or something (though textures are for people to add anyway) and with (possibly optional) bounding by the health bar. So that if you have 100% of your health as shield, or more, you'll have a diagonal overlay over your healthbar (protecting) your health, but can still see your health through it. KUI Nameplates has an effect like this, and it's extremely tidy and makes it very quick to see health and shields on those... and I'd love to have an option for this in Pitbull.
Anyway to filter auras by the tooltip text? And anyway to use keywords to filter, for example, I don't want any aura with the name champion, so something like blacklist *champion*?
Love the addon.
I have issues since the stagger bar plug in no longer works and i can't find the stagger bar in the options.
I am having an issue with the way shields display on unit frames.
In normal blizz frames, when a unit has a shield, it displays the amount of the shield as a special overlay on the health bar. The really important part is that when the shield absorb + current HP > than the max size of the unit frame, blizz frame collapses the shield overlay inside the health bar, making sure not to bleed outside the unitframe.
In pitbull, when a unit has a shield that adds up to more than the max hp of the healthbar, it bleeds outside the unitframe making a very ugly UI.
Is there any way to fix this...?
EDIT: think i found it. was a little tricky to find. Layout Editor > Other > Visual Heal > Disable 'Show Overabsorb'
Hey! Love the addon, and love how configurable it is. My only question is, do I have to manually add all raid / dungeon debuffs & buffs to the aura lists for friend buffs & friend debuffs to be able to see them? Not being able to see a bunch of debuffs in raids is a struggle.
I am trying to get this old addon working again for Classic, I know its not your project but its an additional module for Pitbull that has been abandoned. I have messed with the code and cannot figure out fixing it, I am assuming that function "UnitBuff" does not exist in Classic or is named something else.
https://www.wowace.com/projects/pitbull4_aurabar
The Power type "ANIMA" is missing from the Power Color options. Can this be added?
Power colors come from the game (PowerBarColor), so not even Blizzard handles it? When is ANIMA used?
In reply to nebula169:
Interesting, I wasn't aware of that. There are some mobs in Bastion (Mnemonic Locus iirc) that use Anima as their power. Their power bar just shows a light gray color but I'd like to change that. I ran a script on what power type they were using and the API returned "ANIMA". I definitely think there are more power types than what can be found in the PowerBarColor constant.
Is there a way to make the tank group filter to refresh aside from reloading the UI? Sometimes when we swap out a tank to DPS, they stay in the tank frame.
I m having some trouble positionning texts. For exemple after placing the name of my target i d like to have its level and type (elite, rare, etc) placed on the same line but just a couple pixels above the line for the target name. And i haven't found how to do so using PitBull.
Been getting this error for awhile. Anybody know a fix?
32x PitBull4\UnitFrameLayout.lua:1498: PitBull4_Frame_8:SetScale(): Scale must be > 0
[string "=[C]"]: in function `SetScale'
[string "@PitBull4\UnitFrameLayout.lua"]:1498: in function <PitBull4\UnitFrameLayout.lua:1443>
[string "@PitBull4\UnitFrameLayout.lua"]:1566: in function `UpdateLayout'
[string "@PitBull4\UnitFrame.lua"]:794: in function `Update'
[string "@PitBull4\UnitFrame.lua"]:815: in function `UpdateGUID'
[string "@PitBull4\UnitFrame.lua"]:349: in function <PitBull4\UnitFrame.lua:345>
[string "=[C]"]: in function `Show'
[string "@FrameXML\UIParent.lua"]:2865: in function `SetUIPanel'
[string "@FrameXML\UIParent.lua"]:2939: in function `HideUIPanel'
[string "@FrameXML\UIParent.lua"]:2627: in function <FrameXML\UIParent.lua:2619>
[string "=[C]"]: in function `SetAttribute'
[string "@FrameXML\UIParent.lua"]:3488: in function `HideUIPanel'
[string "@FrameXML\CinematicFrame.lua"]:59: in function <FrameXML\CinematicFrame.lua:44>
Locals:
(*temporary) = PitBull4_Frame_8 {
1 = PitBull4_SoulShard_1 {
}
2 = PitBull4_SoulShard_2 {
}
3 = PitBull4_SoulShard_3 {
}
4 = PitBull4_SoulShard_4 {
}
5 = PitBull4_SoulShard_5 {
}
0 = <userdata>
Delete = <function> defined @PitBull4\Controls\Controls.lua:126
Shards = <table> {
}
height = 0
kind = "Frame"
bg = PitBull4_Texture_9 {
}
max_shards = 0
}
(*temporary) = Infinite
I added a check to avoid the error