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
And how about the castbar background, even when it's set to Idle Background it still fades momentarily after every cast.
As for the Christmas lights... I don't have an answer for you on that one. There's probably a logical explanation for it, but personally I just think they make them that way to get you to buy more!
Anyway... what is your "Empty Opacity" set to on your cast bar?
Empty Opacity is at 100%. Looks just the way I want it while idle and while casting; but after a cast is finished/interrupted both Full and Empty opacities fade to 0. After it reaches 0 Idle background kicks back in and Empty Opacity returns to 100. What I was trying to find out is, is there a way to prevent Empty Opacity from dropping 0 along with the Full.
Did you disable health text on your player frame layout?
Did you set your health text to something like "smart" and are at full HP? (in which case it only shows numbers if you take dmg.
You should still see live groups.
Are you in a party or a raid (raids include arena groups)?
If you are in a raid group... did you make a raid group? (PB4 comes built with party frames but not raid frames groups)
Check that you have the "enable" check box for your group types on the Groups menus.
http://img151.imageshack.us/f/wowscrnshot113010003617.jpg/
Note that wierd aura thingys lying around that dissapear when party frames are disabled.
http://img7.imageshack.us/img7/1655/wowscrnshot113010003619.jpg (disabled)
http://img217.imageshack.us/img217/9904/wowscrnshot113010003010.jpg (group settings)
Thanks in advance for any help.
Meanwhile, you can configure them on a singleton frame config and apply to your party, or configure them live in a group. (Config mode just makes sample frames, you can actually configure your frames without it)
@angrysteel, You don't need to modify the softMin and softMax to exceed those values. Just type whatever you want in the box. softMin and softMax only limit the range the slider works with. I figure the +/-200 is a reasonable value. People that want more than that are probably doing something out of the ordinary and can just type in the box.
With Pitbull 3, it was possible to offset buffs / debuffs by a very large amount. With PB4 you are restricted to an offset of 200 in any direction.
The fix is quite simple, just open Interface > Addons > Pitbull4_Aura > Options and change:
softMin = -200, softMax = 200,
to
softMin = -1200, softMax = 1200,
These items are around line 1750ish.
Is there any chance to get these lines updated / changed to default to 1200 instead of 200, or is there a reason offsetting buffs and debuffs were limited so much in PB4?
Thanks either way! Keep up the good work, <3 the addon.
Thanks
first of all awesome work you're doing. I'm loving PitBull.
My problem are the unit frames playing up as soon as I enter a raid with names being being displayed multiple times and buggrabber going ballistic.
Hope you can help me
2- If you are using Beta19, please attach your buggrabber errors (just c/p to a text document) to the existing ticket (wowace login/pw is same as here) about names sometimes duplicating. -- We are aware of a few reports of the issue, but no one has reported actually getting an error when it happens... just that it happens. And we haven't been 100% able to reliably replicate.
2a - If you aren't using Beta19 please update and see if that fixes the issue for you.