Thank you for making Pitbull compatible with WoW Forever. Currently using Pitbull-Lorenzo-Forever-42. A few issues I'm having (which may just be my inability to use the addon properly) and not been able to get to work but which did work in other WoW versions for me: 

- can't get rogue poisons to show up in buff auras. 

- can't output unit power as a specific color other than white (for any type mana/rage/energy). also can't seem to output unit power plus other strings or text. It will just display unit power and ignore anything else.

- can't figure out how to create/edit filters for Auras. Specifically trying to only display buffs/debuffs that originated from my character or only display specific debuffs for instance. maybe i'm just missing it somewhere.

Again, I apologize if this is just due to my ignorance at using the addon.

@bagelobo Hey, thanks a lot for the detailed feedback, and no need to apologize! :)

These are all valid things to bring up, especially since they worked in previous versions of PitBull4.

I've added all three issues to my list:

- **Rogue poisons:** I'll investigate how weapon enchants and poison buffs are handled in the current Forever client.

- **Power text formatting:** I'll look into why custom colors and additional text aren't being displayed correctly. Some of this may be related to the newer protected-value restrictions.

- **Aura filters:** The filter editor still exists in the code, but its integration with the options needs some attention. I'll investigate restoring proper access to custom filters, including filtering by caster and specific spells.

I can't promise all three will be fixed immediately, but I'll investigate them for the next build.

Thanks again for testing v42 and taking the time to report these issues. Feedback like this really helps!

Cheers,

Rumorix

@bagelobo please test v43 when you have some spare time <3

@bagelobo Are you by chance using older saved variables that need to be replaced? I can confirm that on v42 rage shows red/energy shows yellow, I am able to cycle through any color I want under custom color and apply it for powers. Furthermore all text is working correctly.

Try moving your pitbull.lua to desktop and see if it all works on a stock profile. May just need to redo your UI.

Aura filters - There is a semi-workaround available for this currently, you can set layout editor > aura > icon size to 4 > icon size for my auras to 16-20, so other people's are tiny and yours stay normal size - tested and it seemed to work for me inside instance.

@bagelobo Hey @bagelobo! Thanks for your feedback! :)

@ixlone also suspected that some of these issues might be related to older SavedVariables or profiles that aren't fully compatible with our newer PitBull4 Forever implementation.

He confirmed that power colors and custom texts are working correctly for him on v42, including rage showing red, energy showing yellow, and custom power colors.

Are you using an older PitBull4 profile from a previous version, or did you start with a fresh profile?

Could you try backing up your `PitBull4.lua` SavedVariables file, temporarily moving it out of the folder while WoW is closed, and testing with a fresh default profile?

It would be interesting to see whether the power colors, custom texts, and rogue poisons behave differently.

Thanks again for helping us investigate! :)

Currently uploading a 12.1.5 version for Pitbull - no major changes - just to get it running for 12.1.5 - feel free to give me some feedback =)

https://1drv.ms/f/c/25688cb7a16be526/IgDvr810POcETbKR5MaoqZTgARoMWi3misaF8nw5m6yD2iU

@Rumorix Would it be simple to make it so you can ping a target like how you changed the self ping option?

@Cedande should be working now

@Rumorix Had this start after joining a key

426x Blizzard_UnitFrame/Mainline/UnitFrame.lua:807: attempt to compare local 'maxValue' (a secret number value, while execution tainted by 'PitBull4')

[Blizzard_UnitFrame/Mainline/UnitFrame.lua]:807: in function 'UnitFrameHealthBar_Update'

[Blizzard_UnitFrame/Mainline/UnitFrame.lua]:167: in function 'UnitFrame_Update'

[Blizzard_UnitFrame/Mainline/PartyMemberFrame.lua]:298: in function 'UpdateMember'

[Blizzard_UnitFrame/Mainline/PartyMemberFrame.lua]:478: in function 'OnEvent'

[Blizzard_UnitFrame/Mainline/UnitFrame.lua]:991: in function <...ace/AddOns/Blizzard_UnitFrame/Mainline/UnitFrame.lua:989>

Locals:

statusbar=StatusBar <PartyFrameTemplates.xml:150>{

currValue=<secret number>

HealAbsorbBar=Frame <PartyFrameTemplates.xml:158>

capNumericDisplay=true

TextString=FontString <PartyFrameTemplates.xml:204>

TotalAbsorbBar=Frame <PartyFrameTemplates.xml:159>

lockShow=0

cvarLabel="STATUS_TEXT_PARTY"

lockColor=true

partyFrame=Button <PartyFrame.lua:56>

OtherHealPredictionBar=Frame <PartyFrameTemplates.xml:157>

controlsShownState=true

unitFrame=Button <PartyFrame.lua:56>

textLockable=1

unit="party1"

cvar="statusText"

Background=Texture <PartyFrameTemplates.xml:164>

RightText=FontString <PartyFrameTemplates.xml:214>

LeftText=FontString <PartyFrameTemplates.xml:209>

zeroText="Dead"

OverAbsorbGlow=Texture <PartyFrameTemplates.xml:169>

disconnected=false

forceHideText=false

frequentUpdates=true

MyHealPredictionBar=Frame <PartyFrameTemplates.xml:156>

OverHealAbsorbGlow=Texture <PartyFrameTemplates.xml:170>

HealthBarTexture=Texture <PartyFrameTemplates.xml:199>

}

