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 have a problem, I can't see the raid leader icon on my Target.
Please help-me
I made some screenshots
http://img385.imageshack.us/img385/8262/wowscrnshot090209203129.jpg
http://img524.imageshack.us/img524/9066/wowscrnshot090209203137.jpg
I'm getting a massive number of:
Error: Usage: UnitPower("unit"[, type]) AddOn: PitBull4 File: PowerBar.lua Line: 88 Count: 1
with v4.0.0-beta3-32-g872bdd0
Can anyone tell me why there isn't a fool-proof option (if there is slap me) to disable showing party frames while in raid? I am using Grid for raiding and I won't be using any other raid frames anywhere soon. So, having to switch from party to raid group each time I join a raid in order to not see the party frames is a tad if not a lot annoying.
Maybe it should work, maybe my version is bugged or something, but I can't for the life of me, make the party frames go away while joining a raid. I even made new groups disabling/enabling what I wanted, still nothing.
If there is something I am doing wrong or if there is indeed a way to make the party frames disappear as there was in 3.0 version please point it out.
The first thing I noticed is updates/rewrites to Buff/Debuff/Combopoint interface and the new configuration system consisting of layout _profiles_, which after a while becomes very, very comfortable.
In PB3 you had to find every exclusive seperate frame to edit their unique layout, while in PB4 you can simply use a pre-configured (by you, ofc) layout with the layout profile management implemented in PB4.
After a while though, I'm almost up to as many profiles as there is unique unit frames, but it's good to know I have the option to simply use the same Profile for "Focus Target" as "Focus Target Target" or "Target Target" etc, without trying to duplicate the same settings in each of the unitframes. Neat!
I am happy with the direction this interface is going and if there's anything I really can critizise it has to be the Raid interface and CPU power it consumes. In 40 man battlegrounds as a healer with people joining and leaving it becomes quite painful when the Raid interface is hogging the processor everytime someone leaves/joins/regroups (now someone might claim this is due to bad configuration from my part, however as an oldschool pb3 configurator I feel certain that there is solutions to this).
In raids outside of battlegrounds it's flawless and a piece of beauty, both as healer, dps and tank, and the only additional addons I need is Recount, Omen Threat Meter and DBM, for obvious reasons. Recommended for all, for anything!
Is anybody can help to write lua code for "Name" inscription, thus what name color was "ClassColor" if target player and "HostileColor" if target mob
(~IsMouseOver ? (Name:ClassColor:Truncate(40) \" \" Level:DifficultyColor \" \" SmartRace:HostileColor \" \" Class:ClassColor))]" (Base;Unit). ...bs\LibDogTag-Unit-3.0\Categories\Characteristics.lua:583: attempt to call global 'GetDifficultyColor' (a nil value):
<string>:"local _G = _G;...":114: in function <[string "local _G = _G;..."]:21>
(tail call): ?:
<in C code>: in function `xpcall'
LibDogTag-3.0-90203 (PitBull4):301: in function <...AddOns\PitBull4\libs\LibDogTag-3.0\LibDogTag-3.0.lua:289>
PitBull4-r20090616012413\libs\LibDogTag-3.0\Events.lua:585: in function <...erface\AddOns\PitBull4\libs\LibDogTag-3.0\Events.lua:495>
2nd error:
LibDogTag-3.0.90203: Error with code "[(IsMouseOver ? MP:Short:Color(\"76B3EC\") \" || \" MaxMP:Short:Color(\"377BBC\")) (~IsMouseOver ? (Name:ClassColor:Truncate(40) \" \" Level:DifficultyColor \" \" SmartRace:HostileColor \" \" Class:ClassColor))]" (Base;Unit). ...bs\LibDogTag-Unit-3.0\Categories\Characteristics.lua:583: attempt to call global 'GetDifficultyColor' (a nil value):
<string>:"local _G = _G;...":114: in function <[string "local _G = _G;..."]:21>
(tail call): ?:
<in C code>: in function `xpcall'
LibDogTag-3.0-90203 (PitBull4):301: in function <...AddOns\PitBull4\libs\LibDogTag-3.0\LibDogTag-3.0.lua:289>
LibDogTag-3.0-90203 (PitBull4):408: in function `AddFontString'
PitBull4-r20090616012413\Modules\DogTagTexts\DogTagTexts.lua:196: in function `AddFontString'
PitBull4-r20090616012413\ModuleHandling\TextProviderModule.lua:116: in function `UpdateFrame'
PitBull4-r20090616012413\ModuleHandling\Module.lua:271: in function `Update'
PitBull4-r20090616012413\UnitFrame.lua:527: in function `Update'
PitBull4-r20090616012413\UnitFrame.lua:553: in function `UpdateGUID'
PitBull4-r20090616012413\Main.lua:1136: in function `CheckGUIDForUnitID'
PitBull4-r20090616012413\Main.lua:1141: in function `?'
CallbackHandler-1.0-3:146: in function <...ted\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:146>
<string>:"safecall Dispatcher[1]":4: in function <[string "safecall Dispatcher[1]"]:4>
<in C code>: ?
<string>:"safecall Dispatcher[1]":13: in function `?'
CallbackHandler-1.0-3:91: in function `Fire'
AceEvent-3.0-3 (Afflicted):70: in function <...\AddOns\Afflicted\libs\AceEvent-3.0\AceEvent-3.0.lua:69>
<in C code>: in function `TargetUnit'
Interface\FrameXML\SecureTemplates.lua:379: in function `handler':
Interface\FrameXML\SecureTemplates.lua:487: in function `SecureActionButton_OnClick':
Interface\FrameXML\SecureTemplates.lua:528: in function <Interface\FrameXML\SecureTemplates.lua:520>:
I was using Pitbull 3 and had it set so that health bars for my targets, pets, focus, and target's target were class colored. This worked for all mods, whether they were players or NPC mobs. I then reset my profile accidentally and from then on, even though "class color" was checked in the health bar section, NPC mob health always used the health gradient colors.
I switched to Pitbull 4 now and I would like to know how to make the health bars for my target, target's target, focus, and pet show up class colored. I have the Class Color check boxes checked, and when I target myself or any other player the health bar is Class Colored, but not for NPC mobs.
I know that it did work in PB3 but after messing up my profile I couldn't get it to work again, and I am having the same problem in PB4. Class colored text works correctly for all targets however.
Please help
It would be pretty amazing if portraits were reverse-able! :>
How would I replace these colors for hex codes for more specific colors?
[MP(known=false, unit="player"):Cyan " | ":Red] [MaxMP(known=false, unit="player"):Yellow]
Also what do I use for target and target of target? Or do I need to create a new layout?