I'm sure I'm missing something, but I don't see Chi on my pitbull frame.

In reply to nebula169: Thank you!

Last update completely broke the addon for me. I don't see anything and cannot turn on the frames

In reply to omarthemediocre: I also had the same issue, which was annoying to say the least in the middle of a dungeon. I was able to roll mine back to 4.2.41 and that works without issue.

Quote from syal5:

In v. 4.2.42 arcane charges do not appear in player frame. This issue seems to be tied to multiple lua errors.

Yes I have the same problem after update on 4.2.42 but only with my mage

In v. 4.2.42 arcane charges do not appear in player frame. This issue seems to be tied to multiple lua errors.

Hi, for my player unit frame the class color works for the health bar, but for the party & raid frames it uses the green-orange-red setting even though class colors are enabled, anyone know a fix for this?

Hey. been using pitbull since 2009 ish - incredible addon and I couldn't play without it. Really grateful for all the work developing it over the years, thank you.

I was wondering, after they added the ping system one thing that is really useful is being able to Ping on the Target (or focus, or any frame for that matter) and it pings the person. For me however, this does not work. Sorry if I missed any setting or anything, but is it not possible to Ping a frame with Pitbull?

Thank you regardless and sorry for bothering!

Hello, this is a really solid addon but I have one question about something that has always bugged me. I have my Portrait set as a bar, height 5. The problem is that while most races look okay - their eye line is the focus of the bar - other races look really bad. For example if you have a male dwarf all you see is their nose.

There doesn't seem to be any vertical offset setting for portraits as a bar, only camera distance but I would love to be able to just offset the camera slightly up or down for some of these races so the bar always shows their eyes.

Would that be possible to make? I use a single profile for all of my characters so an offset that is race/bodytype specific would be good - but I would take any offset function and have multiple profiles for my alts if I could just get it right.

Anyway many thanks. These have been my main unit frames since around wrath so really good addon!

Hello

the retail standard wow raid frames can show private auras. For example Ky'veza, the "Assassination" and the "Twilight Massacre".

My PB debuff_show setting is: boss, default debuffs – and I even added manually those 2 spell IDs. But I can't get Pitbull to show them, has anyone a solution for this?

Because ElvUI can show those private auras too, I think there must be a way to pick them out for display outside of the standard blizzard frames.

Dear ckknight,

Any chance for a TOC update for 1.15.4 for Classic?

I don't see any issues or lua errors via BugSack/BugGrabber \o/

Hey everyone.

I love Pitbull. It's super intuitive. I love the way it handles groups and raid sizes and the different layouts that you can apply to each scenario.

Is there a way to force pitbull to only show dispellable debuffs on the party/group frames? Or enlarge them? I can't seem to find the option. SUF has it, as do other UF addons. Am I blind? Can someone help? :)

I appear to have a small error regarding an unfader function. I am not too sure how to handle this.

1x ...cePitbull4_CastingUnfader/CastingUnfader.lua:1: attempt to call global 'GetAddOnInfo' (a nil value)

[string "@Pitbull4_CastingUnfader/CastingUnfader.lua"]:1: in main chunk

Locals:

(*temporary) = 5

(*temporary) = nil

(*temporary) = "PitBull4_"

(*temporary) = "attempt to call global 'GetAddOnInfo' (a nil value)"

Repeatedly getting this error message via bugsack while Vakash is equipped:

5057x PitBull4/Modules/Aura/Update.lua:169: attempt to call field 'SurfaceArgs' (a nil value)

In reply to Icytroll:

When i read your comment i also though it was because of my Fyrakk weapon. Gholak, the Final Conflagration and Fyr'alath the Dreamrender triggered the same error massage, while other weapons did not.

But as it looks like its not the weapons, it is the Howling Rune or Buzzing Rune consumable that triggers this error.

As soon as i click away the rune buff, the error counter stops.