unit="party1"

maxValue=<secret number>

(*temporary)="party1"

(*temporary)=<secret number>

(*temporary)=nil

(*temporary)=nil

(*temporary)=nil

(*temporary)=nil

(*temporary)="attempt to compare local 'maxValue' (a secret number value, while execution tainted by 'PitBull4')"

Quote from: Grymm

I'm sorry but can we please get Rumorix added to the white list or whatever it is to allow them to push updates to CurseForge? They've been far more communicative with the users here, and while I will always respect devs right to live life it's been basically an entire major patch cycle of "the update is coming soon". It looks like *an* update is basically available and it would be great if people actually had access to that plus all the libraries typically bundled with a CF release.

Same question !

@Rumorix : Did you tried to contact nebula169 which update Pitbull since 2019 ?

https://www.curseforge.com/members/nebula169/projects

@NoNe10 yes i allready did, i am currently only allowed to distribute my versions via the way i do (hosting it somewhere thats not curseforge)

sorry to say =/

I'm using the forever‑037 version of this addon.

Health values display correctly as raw exact numbers, but mana, rage, energy and other power types only show percentages instead of real values.

I’ve tried using native WoW APIs `UnitPower()` and `UnitPowerMax()` within LuaTexts custom scripts, but the issue still remains. The health text uses identical script logic and works perfectly. Could you tell me what might be causing this issue?

@denverchenc82 Hey!

I've released **PitBull4 Forever v39**. I haven't changed the power display logic yet, as another tester confirmed that absolute power values work correctly for Priest and Druid.

Could you tell me which class, specialization, and unit frame you're using, and whether you're using the built-in LuaTexts "Absolute" preset or a custom script?

This should help me determine whether the percentage fallback is caused by Blizzard's secret-value restrictions or something specific to the current configuration.

Thanks for your feedback! :)

@Rumorix Where can we get this Forever version please?

@Rumorix I deleted my old Lua files copied from MOP. Everything works correctly now under a fresh default profile. It seems reusing the MOP config directly caused this issue.

Also I encountered 3 other issues:

1. After selecting a target and then clearing it, the portrait of the `target` unit frame would remain stuck on screen. I found some code in `Main.lua` that clears leftover visuals for `targettarget` and `focus` frames. Adding `target` there fixed this problem.

2. When moving unit frames, the `player` and `target` frames stay attached to the mouse and cannot stop dragging. I located drag-stop logic for `targettarget` and `focus` inside `UnitFrame.lua`. Adding `target` and `player` to that section resolved the dragging issue.

3. The `LeaderIcon` still does not display at all.

@Venomisto https://onedrive.live.com/?id=/personal/25688cb7a16be526/Documents/Pitbull4 - by rumorix (forever)&listurl=/personal/25688cb7a16be526/Documents&ithint=folder&migratedtospo=true&redeem=aHR0cHM6Ly8xZHJ2Lm1zL2YvYy8yNTY4OGNiN2ExNmJlNTI2L0lnRGdXWVhic292Z1M3N2NfUW1FQ2lmTUFkVlRXVjZEaXdxSjJzT0xiR3JmSGY4&ga=1

@denverchenc82 im checkng on it =)

@denverchenc82 Hey!

Thanks a lot for investigating these issues and sharing your findings!

Great to hear that the power values are working correctly with a fresh profile. That helps narrow the original issue down to the old MoP configuration rather than the power APIs.

We've already made some changes to target-frame cleanup and drag handling in previous Forever versions, so I'll compare your findings against the latest code to make sure Player and Target are properly covered.

I'll also investigate the missing LeaderIcon, as that still needs attention.

Really appreciate the detailed feedback and especially the code-level troubleshooting! :)

@denverchenc82 I'd try moving your pitbull.lua saved variables to desktop and seeing if they work on a fresh stock profile. If it works, need to just redo your configs - I had to wipe my settings a couple of times over the various version testing (thought I have been messing with a lot of stuff while testing, so could just be me).

@ixlone I deleted my old Lua files copied from MOP. Everything works correctly now under a fresh default profile. It seems reusing the MOP config directly caused this issue. I will rebuild my setup manually. Thanks a lot for your help!