Midnight Season 2

Your aura is not broken. It is being refused.

Patch 12.0 introduced a secrets system: the game stopped handing addons certain values. An addon that asks for one does not get an error. It gets nothing, and carries on. So a WeakAura that watched a debuff quietly stops firing, and every instinct tells you that you configured it wrong.

That is why this page exists, and why it is not the page it was asked to be. The request was a Wago that sorts by date, to find new imports that work on 12.1.0. Date does not predict this: an import uploaded yesterday on a removed trigger is exactly as dead as one from two years ago. The trigger decides it, so that is what you can filter below.

Patch 12.1.0Wago fork category ->New here? ->How we source this ->

First, a correction you have probably been told the wrong way round

The version you will find in most search results, including AI summaries, is that WeakAuras 2 is no longer maintained for Midnight. That is false. It was checked against the project's own releases page: WeakAuras2 shipped 5.22.0 on 5 September 2026, one day before the fork's latest release, with no unmaintained notice anywhere.

The real situation is more specific and more useful. WeakAuras2 is actively developed and is architecturally incompatible with the secrets design. Those are different problems: a player told the first one waits for a fix that is not coming, and a player told the second one goes and changes their triggers today.

What the secrets system does

It fails silently
Quoting the M33kAuras author directly: "WA devs didn't lie when they said that WA is incompatible with secrets design. When certain stuff is secret addon just silently refuses to work." No error, no warning, no red text. The aura is simply never right again, and the natural conclusion is that you set it up wrong.
It covers the things auras are built on
The pull request names auras, cooldowns, casts and the evaluation of conditions as the areas that stop working when the underlying values are secret. That is most of what a combat aura watches, which is why the breakage feels total rather than partial.
It is not a bug and not neglect
Blizzard restricted the data deliberately. WeakAuras2 shipped a release the day before M33kAuras did. Nobody is asleep at the wheel, and no patch is coming to restore the old behaviour: the information the addon needs is no longer given to it.

Will this import work? Filter by what it does

Type what you want the aura to do, or filter to the verdict you care about. 5 behaviours have no working form at all in the fork, and knowing which they are before you spend an evening on one is the whole point.

  • React to something that happened in the combat log

    verified. Transcribed from a primary source: a Blizzard post, patch note, or the game itself.

    Will not work - Combat Log Event (CLEU) trigger

    The single biggest category. Most boss-mechanic auras, most "did my proc land" auras and nearly every shared raid pack are built on this. There is no replacement in the fork.

  • Watch a health bar or a health percentage

    verified. Transcribed from a primary source: a Blizzard post, patch note, or the game itself.

    Will not work - Health trigger

    Execute-range indicators and boss health-phase auras both land here.

  • Time an auto-attack swing

    verified. Transcribed from a primary source: a Blizzard post, patch note, or the game itself.

    Will not work - Swing Timer trigger

    Melee weaving and swing-timer displays have no working form.

  • Know whether a target is in range

    verified. Transcribed from a primary source: a Blizzard post, patch note, or the game itself.

    Will not work - Range Check trigger

    Range indicators and spread or stack helpers built on distance do not function.

  • Highlight the next suggested cast

    verified. Transcribed from a primary source: a Blizzard post, patch note, or the game itself.

    Will not work - Assisted Combat Next Cast trigger

    The rotation-helper trigger added for the assisted combat system. Removed alongside the other four.

  • Count down a buff or debuff duration

    verified. Transcribed from a primary source: a Blizzard post, patch note, or the game itself.

    Works, with limits - Aura trigger with durationObject progress

    The fork's headline addition. You get a bar or a text that counts down, in text, icon and bar regions. What you do not get is arithmetic on the number, because the addon still cannot read it.

  • Show a cooldown as it ticks

    verified. Transcribed from a primary source: a Blizzard post, patch note, or the game itself.

    Works, with limits - Cooldown display with partial support

    The pull request states basic information shows when the full value is unavailable. Expect the icon and the sweep, not conditional logic driven by the exact seconds remaining.

  • Render a bar from a value the addon cannot read

    verified. Transcribed from a primary source: a Blizzard post, patch note, or the game itself.

    Works, with limits - Static progress type accepting secret values

    Works, with limits on adjusting the bar's minimum and maximum while the value is secret.

  • Know when the game is hiding data from the aura

    verified. Transcribed from a primary source: a Blizzard post, patch note, or the game itself.

    Not removed - Secret Restrictions Active load option and condition

    Added by the fork rather than kept from upstream. Build this into a pack and a silent failure becomes a visible one, which is the difference between debugging for an hour and reading a label.

  • Anything else - talents, spec, zone, group size, unit frames

    derived. Calculated from verified rules. The arithmetic is ours; the inputs are not.

    Not removed - Triggers absent from the removal list

    The pull request is a removal list, so a trigger not on it was not removed. That is the honest limit of the claim. A kept trigger that reads a restricted value can still go quiet, so test it rather than assume it: import, then use the checklist below.

