Get an Epic Experience with Premium

PitBull Unit Frames 4.0

Unit Frames Login to Add Favorites
  • 33 Likes
  • World of Warcraft
  • 19,348 Monthly Downloads
  • Supports: 5.2.0
  • 3,070,027 Total Downloads
  • Updated 04/01/2013
  • Created 08/01/2008
  • 2,948 Favorites
  • Project Site
  • Comments
  • Release Type: Beta
  • License: All Rights Reserved
  • Newest File: v4.0.0-beta44
or
Support development! **
Donate

About PitBull Unit Frames 4.0

PitBull4 is a continuation of PitBull.

Differences from PitBull 3:

  • It's mostly done, but not entirely done thus why there are still only betas (despite this it is still very stable).
  • Documentation is written before functions
  • Much easier for third-party extensions.
  • Options will be much, much simpler. In 3.0, there's about 200 panels that you can mess with, it's overwhelming. I want to bring this down to somewhere around 10.
    • Layouts are defined deterministically and unit groups use the layout rather than ad-hoc layouts on a per-unit basis. This will make setting up your unit frames far, far easier.
    • Due to some decisions made, 4.0 is actually more configurable than 3.0. As a layout designer, you will have a lot more control over how things look. You can have different fonts on the same frame, different textures, more precise positioning, and a whole slough of other things.
  • CPU Efficiency will be taken much more seriously.
  • It uses Ace3 instead of Rock.

FAQ: http://www.wowace.com/addons/pitbull4.../faq/.

Guide: http://www.wowace.com/addons/pitbull4.../guide/.

If you want to help localize PitBull in your language, go to http://www.wowace.com/projects/pitbul.../localization/.

Forum thread: http://forums.wowace.com/showthread.php?t=15552...

tag v4.0.0-beta44
6c15111676f0b9c1d2588f965344cab5722aecf0
Shefki <shefki@shefki.org>
2013-04-01 20:06:35 -0700

Tagging as v4.0.0-beta44

--------------------

Shefki:
    - Oops duplicated a line unintentionally.
    - Add support for warlock green fire to the BurningEmbers module.
    - Set the extra2 value to 0 for other bar modules (prevents ghost extra values from showing up when bars get reused).
    - Add support for showing absorbs in the VisualHeal module.
    - Add a 2nd extra bar to BetterStatusBar.
    - Return to old style menus for raid frames since Blizzard has a bug in the new menu system.  Includes a somewhat ugly hack around Clique forcing the use of the new menu system.
    - Display friendships properly in the ReptutationBar & LuaTexts.
    - Remove pre-5.1 compatibility from Aura Filters.
    - Remove pre 5.1 support from Chi module.
    - Remove pre-mop compatibility from UnitFrame.lua
    Conflicts:
    
        UnitFrame.lua
    - Remove pre-mop compatibility in ThreatBar module.
    - Remove support for old guid format.
    - Remove check for MoP from ShadowOrbs module.
    - Remove pre-mop compatibility from ReadyCheckIcon module.
    - Remove pre-mop compatibility from RangeFader module.
    - Remove pre-mop compatibility from RaidTargetIcon module.
    - Remove pre-mop compatibility from MasterLooterIcon module.
    - Remove pre-mop compatibility from the LuaTexts script environment.
    - Remove pre-mop compatibility from LuaTexts module.
    - Remove pre-mop compatibility from LeaderIcon module.
    - Remove pre-mop compatability from HolyPower module.
    - Remove pre-mop compatability from HealthBar module.
    - Remove pre-mop support from Main.lua
    - Remove pre-mop support from Eclipse module.
    - Remove pre-mop support for raid/party events from HideBlizzard module.
    - Remove pre-mop code to support ranged slot.
    - Enable Totems module for Mages with Rune of Power.
    - Remove pre-MOP compat from Totem module.
    - Just stop using MAX_ARENA_TEAM_MEMBERS entirely, it wasn't really the right constant anyway.
    - Switch to using the new 5.2 based popup menu system.  This will allow the SetFocus/ClearFocus, Dismiss etc...  However, this also does remove the feature to add Ready and Role Check menus for group leaders.

Comments

First Previous Page 215 of 242 Next Last
  • #511
    Thanks a lot, and thanks for giving us this. If I had spare cash it would be in your pocket.
  • #477
    Does anyone happen to know if there is a way to show Main Tank and Main assists like there was with 3.0? So far I like 4.0 more but sometimes I use multiple main assists to coordinate and it helps if I am able to see these raid assists and their targets.
  • #505
    Create a group, set the Unit group drop down to Raid, Go to the filtering tab and choose Main tanks or Main assist depending on what you want. If you want Main tank/assist targets use Raid targets for the unit group and so on...

    Note, assist only uses the blizzard assist targets at current. Tanks will use oRA2 and CT_RA in preference to Blizzard tanks if they are set.
  • #514
    Thanks!
  • #481
    I'm interested in this as well.
  • #476
    Hi,

    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
  • #490
    Will be fixed in the next release. Been fixed in the alpha builds for a while.
  • #470
    I am a tad frustrated with this version, I'm thinking of going back to 3.0 tbh.
    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.
  • #485
    In the groups setup go under filtering and try checking/unchecking the proper option and see if that helps?
  • #468
    Okay, after being a dedicated pitbull3 fan for a while I decided to try the new version out, despite losing my old configuration setup, which, by now have grown into a piece of art if you ask me.

    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!
  • #504
    I have a feeling that this is related to LibDogTag (which for embedded users still loads despite being unused if you're using LuaTexts). I'm taking steps to stop this from happening which should improve performance for those of you using an embedded setup (if you don't know if you are, you are).
  • #467
    Keep up the awesome work, so far I love it. One question though. Is it possible to disable the self-player frame. I was looking around, but I couldn't find it. - Thanks
  • #503
    Units, player, uncheck the enable box.
  • #465
    getting a couple of errors, not sure what to do.

    (~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):

    (tail call): ?:
    : in function `xpcall'
    LibDogTag-3.0-90203 (PitBull4):301: in function
    PitBull4-r20090616012413\libs\LibDogTag-3.0\Events.lua:585: in function



    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):

    (tail call): ?:
    : in function `xpcall'
    LibDogTag-3.0-90203 (PitBull4):301: in function
    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


    : ?
    :"safecall Dispatcher[1]":13: in function `?'
    CallbackHandler-1.0-3:91: in function `Fire'
    AceEvent-3.0-3 (Afflicted):70: in function
    : 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 :
  • #491
    You need to update. You're using a version from pre 3.2 which doesn't have the updated LibDogTag for the 3.2 changes.
  • To post a comment, please login or register a new account.
Login to Curse

Don't have an account? Create One.

Get an epic experience with Curse Premium
  • Faster addon downloads
  • Premium-Only Beta Giveaways
  • Ad-Free Curse experience
  • Premium Curse Client
  • and many More Features
  • Learn More »

Infinite Crisis NA

Get Your Preferred Access Code!