🔥 The State of WoW Addons in 12.0: The Addonpocalypse Report¶

Last Updated: March 13, 2026 — 11 days post-launch, 11 days until Mythic raids Patch: 12.0.1 (Interface 120001) Season 1: Starts March 17 | Mythic Raids: March 24 Methodology: 50+ web searches, 60+ page fetches, 9 research reports, every claim tagged ✅/⚠️/❓

📊 The Scorecard: 11 Days In¶

🗓️ What Happened: The Timeline¶

Before we look forward, let's establish exactly what happened and when. Every date below is verified.

🔮 What Happens Next: The Prediction Timeline¶

Based on verified trends, confirmed PTR data, Blizzard's stated policy, and the pattern of concessions during beta.

Patch 12.0.5 (PTR Active, No API Changes Yet)¶

Patch 12.1 (Unannounced)¶

March 24: Mythic Raid Unlock¶

⚡ The API Exploit Tier List (VERIFIED)¶

What ACTUALLY still works in 12.0.1, ranked by how long we expect it to last. Every entry verified against live patch data.

🟢 SAFE — Blizzard Clearly Intended These¶

These are explicitly supported, documented APIs. They're not going anywhere.

Settings Panel API ✅¶

Longevity: Permanent. This is Blizzard's official addon settings system.

-- This is THE supported way to create addon settings in 12.0+
local category = Settings.RegisterVerticalLayoutCategory("My Addon")

local setting = Settings.RegisterAddOnSetting(category,
    "MyAddon_Enabled", "enabled", MyAddon_DB,
    type(true), "Enable Feature", true
)
Settings.CreateCheckbox(category, setting, "Toggle the main feature.")

Settings.RegisterAddOnCategory(category)

Used by: Every addon with a settings panel Source: ✅ Warcraft Wiki - Settings API

Addon Compartment ✅¶

Longevity: Permanent. Blizzard wants addons to use this instead of minimap buttons.

-- In your .toc file:
-- ## AddonCompartmentFunc: MyAddon_OnClick
-- ## IconTexture: Interface\Icons\INV_Misc_QuestionMark

function MyAddon_OnClick(addonName, buttonName)
    if buttonName == "LeftButton" then
        Settings.OpenToCategory(MyAddon.categoryID)
    end
end

Used by: Every modern addon with a minimap presence Source: ✅ Warcraft Wiki - Addon Compartment

C_DamageMeter API ✅¶

Longevity: Permanent. This is Blizzard's replacement for CLEU-based damage tracking.

-- Get available combat sessions
local sessions = C_DamageMeter.GetAvailableCombatSessions()

-- Get session data
local source = C_DamageMeter.GetCombatSessionSourceFromID(
    sessionID, Enum.DamageMeterType.DamageDone
)

-- Check if meter is available
if C_DamageMeter.IsDamageMeterAvailable() then
    -- Display damage data
end

Used by: Details! (as its data backend), Blizzard's native meter Source: ✅ Warcraft Wiki, Wowhead

C_EncounterTimeline API ✅¶

Longevity: Permanent. Blizzard's boss encounter data system.

-- Get encounter event list
local events = C_EncounterTimeline.GetEventList()
local info = C_EncounterTimeline.GetEventInfo(eventID)

-- Custom events (addon-created overlays)
C_EncounterTimeline.AddScriptEvent(eventData)
C_EncounterTimeline.CancelScriptEvent(eventID)

-- Check state
local hasActive = C_EncounterTimeline.HasActiveEvents()

Used by: DBM, BigWigs, Better Timeline Source: ✅ Warcraft Wiki

Duration Objects & Secret-Safe Display ✅¶

Longevity: Permanent. This IS the Secret Values solution.

-- Create a Duration Object for cooldown display
local duration = C_DurationUtil.CreateDuration()
cooldownFrame:SetCooldownFromDurationObject(duration)

-- Boolean-driven visuals (no branching on secrets)
region:SetAlphaFromBoolean(secretBool)
region:SetVertexColorFromBoolean(secretColor)

