PitBull Unit Frames 3.0
Please note that PitBull3 is no longer being actively developed. On top of lack of active development itself, it's based on the Rock framework which itself is no longer maintained either.
I strongly recommend that users migrate to PitBull4. You can not convert your config from PitBull3 and must reconfigure.
PitBull4 itself can be found at:
http://wow.curse.com/downloads/wow-addons/details/pitbull4.aspx
You can find guides for setting it up at:
http://www.wowace.com/addons/pitbull4/pages/guide/
And the FAQ here:
http://www.wowace.com/addons/pitbull4/pages/faq/
While PitBull4 is still in beta it is fully functional and has more features than PitBull3. It is actively developed on and bug fixes made regularly.
I do not plan on making any fixes to PitBull3 once Cataclysm releases. So you have plenty of time to make the migration.
Accepting paypal donations to [email protected]
PitBull is a Unit Frames addon that provides maximal customization and undergoes rigorous efficiency testing. It is created in a modular framework, which allows for mulitple authors to put their skills to work creating this great project.
It has support for many different kinds of units: player, target, pet, pet's target, target of target, target of target of target, focus, focus' target, party, party pets, party targets, party pet targets, raid, raid pets, raid targets, main tanks, main tank targets, main assists, main assist targets, etc.
Note: Almost all texts are configurable using the LibDogTag-3.0 format. See http://old.wowace.com/wiki/LibDogTag-3.0 for details or type '/dog' in-game.
Modules:
- Aura - track any buffs or debuffs on the shown units. Also has the ability to highlight based on a curable debuff.
- Banzai - highlight units that have threat on them.
- BarFader - allow for smooth fading when units gain or lose health/mana.
- CastBar - attach a cast bar to the applicable units: covers player, pet, party, target, focus, etc.
- CombatIcon - show an icon when the unit is in combat.
- CombatFader - fade unit out when out of combat.
- CombatText - show realtime damage/healing text on the unit frame.
- ComboPoints - for Rogues and Druids, show combo points.
- DruidManaBar - for Druids, show a mana bar when in Cat/Bear form.
- ExperienceBar - for the player and hunter pets, show an experience bar.
- HealthBar - show current health.
- HappinessIcon - show an icon on the pet frame to indicate its happiness.
- HideBlizzard - hide unneeded Blizzard frames .
- Highlight - show a highlight when hovering over a frame or targetting said frame.
- LeaderIcon - show the leader of the party.
- MasterLooterIcon - show the master looter of the raid.
- Portrait - show a 3D, 2D, or class portrait.
- PowerBar - show a mana/energy/focus/rage bar.
- PvPIcon - show an icon when the unit is in PvP mode.
- RaidTargetIcon - how the raid target icon (Skull/Triangle/etc.)
- RangeCheck - fade the unit frame slightly when the unit is out of range.
- ReadyCheckIcon - show Ready Check icon based on if the unit is ready or not.
- ReputationBar - for the player, show a reputation bar.
- RestIcon - show an icon if the player is resting.
- Spark - Graceful display of energy ticks and the spellcasting five-second-rule.
- ThreatBar - show a threat bar on the unit frame.
- TotemTimers - shows Totem timers for the PitBull player frame.
- VisualHeal - for healers, shows a bar showing the estimated heal amount while casting.
- VoiceIcon - show an icon based on whether or not the unit is talking.
Note: all modules can be enabled or disabled on-demand. Disabled modules don't take up any extra memory or CPU power.
since a while addons are not allowed to focus "automatically", so you will have to make a macro and key bind it to be able to focus quickly
ID: 1
Error occured in: AddOn: PitBull
Count: 1
Message: Error: AddOn PitBull attempted to call a forbidden function (FocusUnit()) from a tainted execution path.
Debug:
[C]: FocusUnit()
..\FrameXML\UnitPopup.lua:1267: func()
..\FrameXML\UIDropDownMenu.lua:575: UIDropDownMenuButton_OnClick()
[string "*:OnClick"]:1:
[string "*:OnClick"]:1
Date: 2010-04-04 11:06:48
ID: 1
Error occured in: Global
Count: 1
Message: ..\AddOns\PitBull\PitBull.lua line 1154:
attempt to perform arithmetic on local 'r' (a table value)
Debug:
(tail call): ?
...libs\LibRockModuleCore-1.0\LibRockModuleCore-1.0.lua:400: CallMethodOnAllModules()
PitBull\PitBull.lua:4591: UpdateFrame()
PitBull\PitBull.lua:5108: PopulateUnitFrame()
PitBull\PitBull.lua:4039:
PitBull\PitBull.lua:4035
[C]: ?
...s\PitBull\libs\LibRockEvent-1.0\LibRockEvent-1.0.lua:469:
...s\PitBull\libs\LibRockEvent-1.0\LibRockEvent-1.0.lua:415
(tail call): ?
[C]: CameraOrSelectOrMoveStop()
[string "CAMERAORSELECTORMOVE"]:4:
[string "CAMERAORSELECTORMOVE"]:1
any idea what this means?
Important announcement about PitBull Unit Frames.
Effective today development on PitBull4 is ceasing. We will be resuming development of PitBull3. We've heard the call of users who have brought their difficulties in switching to PitBull4.
The lack of a way to migrate settings to PitBull4 to PitBull3 has caused users a great deal of frustration in switching. Especially in light of the new configuration style of PitBull4. Layouts while very powerful have proven to be too confusing.
Many features that are simply not possible with PitBull3 will be lost in going back. For instance the ability to have as many frames as you wanted for any given unit (which was almost done for singletons and not just groups), advanced aura filtering that you can control, multiple text providers so you can choose not to use LibDogTag, and rune support for Death Knights.
Users who have migrated to PitBull4 should immediately begin migrating their configurations back to PitBull3.
Was an April Fool's Day joke.
Effective today development on PitBull4 is ceasing. We will be resuming development of PitBull3. We've heard the call of users who have brought their difficulties in switching to PitBull4.
The lack of a way to migrate settings to PitBull4 to PitBull3 has caused users a great deal of frustration in switching. Especially in light of the new configuration style of PitBull4. Layouts while very powerful have proven to be too confusing.
Many features that are simply not possible with PitBull3 will be lost in going back. For instance the ability to have as many frames as you wanted for any given unit (which was almost done for singletons and not just groups), advanced aura filtering that you can control, multiple text providers so you can choose not to use LibDogTag, and rune support for Death Knights.
Users who have migrated to PitBull4 should immediately begin migrating their configurations back to PitBull3.
It only took about an hour but I got PB 4 running exactly the same as my PB 3 setup, and with a lot of added features. Less memory usage, more fps. Thanks to CK and Shef for all your hard work (with PB 3 and esp PB 4).
Please note that PitBull3 is no longer being actively developed. On top of lack of active development itself, it's based on the Rock framework which itself is no longer maintained either.
I strongly recommend that users migrate to PitBull4. You can not convert your config from PitBull3 and must reconfigure.
PitBull4 itself can be found at:
http://wow.curse.com/downloads/wow-addons/details/pitbull4.aspx
You can find guides for setting it up at:
http://www.wowace.com/addons/pitbull4/pages/guide/
And the FAQ here:
http://www.wowace.com/addons/pitbull4/pages/faq/
While PitBull4 is still in beta it is fully functional and has more features than PitBull3. It is actively developed on and bug fixes made regularly.
I do not plan on making any fixes to PitBull3 once Cataclysm releases. So you have plenty of time to make the migration.
We're working on though it's not done yet a way to share configs more easily, but this is only to share configs from one PitBull4 user to another PitBull4 user.
Due to the very different designs of PB3 and PB4 it's not possible to migrate configurations. Sorry.
I tried PB4 today but I guess Ill just have to try to learn how to confgure it.
http://www.wowace.com/addons/pitbull4/pages/guide/making-layouts-and-applying-to-frames/
It should help you a lot.
Commenting out line 872 of Pitbull.lua seems to fix this issue, though I have no idea what I've just disabled. To be more specific, change:
frame:SetTexCoordModifiesRect(false)
to
--frame:SetTexCoordModifiesRect(false)
Message: ..\AddOns\PitBull\PitBull.lua line 5027:
Deleting a frame of type "Frame" that still has 3 regions
Debug:
[C]: ?
[C]: ?
PitBull\PitBull.lua:886:
PitBull\PitBull.lua:844
PitBull\PitBull.lua:5027: _ClearUnitFrame()
PitBull\PitBull.lua:5072: object_method()
...ns\CowTip\libs\LibRockTimer-1.0\LibRockTimer-1.0.lua:289:
...ns\CowTip\libs\LibRockTimer-1.0\LibRockTimer-1.0.lua:227