Showing 10 of 10.

verified. Transcribed from a primary source: a Blizzard post, patch note, or the game itself.
Transcribed from a primary source: a Blizzard post, patch note, or the game itself.
derived. Calculated from verified rules. The arithmetic is ours; the inputs are not.
Calculated from verified rules. The arithmetic is ours; the inputs are not.

What M33kAuras actually changes

Straight from the fork's own merged pull request, not from commentary about it. It is a fork of WeakAuras2 that trades away the triggers that cannot work for partial function in the places that matter most.

  • Five trigger types were removed outright

    removed

    Combat Log Event (CLEU), Health, Swing Timer, Range Check and Assisted Combat Next Cast. These are not degraded, they are gone - an aura built on any of them has no equivalent in the fork.

  • A new durationObject progress type

    added

    Displays progress from a duration object in text, icon and bar regions, which covers the single most common thing players want back: a bar that still counts down a buff or cooldown it is not allowed to read.

  • Static progress bars accept secret values

    added

    A bar can render a value the addon cannot read directly, with limits on adjusting the minimum and maximum while the value is secret.

  • A "Secret Restrictions Active" load option and condition

    added

    Lets an aura detect that it is being restricted and show something else instead of quietly showing nothing. This is the piece that turns a silent failure into a visible one, and it is the reason to prefer the fork even for auras that mostly still work.

  • Cooldown displays are partially supported

    partial

    Basic information shows when the full value is unavailable.

What you gain

Partial function for secret-restricted content: duration bars and cooldown icons that would otherwise show nothing at all, and a condition that tells you when you are being restricted.

What you give up

Five trigger types entirely. Any complex tracking or condition built on combat log events, health, swing timers or range will not function, and no setting brings it back.

How to tell a dead aura from a badly configured one

Neither shows an error, which is what makes this expensive. Work in this order and you find out in a minute instead of an evening.

  1. 01

    Add a "Secret Restrictions Active" condition to the aura and give it something loud to show. If it fires, the aura is not broken - the data is being withheld, and no amount of reconfiguring will change that.

  2. 02

    Open the aura and read its trigger type before you debug anything else. If it is Combat Log Event, Health, Swing Timer, Range Check or Assisted Combat Next Cast, stop: it will never fire again and the time is better spent replacing it.

  3. 03

    Test on a target dummy, not in a key. A silent failure and a mechanic that did not happen look identical in a pull, and you will blame the wrong thing.

  4. 04

    Change one thing at a time. Silent failure plus trial and error is how an afternoon disappears.

Where to get the imports, and why they are not listed here

Wago added a category for WeakAuras forks. Use their site for the catalogue:

Browse the fork category ->Search Wago ->

Both links are real routes in Wago's own client router - /browse/:addon and /search/:mode are declared in the JavaScript the site serves, read on 2026-09-08. Whether the m33kauras category is populated, and what sort controls it offers, could not be checked from here: wago.io renders entirely in the browser, so fetching it returns an empty 3 KB shell on every path, including paths that do not exist.

Why this site does not mirror or search their catalogue

Wago publishes no machine-readable search. Its data host, data.wago.io, answers exactly one useful route: /api/check/{type}?ids=... for weakauras and plater, which checks imports you ALREADY have for updates. It cannot list, browse, sort by date or filter by patch. There is no /api/search and no /api/browse - both return a clean 404 from their router - and there is no OpenAPI document. Twenty-plus route shapes were probed. Mirroring their catalogue here would mean scraping a single-page app, which breaks on their next deploy and is not ours to take.

So use their site for the catalogue and this page for the judgement. Sort their list however you like; the thing that decides whether an import works is the trigger it is built on, and that is above.

Still open

  • Whether the Wago m33kauras category is populated, and what filters it offers, is unverified - the site renders in the browser, so a fetch returns an empty shell.

  • Whether SeraphAuras and ThisWeeksAuras, other forks in this space, are current was not verified: CurseForge refused automated requests when this was checked.

  • How much of a typical aura pack survives the five removed triggers is not quantified anywhere found. Expect to test your own auras rather than assume a percentage.

  • Whether upstream WeakAuras2 has since restored any of this is not tracked here. Its release notes are linked above; read them rather than trusting this page's date.

Sources

  • M33kAuras PR #8 - Midnight compatibility - Merged 2026-04-19. The mechanism, the removed triggers and the workarounds, in the author's own words. Every claim tagged verified below is read off this page.
  • M33kAuras releases - Latest release 5.20.7-rg4-m86, 2026-09-06. The repository states it is forked from WeakAuras/WeakAuras2.
  • WeakAuras2 releases - Latest release 5.22.0, 2026-09-05. No unmaintained notice. Checked because the opposite is widely repeated.

Checked 2026-09-08.

If a trigger listed here as not removed turns out to fail silently for you, say so in the comments with what it watched. That is the kind of thing only players can find, and it is the fastest way this list gets better.

Comments

Comments load when you reach this section.

Loading comments...