-- Color Curves for threshold visualization
local curve = C_CurveUtil.CreateCurve()
-- Secret values can be fed into curves for visual display

Used by: Cell, Arc UI, OmniCD, cooldown tracking addons Source: ✅ Warcraft Wiki - Secret Values

Housing APIs ✅¶

Longevity: Permanent. Brand new, unrestricted frontier.

-- Housing APIs are NOT affected by Secret Values
-- Full read/write access to housing data
C_HouseExterior.GetCurrentHouseExteriorType()
C_HouseExterior.GetHouseExteriorSizeOptions()
C_HousingCatalog.GetCatalogItems()
C_HousingDecor.PreviewDecorItem(itemID)

-- Photo sharing (12.0.1)
C_HousingPhotoSharing.SharePhoto(photoData)

Used by: HomeBound (3M+ downloads), HomeDecor, Plumber Source: ✅ Warcraft Wiki

ScrollBox / DataProvider ✅¶

Longevity: Permanent. The modern scroll system since 10.0.

local scrollBox = CreateFrame("Frame", nil, parent, "WowScrollBoxList")
local scrollBar = CreateFrame("EventFrame", nil, parent, "MinimalScrollBar")
local view = CreateScrollBoxListLinearView()
view:SetElementExtent(24)
view:SetElementInitializer("ButtonTemplate", function(btn, data)
    btn:SetText(data.name)
end)
ScrollUtil.InitScrollBoxListWithScrollBar(scrollBox, scrollBar, view)

local dp = CreateDataProvider()
dp:Insert({ name = "Hello" })
scrollBox:SetDataProvider(dp)

Used by: Every addon with scrollable lists Source: ✅ Warcraft Wiki - Making Scrollable Frames

RegisterEventCallback (Frame-Free Events) ✅¶

Longevity: Permanent. New in 12.0, explicitly designed for addons.

-- No frame needed! Register events directly.
RegisterEventCallback("PLAYER_LOGIN", function(event)
    print("Logged in!")
end)

RegisterUnitEventCallback("UNIT_HEALTH", function(event, unit)
    -- Handle unit health change
end, "player")

-- Check if an event supports callbacks
if C_EventUtils.IsCallbackEvent("PLAYER_LOGIN") then
    -- Can use RegisterEventCallback
end

Used by: Modern addons adopting the new pattern Source: ✅ Warcraft Wiki - RegisterEventCallback

🟡 BORROWED TIME — Working Now, Could Close Any Patch¶

These techniques work but exploit gaps or temporary concessions. Use them, but have a fallback plan.

hooksecurefunc (Combat-Facing) ⚠️¶

Risk: Medium. The hook mechanism itself is permanent, but what you can do with the data is shrinking.

hooksecurefunc was NOT removed and is NOT on the removed API list. It remains the canonical way to post-hook secure functions. However, hook arguments increasingly arrive as Secret Values in restricted contexts.

-- STILL WORKS: Hooking for visual customization
hooksecurefunc("CompactUnitFrame_UpdateAll", function(frame)
    if frame:IsForbidden() then return end
    frame.healthBar:SetStatusBarTexture(MY_TEXTURE)
end)

-- STILL WORKS but arguments may be secret:
hooksecurefunc(GameTooltip, "SetAction", function(self, slot)
    local kind, id = GetActionInfo(slot)
    -- kind and id might be secret values in combat!
    if issecretvalue(kind) then return end
    -- Safe to use outside restricted contexts
end)

The pattern going forward: Hook fires → check issecretvalue() on every argument → graceful degradation.

Used by: Every major addon (ElvUI, Details!, DBM, Cell, Plater, idTip) Source: ✅ Warcraft Wiki - hooksecurefunc, ✅ Cell PR #457

Healer Spell Un-Secreting ⚠️¶

Risk: HIGH. Blizzard explicitly said this is temporary.

On February 24, 2026, Blizzard un-secreted many healer spells. But they warned:

"We will likely re-protect these spells once our own filtering solution...is in place."

-- These healer auras are CURRENTLY non-secret
-- But Blizzard has said they'll re-protect them
-- Build your addon to gracefully degrade!

