CCAlarm

Warns loudly when your healer or tank is crowd-controlled.

In Mythic+, the second nobody notices the healer is stunned is often the second that wipes the group. CCAlarm puts it where you cannot miss it: red warning text at the top centre of your screen, the icons of the active effects with their remaining time counting down underneath, and a sound.

Healer and tank get separate sounds, so you know who was hit without looking.

It works inside Mythic+ and PvP — where Blizzard keeps auras secret from addons and most crowd-control trackers simply go quiet. See below for how.

Why this is harder than it sounds

Detecting crowd control on other players is genuinely difficult in Midnight, and it is worth explaining what CCAlarm does differently.

That last row is the one that matters. Blizzard keeps auras secret from addons in exactly the content where a stunned healer is most expensive, so an addon that reads auras is blind precisely where it is needed — and a missing alarm looks just like a quiet pull.

So CCAlarm does not read auras for the alarm. It declares what it wants and lets the game engine do the work:

• Icons come from an aura container declared with Blizzard's own CROWD_CONTROL filter. The engine tracks, filters and draws; the addon never sees the data. Because Blizzard's own classification decides, this covers crowd control no spell list has ever heard of.
• The warning text is a second container whose button carries nothing but a line of text. The engine shows and hides it with the aura, so the text appears exactly while the unit is controlled — again without a single aura read.
• The sound is registered with C_UnitAuras.AddAuraSound, per unit and spell ID, and played by the game itself.

The sound is the one part still bound to spell IDs — and almost every addon in this space hardcodes that list. A hardcoded list is wrong the day a patch ships and stays wrong until someone updates it.

CCAlarm learns its list instead. LOSS_OF_CONTROL_ADDED fires whenever you are controlled, and it carries Blizzard's own classification (locType) together with the spell ID. Whatever stuns you in a dungeon also stuns the healer and the tank in that same dungeon — so the list fills itself as you play and then covers your whole group.

So the first encounter is not wasted, any unknown harmful aura seen on a healer or tank is recorded as a candidate. /ccalarm candidates lists them by name and ID, ready to be promoted with a single command.

SCHOOL_INTERRUPT and DISARM are deliberately never learned — neither stops anyone from moving or healing, and alerting on them would only add noise.

Getting started

1. Copy the CCAlarm folder into Interface/AddOns/.
2. Restart WoW completely. New addons are only read at startup; a /reload is not enough.
3. Run /ccalarm test for a five-second dummy alert, so position and sound are right before it matters.
4. In a group, /ccalarm status shows how many units are watched and how many sounds are registered with the engine. Both above zero means it is armed — worth one look, because a working alarm and a broken one both stay quiet until something happens.

There is nothing to configure up front. It works out of the box.

Configuration

Everything is adjustable in game under Options → AddOns → CCAlarm, or with /ccalarm config:

While unlocked the frame is tinted so you can grab it even with no alarm running. The complete anchor is saved, so the display returns to the same spot after a resolution or UI scale change.

Sounds

Two alarm sounds ship with the addon as files — one for the healer, one for the tank — and they are the defaults. They exist because the engine-side alarm takes a sound file: the client's built-in interface sounds are sound-kit numbers, which AddAuraSound will not accept. Those built-ins are still offered and still play in /ccalarm test; pick one for the live alarm and the bundled file stands in for it, and /ccalarm status says so rather than leaving you to wonder. Anything other addons have registered with LibSharedMedia as a file works fully.

Slash commands

German aliases work as well (einstellungen, liste, kandidaten, dazu, weg, leeren, an, aus).

No dependencies

CCAlarm ships everything it needs. LibStub, CallbackHandler-1.0 and LibSharedMedia-3.0 are embedded — no other addon is required. Because LibStub shares libraries, a newer copy from another addon wins automatically, and fonts or sounds registered by other addons simply show up in the lists as a bonus. A test in the build pipeline enforces that this stays true.

Limitations

Stated plainly, so nobody relies on something the addon cannot do:

• The spell list only drives the sound. Icons and warning text follow Blizzard's own crowd-control flag, so they cover effects no list knows. The sound is registered per spell ID and stays silent for spells the list has not learned yet.
• The list starts empty. It fills as effects hit you for the first time, or as you promote candidates.
• Inside Mythic+ and PvP nothing new is learned. Auras are secret there. The alarm itself still works — the game draws and plays it — but new spells can only be picked up outside.
• The engine takes a sound file, not a sound-kit id. See Sounds above.
• Private auras and some encounter mechanics are invisible to addons. What Blizzard hides, this addon cannot see either.
• Group members only. For yourself, WoW already draws its own loss-of-control display in the middle of your screen.
• Roles come from the group role assignment (UnitGroupRolesAssigned). A member without an assigned role is not watched.

Languages

English and German. English is the primary language; missing keys fall back to English rather than showing a blank.

Built to be trusted

CCAlarm ships with a test harness that stubs the WoW API — aura containers and engine sounds included — so the addon can be verified without launching the game. 144 assertions cover both directions: that healer and tank are watched with the right filter and the right sound, and that a damage dealer, a deselected role, a switched-off addon or an excluded zone produce nothing at all. Among them the cases that are hard to notice in play: that the alarm still stands while auras are secret, that sounds the engine refuses mid-pull are re-registered afterwards, and that a client without aura containers says so once instead of failing quietly. Every push runs those checks, together with gates for scope, translations, self-containment and packaging, and a release is refused if any of them fails.

Source, issues and feedback: github.com/Sparxx947/CCAlarm Released under the MIT license.