Incorrect Unit Characteristics Target trigger behaviour when unselecting a target
calummitchell opened this issue ยท 2 comments
Is there an existing issue for this?
- I have searched the existing open and closed issues.
Description
A simple Unit Characteristics trigger with Unit=target with or without other checks such as level should activate when I have a target and deactivate with I unselect the target by pressing Escape. Instead if I'm close enough to the target (<40yds-ish) the trigger deactivates then activates then deactivates in very quick succession. Among other things this causes the On Show/On Hide to execute unexpectedly. However, when standing further away from the target (>=40yds) the problem doesn't occur.
Related discord help thread https://discord.com/channels/172440238717665280/1192816168306749470
WeakAuras Version
WeakAuras 5.9.0
World of Warcraft Flavor
Retail (Default)
World of Warcraft Region
EU
Tested with only WeakAuras
- Yes
Lua Error
No errors
Reproduction Steps
- Click on a target to select it
- The test aura activates showing your rough range to the target and playing a banana peel sound
- Stand <40yds from the target
- Unselect the target by pressing Escape
- The test aura deactivates but plays the banana peel sound again
- Repeat the above steps but stand >45yds from the target and the problem won't occur
- Change the trigger activation to Custom Function and repeat the above steps to see the weird trigger deactivation sequence.
Last Good Version
No response
Screenshots
No response
Export String
!WA:2!1rvZUnovu4jQlqYIfmrqfthwekIoDeIK2IOtBrZI6scnqAtXX9hef5ETVhBFNX5EV6EVUTzwgHeSbw0hHSMv5raXdGvfpb9rywWAox7qha16ifF)54ZpFFFNtTo1hwNwN(ZTuICtgJdQ(h63R7(TdVGKi6(Lx9SvEv)Vz3WJ1ErImH6RNdFMeLRnIH(WLg56X58idtWx(PonWhfyYv8ghdKxUDUIOB(vGXJWtGLFIHOsaZtEQdWPxRtjuXfFx)4yny(GhmLWJsfQdemUjCN27732t2GY0YmYiBCcIfQHetGmWWgcZ2vt(oVjtousjgimV81nKC8yIHfDmJAsD3g3QiL5PEDpnMjML80ICovUvxUbuXKi40TP0(C9P3M7NUhqzKthyTtFQlHJ)oaGSbzmztrsYyQiO0jNfgZ4mDQJl(Y4m2OyjjGs)RlPMT8VCnJKGBoETSEUgciHAHkCxGKTNGcNDJopeoh4Mb5XXSlNgSZ2d8dg4VTN)TxDGcWR8gCq7E9UjdpklqibfblTfw85p3R0i57EigJg7KsS1lOyAee0flewH(JTX2MfNDLDvPxshRLqwwxQ2XJtgcANBEtgwMDEL2TWIF6Q38pFptB)pDcfH84yFS4u72U3bDoS3v58zfTZuKbFrP(4CyncFKS(m(Q6(EIewKS1TkitLesQqrWYMVF1F4)iPShyLoYhskD4mNytWF7bYhFNILQfEwnd91mlrZjzhHmdgUF5kcNz1ic(6fpSZVdenmWOaEIj9TkEKlxWHRPOoWArGL(uAisGsHXwtTLCXgUdjmENINHFqXgfBwSvXxGVFV))jUXcUXBFI4Iu15vHFUjiV6bjwj5cZx8ORXTHKOxMOSkk3mbHEujhXrSxLI8xgsVZ7nmpZWC8IYiA98fTDCrYlQAb7vGDXyBWgGB6ImyUkcczdLcLzwp3jv9CZn9FHyJv2w0gFCKCX7VPBOGgGObC2evzABraxdA3euwc0YoTF8TLF4D4HvBwPxR2wSXDsxr3ET6fOmHfpYTx7o(HiMhZsCKF09NAsfeXkrv1LvLxTRXra4eL(YYMENR0qwC14f3(((93luddrG1B1MR0CLjgr0mE59R9tPlYOYg3vFud)YUOg(G2SwUkt(4uJrQ3Qvl74YMmrRBNx2A1PXkSBcLuedzUxxnGRJ9ilWfoyhV2T3F8fcf9yfro(4zlwlNrNEIi7Bp6ZwBt1fVs(j3FzthH9RSOatQc0PIm6i1OQY)pQpTIT3PCQDTA1WP2O2LvHgtz8kpH7CKlD)ridsirJcIZecvADT3N3CZMRu)8)8K)(d
That's a blizzard issue, we are receiving 3 events that tell us that you deselected the target, selected the target and deselected the target.
I've created a bug report for blizzard to look at:
Stanzilla/WoWUIBugs#520
Though I have to admit that blizzard fixes only a few issues affecting addons per year, and as such it might linger there forever.