local auraData = C_UnitAuras.GetAuraDataByIndex(unit, index)
if issecretvalue(auraData.name) then
    -- Fallback: show icon only, no timer text
    ShowIconOnly(auraData.spellId)
else
    -- Full display while we still have access
    ShowFullAuraData(auraData)
end

Used by: Cell, VuhDo, Healbot, Danders Frames, Grid2 Source: ✅ Wowhead

Metatable Access on Non-Forbidden Frames ⚠️¶

Risk: Low-medium. Works and no signs of restriction, but Blizzard fixed metatable bugs in restricted environments during beta — showing they're paying attention.

-- Get the shared frame metatable
local mt = GetFrameMetatable()

-- Add custom method to ALL frames
mt.__index.MyCustomMethod = function(self)
    return self:GetName() or "unnamed"
end

-- Works on non-forbidden frames
local frame = CreateFrame("Frame")
print(frame:MyCustomMethod())

Caveat: Metatable operations that touch Secret Values will error. __index/__newindex on secrets is blocked.

Used by: WeakAuras (RIP), ElvUI, MidnightSimpleUnitFrames Source: ✅ Warcraft Wiki - Widget API, ✅ Warcraft Wiki - Planned API Changes

Addon Communication (Between Pulls) ⚠️¶

Risk: Medium. Works outside encounters, locked during them. The lockdown scope could expand.

-- Check if we're in lockdown
if C_ChatInfo.InChatMessagingLockdown() then
    -- Queue the message for later
    tinsert(pendingMessages, { prefix, msg, channel, target })
    return
end

-- Send normally
C_ChatInfo.SendAddonMessage(prefix, msg, "RAID")

-- Flush queue on encounter end
local frame = CreateFrame("Frame")
frame:RegisterEvent("ENCOUNTER_END")
frame:SetScript("OnEvent", function()
    for _, pending in ipairs(pendingMessages) do
        C_ChatInfo.SendAddonMessage(unpack(pending))
    end
    wipe(pendingMessages)
end)

Used by: Cell (implements IsCommRestricted()), MRT, DBM, BigWigs Source: ✅ Cell PR #457, ✅ Warcraft Wiki

CLEU Outside Restricted Contexts ⚠️¶

Risk: Medium-high. The event technically fires but payload is secrets during instanced content. Open world usage works, but Blizzard could tighten further.

-- CLEU fires but data is wrapped in Secret Values during:
-- Mythic keystones, PvP, encounters, combat

local frame = CreateFrame("Frame")
frame:RegisterEvent("COMBAT_LOG_EVENT_UNFILTERED")
frame:SetScript("OnEvent", function()
    -- Check if we're restricted first
    if C_CombatLog.IsCombatLogRestricted() then
        return -- Data is secrets, don't even try
    end

    -- Open world: data is normal, full parsing works
    local timestamp, event, _, sourceGUID = CombatLogGetCurrentEventInfo()
    -- Process normally
end)

Used by: Legacy combat tracking (open world only) Source: ✅ Warcraft Wiki - COMBAT_LOG_EVENT, ✅ Warcraft Wiki - Planned API Changes

Frame Strata on Blizzard Frames (Out of Combat) ⚠️¶

Risk: Medium. Since Patch 11.1.7, calling SetFrameStrata()/SetFrameLevel() on protected frames during combat is blocked. Out-of-combat manipulation still works but the protection scope has been expanding.

-- Works on own frames ALWAYS (including combat):
myFrame:SetFrameStrata("HIGH")
myFrame:SetFrameLevel(100)

-- Works on Blizzard frames OUTSIDE combat:
SomeBlizzardFrame:SetFrameStrata("MEDIUM")

-- BLOCKED on protected frames IN combat since 11.1.7:
-- Use SecureStateDriver instead
RegisterStateDriver(mySecureFrame, "strata", "[combat] HIGH; LOW")

Used by: StrataFix, Plater, MidnightSimpleUnitFrames Source: ✅ Warcraft Wiki - SetFrameStrata

