WeakAuras
patreon
WeakAuras and Patch 8.2
🕑 Added 2019-06-20 15:49:24 +0000 UTCWe had this blog post planned for a while but Blizzard only just now (one week before release...) posted their official list of API changes for the next patch.
The two changes that affect WeakAuras the most are the file path handling and nameplates ones:
File Paths:
We've already discussed the details of this change in a recent blog post so just a short tldr:
You should update to the latest WeakAuras release now and login in to WoW once before 8.2 launches to properly migrate your settings.
Nameplates:
The 8.2 release also contains a change in how nameplates are handled. This does only affect auras that attach to nameplates, like the "LineToEnemy" ones that became very popular this expansion.
The intent of the API change is to prevent exactly that, drawing lines to nameplates. Attaching auras to nameplates is still possible, but auras that written without the 8.2 changes in mind, might still break. We actually applaud Blizzard this time for using a more surgical approach for breaking unintended behavior instead of using their usual sledgehammer method.
The new "Anchor Restricted Frame" works like this:
* All nameplates are considered Anchor Restricted Frames.
* GetPoint, GetCenter, etc are no longer possible to use on an anchor restricted frame from insecure code.
* Calling SetPoint with an anchor restricted frame as the relative frame will successfully anchor to the restricted frame, and cause the anchored frame to also become an anchor restricted frame.
* It is not possible to use 2 different anchor restricted frames as relative frames for anchor points on a third frame. So, you can't anchor the topleft of a line to nameplate1, and the bottom right of the same line to nameplate2.
* Nor is it possible to anchor to both a anchor restricted frame and a non-restricted frame
That's it for now and we hope you enjoy all the new content coming in the patch next week!
