Yes, if you have MobHealth3 installed, you can basically just delete it. PitBull uses LibMobHealth-4.0, which you do not have to install - it comes with Pitbull. If you install it as a seperate addon, tho, you get access to additional options. This will take additional space on your HD, but it will only get loaded once. If you have MobInfo2 installed and remove it, you wil loose the droprates info and stuff like that.
Is it just me that never been able to figure out how that makes sence as a preset for class text? I mean, in classtags ppl will most lightly wanna know level and CLASS in a shorter display, not level and race....
Well, if you fight mobs, class is almost totally uninteresting. Maybe the field should be renamed to "Description" or something like that. By default, it should display class only for players. And suppress the display of "not specified" and such. Not hard to make a DogTag that does just that, tho.
PitBull_PowerBar\PowerBar.lua:287: bad argument #1 to 'unpack' (table expected, got nil)
PitBull-3.0r68199\PitBull.lua:4949: in function `_PopulateUnitFrame'
PitBull-3.0r68199\PitBull.lua:5050: in function `object_method'
LibRockTimer-1.0-1118 (LibRockTimer-1.0):289: in function <...terface\AddOns\LibRockTimer-1.0\LibRockTimer-1.0.lua:227>
Getting this sometimes (not every time) when joining a group.
Pitbull\libs\Threat-1.0\ThreatNPCModuleCore.lua:25: Cannot find a library instance of "LibBabble-Boss-3.0"
Had a similar problem with other addons (Assessment and Omen) using Threat-1.0. I just deleted the Threat-1.0 folder in those addons' libs folder and installed Threat-1.0 as a separate addon. Not the nicest way, but works for now.
That is not true. The new lib does not wipe mob data right away. But by default, it only keeps a certain number of entries, so that the total size stays at about 50KB (or 1000 entries?). If you install the lib as a standalone addon, you get actions to make it not save data at all, or to keep more entries (up to "all of them").
Pitbull is using libmobhealth-4.0, therefore i removed any other mobhealth libs and addons and it worked smoothly
Yeah, well, some people use MobInfo2, which does more than just gather data about a mob's health. Those people probably do not want to miss their extra-data like drops, or whether a mob is a runner. Would be cool if you could disable the use of LibMobHealth-4.0 for such cases. No need to gather the data twice.
Do you have MobHealth3 running as well? Pitbull has its own method of determining a mob's health now. Friend of mine claims that the strange numbers vanished when he deleted MobHealth3. No idea if that is true, tho. :)
I switched to PitBull_AltAura, and I have no more lag during buffing up in battlegrounds. BUT... dunno how to explain. Here some pics.
<-- My target, just that I no longer have anything targetted. When un-targetting, this huge... thing appeared.
<-- My raid frames, after buffing the whole BG thoroughly. The buff symbols used to appear smallish, and right next to the health bars.
Sorry for the huge pics, but I seriously did not know how to explain my problem in fewer than a hundred words. ^^
Is anyone else having issues with estimated heals? Instead of placing the estimated heal directly next to the remaining health, it offsets the bar to the right by a distance equal to their existing health (in other words, the more health they have, the more the estimated heal is shifted to the right). The overheal text is still in the correct place however. It does this for all unit frames.
Maybe take a look at the SVN VisualHeal. Its Pitbull module is really good, and it gets the more useful the more people use VH.
During the beginning of AV battlegrounds (maybe others as well, but I only do AV right now), I get nasty freezes. Memory usage of Pitbull increases massively during that time (from 2something MB to well over 6). After a few such stutters where I am basically can't move, all is over and I can play normally. Most of the time, this is limited to the buff-up period, but when I enter the battleground late, I am a sitting duck for a while.
Only happens with raidframes enabled. I do not get this when I disable them. Is this a known behaviour?