🔴 NEXT ON THE BLOCK — Blizzard Probably Targeting These¶

These work today but show signs of being in Blizzard's crosshairs for future restrictions.

Specific Spell Whitelisting Exploits 🔴¶

Risk: High. The whitelist is explicitly temporary for some entries.

Currently, 8 cooldown-only spells and 8 full aura data spells are whitelisted as non-secret. Blizzard has said the healer spells are temporary. Addons building around specific whitelist entries are building on sand.

-- These specific spells are currently non-secret:
-- Cooldowns: Second Wind, Surge Forward, Skyward Ascent, Aerial Halt,
--            Whirling Surge, Lightning Rush, Switch Flight Style,
--            all combat resurrection spells
-- Auras: Thrill of the Skies, Ohn'ahra's Gusts, Static Charge,
--        Skyriding Racing, Maelstrom Weapon, Void Metamorphosis,
--        Collapsing Star

-- Check if a specific spell's cooldown should be secret:
if C_Secrets.ShouldSpellCooldownBeSecret(spellID) then
    -- Use Duration Object path
else
    -- Direct access works (FOR NOW)
    local info = C_Spell.GetSpellCooldown(spellID)
end

The safe pattern: Always implement the Duration Object fallback. Don't assume any specific spell will stay whitelisted.

Source: ✅ Wowhead - Whitelisted Spells

Tooltip Scanning for Unit Data 🔴¶

Risk: High in instanced content. Item tooltips work fine; unit data is increasingly restricted.

-- Item tooltips: STILL WORK (even in instances)
local info = C_TooltipInfo.GetItemByID(itemID)

-- Unit tooltips: BROKEN in instances
-- Creature GUIDs and names become Secret Values
-- tostring() on secret tooltip data throws:
-- "attempt to perform string conversion on a secret value"

Multiple addons have filed issues. AllTheThings opened issue #2261. A dedicated compatibility addon — "PlsFixMe Midnight Tooltips" — exists solely to suppress these errors.

Used by: idTip, TipTac, Pawn, AtlasLoot, AllTheThings Source: ✅ GitHub - AllTheThings #2261, ✅ CurseForge - PlsFixMe

Macro Workarounds for Addon Restrictions 🔴¶

Risk: Very high. Blizzard is actively hotfixing these.

March 11, 2026 hotfixes already restricted:

• Macros can no longer set target markers on more than 3 units within a short time
• Macros restricted from sending chat messages during active encounters

-- BLOCKED as of March 11:
-- Rapid target marker macro spam — limited to 3 units
-- Macro whisper relay to external player — blocked
-- Non-group channel messages during encounters — blocked

If you're building around macro edge cases, expect them to be closed within one hotfix cycle.

Source: ✅ Blizzard - Hotfixes March 11, ✅ Wowhead - Macro Changes

"Addons Still Win" Competitive Advantages 🔴¶

Wowhead's January 2026 investigation found that despite restrictions, addons continue providing competitive advantages through:

• Reminder addons (Northern Sky, Viserio Cooldowns) alerting on defensives/offensives unavailable in default UI
• Boss mods creating independent timer systems with dynamic phase-tracking
• Nameplate coloring identifying priority targets
• Hard-coded timers functioning as pseudo-WeakAuras

Blizzard is clearly watching this space and has already started closing holes (macro restrictions).

Source: ✅ Wowhead - Addons Continue to Provide Advantage

☠️ ALREADY DEAD — Confirmed Blocked¶

No workarounds. No "well actually." Dead.

CLEU Combat Parsing ☠️¶

-- DEAD. Data is KStrings/Secrets during any restricted context.
-- The event fires, but CombatLogGetCurrentEventInfo() returns
-- Secret Values that cannot be inspected, compared, or computed on.

-- "attempt to compare two secret values" — Lua error
-- "attempt to perform arithmetic on a secret value" — Lua error
-- "attempt to perform string conversion on a secret value" — Lua error

Cell's PR #457 documents the complete migration: CLEU disabled entirely, switched to UNIT_AURA + UNIT_HEALTH + UNIT_SPELLCAST_SUCCEEDED.

