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
THANKS
Ever since 4.1 Pitbull in raid groups drops my fps down to 1-10 when I normally get 80+. I have had pitbull configured in this way for a long time. And never had a fps issue in raids (pvp or pve). Ever since 4.1 I have been. Disabling pitbull corrects the issue. At one point after 4.1 release I couldn't even do 5 mans for the very same reason. As soon as a encounter would happen it would just plunge like a rock. Though time after 4.1 and 5 mans are again workable .. same with 10 mans (sort of) ... from 10+ raids is when fps start to heavily occur. What has changed from 4.0 to 4.1 that would cause pitbull on my end to suck up so much fps. Any help is appreciated =)
http://www.flaax.de/img/cpbug.jpg
On the top left cornor you can see the default cp from blizzard after the kill of magmaw. Is there a way how I could try to fix it?
~~~~~~~~~~~~~~~~~~~~~~
Date: 2011-05-06 14:52:02
ID: 2
Error occured in: Global
Count: 1
Message: PitBull4_LuaTexts:target:Lua:Name caused the following error:
PitBull4_FontString_1:SetFormattedText(): Font not set
Debug:
(tail call): ?
PitBull4_LuaTexts\LuaTexts.lua:768:
PitBull4_LuaTexts\LuaTexts.lua:755
PitBull4_LuaTexts\LuaTexts.lua:823:
PitBull4_LuaTexts\LuaTexts.lua:778
PitBull4_LuaTexts\LuaTexts.lua:1362: AddFontString()
...ddOns\PitBull4\ModuleHandling\TextProviderModule.lua:118: UpdateFrame()
PitBull4\ModuleHandling\Module.lua:319: Update()
PitBull4\UnitFrame.lua:762: Update()
PitBull4\UnitFrame.lua:788: UpdateGUID()
PitBull4\Main.lua:1389: CheckGUIDForUnitID()
PitBull4\Main.lua:1400: ?()
...Ons\Ace3\CallbackHandler-1.0\CallbackHandler-1.0.lua:147:
...Ons\Ace3\CallbackHandler-1.0\CallbackHandler-1.0.lua:147
[string "safecall Dispatcher[1]"]:4:
[string "safecall Dispatcher[1]"]:4
[C]: ?
[string "safecall Dispatcher[1]"]:13: ?()
...Ons\Ace3\CallbackHandler-1.0\CallbackHandler-1.0.lua:92: Fire()
Ace3\AceEvent-3.0\AceEvent-3.0.lua:120:
Ace3\AceEvent-3.0\AceEvent-3.0.lua:119
[C]: CameraOrSelectOrMoveStop()
[string "CAMERAORSELECTORMOVE"]:4:
[string "CAMERAORSELECTORMOVE"]:1
~~~~~~~~~~~~~~~~~~~~~~~~
Honestly, FamBags is suddenly throwing a similar-sounding error, so I think it's something to do with a sharedmedia problem. But I haven't updated anything to do with my shared media, fonts, or Ace3, so I don't know what's happened. Any input would be appreciated. Right now, PitBull is just showing big black boxes, nothing at all is making it through.
But it may not be the problem. My bf uses the same three addons as those involved here - PitBull, FamBags, and MSBT - and doesn't have a problem. He even transferred his MSBT folder to mine (I updated it this morning but he didn't), and I still had the error. (He still doesn't.) I would suspect a fourth addon involved in some bizarre cross-wiring, except disabling MSBT was the only thing that made any difference for me.
PitBull4_FontString_1:SetFormattedText(): Font not set "
Its saying the Font you are using is not set. Chances are there is an issue with your Fonts you are using with Shared Media.
Its possible that you have multiple instances of Shared Media (some embeded and some not embedded) and the one that is loading first does not have all the fonts of the ones you want to use.
"Most automatic addon updaters delete addon folders before installing the new version. I'm not a huge fan of that behavior, but I can understand why they do it that way since it avoids other problems.
Did you have a custom font in the MSBT\Fonts directory? If so, the file is probably not there anymore and the other mods are trying to access a non-existent font file. MSBT is smart enough to recognize when a non-existent font file is specified and falls back to the default font. Most other addons just blindly use whatever font is specified and error out when it isn't there.
What I suggest to avoid that is to create a separate folder under <WoW>\Interface\Addons like MyCustomMedia or something unique and then specify it as the path when adding custom media as Interface
Addons
MyCustomMedia
WhateverFont.ttf. That way when automatic updaters run they won't wipe out your custom media."
The strange thing is I do have a separate SharedMedia_MyMedia/fonts folder in my Interface/Addons, which has my custom font in it, but PitBull and FamBags were referencing the MSBT font folder instead. When I put my font back in MSBT's font folder, the errors stopped. How can I get PitBull to reference the stand-alone font folder instead of MSBT's?