Hunter's Mark Alert

# Changelog

## 1.3.0

### Patch 12.1 support (Curse of Ula'tek)

- Now built for Midnight **12.1.0** (Interface 120100) while still supported on 12.0.7. The TOC declares both, so it loads without the out-of-date flag on either.
- Upgrading from 1.2.x: replace the folder. Your saved settings carry over unchanged.

### Rewritten aura detection for 12.1's Secret Values

- 12.1 makes aura lookups by index, slot, or instance ID raise a Lua error whenever auras are secret — which covers all instanced combat, encounters, keystones, and PvP. Detection now goes exclusively through `GetAuraDataBySpellID` / `GetAuraDataBySpellName`, the only aura reads that survive those restrictions. The addon no longer walks the target's debuff list at all.
- **Self-calibrating.** The first time the addon reads the Mark while auras are secret, it has proven the Mark is exempt from Secret Values and treats a missing Mark as conclusively absent for the rest of that session. Until that is proven, a missing Mark in restricted combat is treated as unverifiable rather than guessed.
- **Your own auras can now be hidden.** Through 12.0 your own auras always stayed readable; 12.1 can withhold those too. The "alert when unverifiable" setting now governs both your own Mark and the group-wide check.
- Handles `UnitClass` returning a secret under restricted content — the group-wide "any hunter's Mark" scan now always runs there instead of being an edge case.

### Options & diagnostics

- Renamed the detection checkbox to **"Alert even when aura data is hidden"** (was "…when others' auras are hidden"), with an updated tooltip reflecting that your own data can now be hidden too.
- `/hma debug` now reports the active aura-lookup path, whether your auras and all auras are currently secret, and whether the Mark has proven itself readable while secret — run it inside a real keystone or raid pull to see which case you are in.

### Known caveat

- Whether Hunter's Mark is exempt from Secret Values in 12.1 is Blizzard's undocumented call. The 12.1 detection path is covered by offline tests but has not yet been confirmed on a live 12.1 client. The addon self-calibrates either way, but if the Mark is not exempt it can only warn on the unverifiable setting rather than on proven absence.