Source: ✅ Warcraft Wiki — "Combat Log Events are no longer available to addons"

Secret Value Bypasses ☠️¶

Every known bypass has been patched:

Source: ✅ Warcraft Wiki - Secret Values

Rotation Helpers ☠️¶

Hekili, MaxDps, and all rotation helpers are fundamentally impossible under Secret Values. You cannot compute "which button to press" when you can't read cooldown values, check aura states, or evaluate resource counts during combat.

Source: ✅ Multiple — WeakAuras team: "The core value proposition of WeakAuras isn't compatible with the direction Blizzard is taking the game."

Old Global Action Bar Functions ☠️¶

138 APIs removed in 12.0.0. The most impactful:

-- ALL OF THESE ARE GONE:
ActionHasRange()          -- use C_ActionBar.IsActionInRange()
GetActionAutocast()       -- use C_ActionBar namespace
IsItemAction()            -- use C_ActionBar namespace
HasBonusActionBar()       -- use C_ActionBar.HasBonusActionBar()
HasVehicleActionBar()     -- use C_ActionBar.HasVehicleActionBar()
CombatLogAddFilter()      -- use C_CombatLog namespace
CombatLogResetFilter()    -- use C_CombatLog namespace
IsEncounterInProgress()   -- removed entirely
BNSendGameData()          -- removed

Source: ✅ Warcraft Wiki - 12.0.0 API Changes

UIDropDownMenu / EasyMenu ☠️¶

Deprecated since 11.0, removed in 12.0. The new menu system:

-- OLD (DEAD):
-- UIDropDownMenu_Initialize(dropdown, initFunc)
-- EasyMenu(menuList, dropdown, ...)

-- NEW (11.0+):
MenuUtil.CreateContextMenu(owner, function(owner, rootDescription)
    rootDescription:CreateButton("Option 1", function() print("1") end)
    rootDescription:CreateButton("Option 2", function() print("2") end)
end)

-- Hook Blizzard menus:
Menu.ModifyMenu("MENU_TAG", function(owner, rootDescription, contextData)
    rootDescription:CreateButton("My Custom Option", function() end)
end)

Source: ✅ Warcraft Wiki - 11.0.0 API Changes

🏆 Top 10 Addon Status Report (VERIFIED)¶

Not speculation. Not "might die." Real status, real evidence, real download numbers where available.

1. WeakAuras — ☠️ DEAD (Combat)¶

Stanzilla (WeakAuras Lead): "The core value proposition of WeakAuras isn't compatible with the direction Blizzard is taking the game."

Conditions for return (none currently being met):

1. Ability to compute new secret values from existing ones
2. Reverting restrictions for personal combat state only
3. Complete system reversal

Sources: ✅ Wowhead, ✅ Icy Veins, ✅ PCGamesN, ✅ WeakAuras Patreon

2. ElvUI — 🟡 ALIVE (Reduced, Dramatic Comeback)¶

What's preserved: Action bars, chat, bags, UI skins, anchoring, basic buff/debuff filtering, Cooldown Manager skinning.

What's cut: Style Filters (combat-conditional styling), Portraits (removed across ALL game versions), Cutaway Bars (Midnight only), simplified tag/text formatting.

The drama: When ElvUI initially quit, a content creator named Quazii paywalled a fork as "QuaziiUI" behind Patreon. ElvUI dev Luckyone accused him of literal code theft — "not just ideas or similar execution, but literal functions, comments, and references that still point at ElvUI functions." Quazii subsequently deleted his Patreon, Discord, YouTube, and posted a goodbye message.

Sources: ✅ Icy Veins, ✅ Warcraft Tavern, ✅ Kaylriene - Vibecoded Wars

3. Details! Damage Meter — 🟢 ALIVE (Reskin Architecture)¶

What works: Damage Done, DPS, Damage Taken, Healing Done, HPS, Interrupts, Dispels, Deaths, per-ability breakdowns, combat session segments.

What's lost: Overhealing tracking, CC break detection, buff uptime analysis, resource generation tracking, pet damage segmentation, spell merging, advanced death breakdowns, chat reporting.

