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!

@denverchenc82 good to hear =)

Hi, a little LUA error with "Essence" Evoker resource :

445x ...s/Blizzard_UnitFrame/Mainline/EssenceFramePlayer.lua:64: attempt to compare local 'peace' (a secret number value, while execution tainted by 'PitBull4')

[Blizzard_UnitFrame/Mainline/EssenceFramePlayer.lua]:64: in function <...s/Blizzard_UnitFrame/Mainline/EssenceFramePlayer.lua:62>

@NoNe10 cheers! should be fixed in p101 - please give it a try=)

@NoNe10 *v104 - i might have inserted som eissues and needed to fix them :D

unable to use the aura filter feature; does anyone know how to get it working?

@Cognition I am not sure if the feature has been removed or if I accidentally altered the settings. I tried following the advice from various AI responses and posts, but the issue remains unresolved.

@Cognition cheers! could you just tell me about what version we are talking? retail or forever and whats aura filtering for you :D

@Cognition when i understand it correctly- you are talking about the old aura filtering method - that god disabled with midnight - i have reenabled it but its currently untested so use it with care and i am open to feedback! (v99 btw)

@Rumorix Exectly wanted