Edit: Blizzard has clarified further on Redddit that this is for the Lua API and changes to classes, the base UI and more are still planned.
BlizzardIt's important to note that the message here -- one from a WoW Lead Software Engineer to a community of addon authors -- was talking about changes to the Lua API that they use to write addons, and not anything else such as development on any part of the game or its User Interface or classes, etc. etc.
This is how we've tried to always treat the API. We don't want to modify it in between patches, other than to address extreme bugs/exploits, because doing so would probably break players' addons until they get updated.
We have UI updates in 12.0.1 (coming soon!), and we almost-continuously hotfix the game to address quality-of-life issues, such as damage meter functionality, or class abilities currently missing from the cooldown manager, and bugs, and everything else.
This means that we can and likely will see base UI functionality improve during 12.0.1 and through hotfixes.
This is important as many players are still looking for addon improvements and Blizzard have announced that only exploit and high priority requests are making it to Midnight launch for the addon API. Any other requests are looking to have to wait until Midnight's first major patch 12.0.5.
WoW Devs via WoWUI Discord
Blizzard again! Below you will find a list of changes we are making to addon restriction APIs in the coming weeks.
These are not the entirety of the changes we are planning, just the ones already committed to for the immediately upcoming Beta releases.
IMPORTANT: The RC process for 12.0.1 has begun, and while the Beta build this week is likely not going to be the final RC we are getting close. As a result, only very high priority issues are being worked on in 12.0.1 (mostly exploits, but also a smattering of remaining high-priority addon dev requests). Once we get closer to 12.0.1 launch we will release a list of tasks we plan to work on for 12.0.5 so you can have a better idea of the upcoming roadmap (including many of your requests).
Critical changes due to be deployed to live/pre-patch over the next few days
Fixed an issue where the C_UnitAuras.AddPrivateAuraAppliedSound API caused Lua errors at the time of the sound playing.
Fixed an issue causing secret-related Lua errors in Edit Mode.
Fixed an issue causing click casting to get eaten by private auras on raid frames.
Fixed various issues with secrets in tooltips causing Lua errors.
Fixed an issue where responding to a BNet whisper could cause a Lua error in auto complete code.
Fixed an issue causing secret-related Lua errors when addons created dropdowns.
Fixed an issue where arena frames could cause Lua errors when exiting edit mode.
Changes in Beta 8 (ETA 1/28)
Boss Warning APIs
Added a new C_EncounterEvents namespace that allows querying static information about encounter events.
Added a new C_EncounterEvents.SetEventColor API that allows addons to associate a specific color with an encounter event (our UI will use it to colorize text and timer bars).
Added a new C_EncounterEvents.SetEventSound API that allows addons to specify a sound to play when encounter events show text warnings or transition states on the timeline.
Sounds will be played automatically by the client.
Aura Filters
Added 4 new filter types for Aura APIs:
CROWD_CONTROL
BIG_DEFENSIVE
RAID_PLAYER_DISPELLABLE (returns auras the player can dispel)
RAID_IN_COMBAT (returns auras that are flagged to show on raid frames in combat, when used with Player and Helpful filters this should return mostly just HoTs).
Misc Changes
|T string markup inside secret strings now permits the use of local file overrides if the texture is part of the base game.
Referencing custom addon textures using secret strings is still not allowed.
Fixed an issue where tainted calls to CVarCallbackRegistry:GetCVarValue could store tainted values in the cached value table, causing restriction issues.
Fixed an issue in the Restricted Environment ipairs function that caused it to return early when any falsey value was stored in the table.
Added the optional start and end range parameters to unpack in the Restricted Environment.