Forum user: "They are skins of existing tools Blizzard now provides. They have no access to anything that WoW isn't already providing baseline."

For deep analysis: Use Warcraft Logs — the /combatlog disk file is completely unaffected.

Sources: ✅ Wowhead, ✅ Blizzard Forums

4. DBM (Deadly Boss Mods) — 🟢 ALIVE (Reformatted)¶

MysticalOS (DBM creator) met directly with Ion Hazzikostas and lead software engineer Andy Churchill. The result: boss mods continue but as reformatters of Blizzard's native encounter system.

New capabilities: Custom timers via reminder system, custom audio on three alert severity pools, Private Aura integration for encounter debuffs, UI reskinning of Boss Timeline.

Lost capabilities: Cannot rename ability casts ("soak"/"frontal"), cannot independently decide which alerts to show, external audio countdowns prohibited, real-time encounter state analysis gone.

Sources: ✅ Wowhead - DBM & BigWigs Meet Ion, ✅ Wowhead - Boss Mods in Midnight

5. BigWigs — 🟢 ALIVE (Reformatted)¶

Similar architectural changes as DBM. Custom layouts and aesthetic customization preserved. Functions as enhancement layer over native boss warnings.

Source: ✅ CurseForge - BigWigs

6. Plater Nameplates — 🟡 ALIVE (Heavily Reduced)¶

Community note: "The addon apocalypse didn't kill Plater; it just demoted it."

Rising replacement: Platynator — built from scratch for Midnight constraints. "Design within the box" philosophy.

Sources: ✅ Wowhead - Nameplates in Midnight, ✅ CurseForge - Platynator

7. Cell Raid Frames — 🟢 ALIVE (Best-Documented Adaptation)¶

Cell PR #457 is required reading for any addon developer adapting to Midnight. Key innovations:

• Granular per-aura secret detection
• CLEU replacement strategies varying by module
• Communication restriction handling with message queuing
• Heal prediction via CreateUnitHealPredictionCalculator()
• Initial Midnight raid debuffs for 6 raids, 6 dungeons, 41 bosses

Sources: ✅ GitHub - Cell PR #457, ✅ Icy Veins

8. Hekili — ☠️ DEAD¶

Rotation helpers are precisely what Secret Values were designed to kill. Cannot read cooldown states, cannot check aura conditions, cannot evaluate resource counts during combat. No path forward.

9. GTFO — ☠️ DEAD¶

GTFO relied on CLEU to detect when you stood in fire and played an alert sound. With CLEU data wrapped in secrets, it can't know what damage event is happening. Blizzard's native Combat Audio Alerts are the replacement, but they're pre-configured — no custom alert mapping.

10. HomeBound (Housing) — 🟢 THRIVING (New Category)¶

Housing addons represent the only growing sector of the addon ecosystem. While combat addons contract, housing addons are exploding. HomeBound, HomeDecor, and Plumber collectively have millions of downloads and zero API restrictions to worry about.

This is the future Blizzard wants: addons that enhance player expression, not combat optimization.

Sources: ✅ CurseForge - HomeBound, ✅ CurseForge - HomeDecor

📊 The Threat Matrix¶

Every row verified. Status as of March 13, 2026.

🔮 The March 24 Question¶

What We Know¶

Season 1 begins March 17. Normal/Heroic raids open. M+ keystones start. This gives guilds one week of non-Mythic experience before the real pressure begins.

Mythic raids unlock March 24. World First guilds (Liquid, Echo, Method) will be pushing progression 16+ hours per day for 1-2 weeks.

What's Different This Time¶

Guild Strategy Development Pipeline (Pre-12.0):

1. Pull boss
2. CLEU fires → WeakAuras parse every event
3. DBM/BigWigs independently detect mechanics
4. WeakAura custom alerts: "SOAK NOW", "SPREAD", "FRONTAL"
5. Damage meters show exact breakdown in real-time
6. Nameplate addons color priority targets
7. Addon comms sync raid cooldowns between pulls
8. Iterate on strategy with full data transparency

