Hey @casualshammy, in one-or-more enemy scenario.. could you explain why my icon size of nameplate debuffs will change whether I'm selected on a target (with debuffs) or unselecting/reselecting to another affected target with debuffs; debuff icons become enlarged upon selection of a target and will not adhere to the (ideal) size/scale I've set whereas it seems to play nice on a separate target(s) in the background. Frame strata does not appear to change but icon sizing does - I've tried overlapping and stacking nameplates.

Thank you!

Edit: additionally, also looking for information on whether I can configure nameplate debuffs globally to only show from my character - thanks a lot!

Hi,

There are not batch editing currently. Unfortunately, you have to switch on Show only my auras option on per-spell basis. Maybe I'll add such option in the next release (if there are not conflicting filters).

Right, alright not a problem! I did find the scale slider for the target but my issues is that the iconography will enlarge to a different scale if it's not the subject of my target.. I think? I will check to see if this setting is not set to 1.0

Could you please make a screenshot / gif / video of this bug? I will also appreciate if you post a screenshot of your NameplateAuras' settings (Size & position tab) + name of your nameplate addon.

@casualshammy thank you expressing your interest in the problem - this very well could just be intended behavior and we're misunderstanding each other?
here is a video link of target dummy practice

No (other) nameplate addon is in use and I also checked my cvars for any suspicious variables I might've changed...

size & position tab!

Thanks again @casualshammy!

Looks like it's how Frame:SetScale method works... I have rewrited scaling-related code and will push beta soon. Beta - because this change can potentially break everything, so I need time for testing. I'll appreciate if you'll try it out.

Of course! I'll go and follow your updates for the project on curse. Thank you!

I did not mean to close the issue but issue does seem to be fixed! 👍 :)