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
I know there is a plan to make boss frames available in PB4, but it has not yet been implemented. Turning off the bossframe for everyone without a replacement is not ideal for many people either.
Continue to give your feedback on the tickets. We appreciate constructive critique!
@Rommino, Curse should have the correct version. The version you downloaded had a small change that has no impact on the issue you're reporting. Sounds to me like you didn't fully upgrade somehow.
Checked it out and it showed v4.0.0-beta12. I grabbed v4.0.0-beta12-1-gef7174e from this site and manually copied over the contents of the zip. That totally fixed the problem. I got the original file from Curse, so possible that Curse isn't up to date? Either way, everything is working brilliantly now! Thanks much!
@Rommino, Sounds like you didn't actually get the upgrade completely properly. Check that you have beta12 by doing /pb and looking at the version number in the top right.
This may have already been addressed, if so, I didn't see the thread. I just upgraded to Pitbull 4.0 following the release of the 4.01 patch. Everything set-up pretty easily, however, I am noticing that the health isn't tracking at all (instantly or otherwise). So, for example, as I take damage the bar will go down but the actual number/percentage will still show 100% as I am taking damage. Likewise for my party and targets. Not sure if this is a setting that I have managed to select/deselect but I am wondering if there is something that I can do to fix this.
@Cayle, I can't reproduce that problem, When I turn the module off or disable the text it stops. Are you sure you aren't confusing floating combat text or some other addon with this?
@H0PE, sounds like the same issue Tinolyn is complaining about, you'll need to turn off the animation and the smooth opacity change features. Both use the animation system. Incidentally, to both of you are you on Windows. Because I can't reproduce the issue, it's possible they broke the Animation system only on WIndows.
@nscxaoc, You sure you have SharedMedia loading for that character.
@Liantha, First off that feature is protected, so you can't do that anymore from PitBull4. Eventually we'll come up with a way to deal with it. Secondly, if you're getting that error, then you haven't updated your PitBull4.
* make the eclipse bar able to be placed horizontal or vertical like runes,shards, etc.
To make a new group, review the guide section on partys and groups. (Guide is linked above)
tec
To get your name to just show name and not afk or DND:
Select Lua:Health and Choose "Custom" from the cod drop down. Put this into the box:
return Name(unit)
Press the Accept Button.
Dead is a reaction in the Lua:Health portion.
If you use "Health: Smart" as the code it will only show how much someone is low on health and DEAD. Full health will not show any numbers.
However! This won't fix right clicking off the auras with PB4. Blizzard decided with 4.0 to make that a protected function. You CAN use the default Blizzard icons (upper right) to click them off... just not the ones on your frames. :(
There is a plan to write an aura module that will restore some of that functionality but I can't give you an ETA on when it will be done. Sorry :|
The latest and greatest version from 10/12 corrected it from throwing that error.