Time to develop strategy: ~2-4 pulls for basic understanding

Guild Strategy Development Pipeline (12.0+):

1. Pull boss
2. CLEU fires → Secret Values, useless for parsing
3. DBM/BigWigs REFORMAT Blizzard's native boss timeline
4. Native alerts: generic severity levels (minor/medium/critical)
5. Damage meter shows C_DamageMeter data (no overhealing, no CC breaks)
6. Nameplate addons: visual only, no NPC identification in instances
7. Addon comms LOCKED during encounter — flush on ENCOUNTER_END
8. Post-fight analysis via Warcraft Logs (disk file unaffected)

Time to develop strategy: ??? (genuinely unknown)

The Five Scenarios¶

The Data We'll Know By April¶

🎭 The Vibecoded Addon Wars of 2026¶

This actually happened. Every word is sourced.

When ElvUI initially cancelled development in October 2025, a power vacuum formed in the WoW UI space. What followed was chaos:

Act 1: QuaziiUI¶

Quazii, a content creator, promoted QuaziiUI as the ElvUI replacement. Key facts:

• Marketed as "free until the end of eternity" during The War Within
• Paywalled behind Patreon for Midnight ($$$)
• ElvUI dev Luckyone publicly accused Quazii of literal code theft: "QuaziiUI contains ElvUI code — not just ideas or similar execution, but literal functions, comments, and references that still point at ElvUI functions."
• Luckyone reported QuaziiUI to Patreon for investigation
• Quazii subsequently deleted his Patreon, Discord, and YouTube and posted a goodbye message

Act 2: NephUI vs. DandersFrames¶

• NephUI launched during beta with Edit Mode integration
• Danders (DandersFrames developer) accused Neph of stealing frame implementations
• NephUI was openly "vibe coded" — primarily AI-generated Lua
• Danders implemented a forced dialogue making users choose between the two addons, with messaging stating "NephUI is stolen code"
• NephUI shut down January 23, 2026
• Community fork QUI emerged on GitHub

The "Vibecoding" Question¶

The blog post by Kaylriene that documented this drama coined the term: these developers used AI tools to generate code without genuine addon development expertise. It worked — until it was tested against GPL compliance, community scrutiny, and the actual complexity of WoW's API.

Over 100,000 players were affected by the QuaziiUI/NephUI shutdowns (per Buffed.de estimate).

Sources: ✅ Kaylriene Blog, ✅ The Escapist

♿ The Accessibility Gap¶

Players with disabilities have been among the most vocal and least addressed by Blizzard's changes.

From the official forums:

"I have disabilities, and literally don't know whether Midnight will be playable beyond LFR for me." — Hallany

"I live with a very severe anxiety disorder that results from CPTSD from military service, and it helps me stay calm enough to perform." — Vespasion (on rotation helpers as anxiety stabilizers)

"I am profoundly deaf gamer so text to speech is 100% useless." — SilentKiller (highlighting that Blizzard's Combat Audio Alerts/TTS solution doesn't help deaf players)

Blizzard's Response¶

Blizzard committed to:

• Combat Audio Alerts with Text-to-Speech
• Improved visual/audio telegraphs
• Adjusted encounter pacing with additional reaction time
• Assisted Highlight and One-Button Rotation tools
• Refined Cooldown Manager

The Gap¶

TTS doesn't help deaf players. Pre-configured alert pools don't replace the custom sensory mapping that WeakAuras provided. Assisted Highlight is a start but doesn't match the specificity of custom auras. The accessibility community remains deeply concerned.

Source: ✅ Blizzard Forums - Accessibility Concerns, ✅ Blizzard Forums - Disabilities Thread

📱 The New Addon Ecosystem¶

Rising Stars (Verified Downloads)¶

The "Enhance, Don't Replace" Philosophy¶

The dominant design pattern of 2026. Instead of building parallel UI systems, the best new addons enhance Blizzard's native features:

The WeakAura-to-Standalone Pipeline¶

A new development pattern: popular WeakAuras rewritten as standalone addons.

Healer Addons: The Scramble¶

Source: ✅ Blizzard Forums - Healing Addon Status

🧪 Developer Survival Guide¶

The Secret Values Quick Reference¶

-- DETECT secrets
issecretvalue(value)        -- Is this specific value secret?
issecrettable(table)        -- Does this table contain any secrets?
canaccesssecrets()          -- Can current (untainted) code read secrets?
hasanysecretvalues(table)   -- Quick check for secret contamination

-- HANDLE secrets
scrubsecretvalues(table)    -- Replace all secrets with nil
secretwrap(func)            -- Wrap function for secret-safe execution

-- QUERY restriction state
C_Secrets.HasSecretRestrictions()          -- Are restrictions active?
C_Secrets.ShouldSpellCooldownBeSecret()    -- Cooldown restriction check
C_Secrets.ShouldAurasBeSecret()            -- Aura restriction check
C_RestrictedActions.IsAddOnRestrictionActive()  -- Addon restriction state
C_CombatLog.IsCombatLogRestricted()        -- Combat log restriction

-- EVENTS
-- ADDON_RESTRICTION_STATE_CHANGED fires when restriction state changes
-- Enum.AddOnRestrictionType: Combat, Encounter, ChallengeMode, PvPMatch, Map
-- Enum.AddOnRestrictionState: Inactive, Activating, Active

Testing CVars (Development Only)¶

/console secretAurasForced 1
/console secretCooldownsForced 1
/console secretUnitIdentityForced 1
/console secretSpellcastsForced 1
/console secretUnitPowerForced 1
/console secretUnitPowerMaxForced 1
/console secretUnitComparisonForced 1
/console addonChatRestrictionsForced 1

Set to 0 to disable. These CVars are non-persistent (reset on relog).

The Graceful Degradation Pattern¶

The #1 pattern every addon developer must implement:

local function UpdateDisplay(unit, spellID)
    -- STEP 1: Check if restrictions are active
    if C_Secrets.HasSecretRestrictions() then
        -- STEP 2: Use Duration Object path for cooldowns
        local duration = C_Spell.GetSpellCooldownDuration(spellID)
        if duration then
            cooldownFrame:SetCooldownFromDurationObject(duration)
        end

        -- STEP 3: Use boolean-driven visuals for state
        local isActive = UnitBuff(unit, spellID)
        region:SetAlphaFromBoolean(isActive)
        return
    end

    -- STEP 4: Full access outside restricted contexts
    local info = C_Spell.GetSpellCooldown(spellID)
    if info.duration > 0 then
        cooldownFrame:SetCooldown(info.startTime, info.duration)
    end

    -- Full aura data available
    local aura = C_UnitAuras.GetAuraDataBySpellName(unit, spellName)
    if aura then
        ShowFullAuraDisplay(aura)
    end
end

📡 Sources¶

Every claim in this report links to a verified source. Here's the complete list, organized by category.

Official Blizzard¶

API Documentation (Warcraft Wiki)¶

Gaming Press¶

Community News¶

Developer Sources¶

Addon Distribution¶

🏁 The Bottom Line¶

Eleven days in. The dust hasn't settled. Here's where we stand:

What Blizzard wanted: Addons that change how things look, not how players play. A level competitive playing field. Native tools replacing addon dependencies.

What actually happened: Combat addons contracted sharply. Housing addons exploded. The "enhance, don't replace" philosophy took root. But competitive players lost tools they relied on, accessibility gaps remain unresolved, and the first real stress test — Mythic raids — hasn't happened yet.

What comes next: March 24, 2026. Mythic raids. The Race to World First. The first time in over a decade that the best guilds in the world face the hardest content without WeakAuras, without CLEU parsing, and without independent mechanic detection.

That's when we find out if the Addon Disarmament was a masterstroke or a mistake.

Report compiled from 9 research reports, 50+ web searches, 60+ page fetches, and verification against live 12.0.1 data. Every claim tagged with ✅ (CONFIRMED), ⚠️ (LIKELY), or ❓ (UNVERIFIED).

Cell PR #457 remains the single best technical resource for addon developers adapting to Midnight.