v2.1.3

• Fixed group messages rejected when a member on the player's realm has no realm suffix. Check UnitRealmRelationship before adding the local realm name. Unknown, connected, and other realms still require their own readable realm name.
• Added tests for Merlock delivery with NSRT loaded in raid, party, and instance groups, and for NSRT cauldron messages with no realm suffix.

Validation: 43 automated tests pass. A separate simulated integration check loads the installed NSRT 12.1.24 Comms.lua and verifies Merlock delivery and both cauldron receivers. Live sound playback still requires an in-game check.

API checks: installed Midnight 12.1.0.69933, NSRT 12.1.24, and Blizzard's current unit API definitions. NSRT's installed ResolveGroupMemberUnit also handles a missing member realm name.

v2.1.2

• Fixed pulls that received no chudding roll because the selected player did not receive the current BigWigs timer. Select the roll player from clients that observed the current countdown. The proc chance remains 1 in 20.
• Keep current timer replies when another client queries the group. Debug logs now show the observed timer, the assigned roll player, and the roll value.
• Fixed chudding procs lost when the countdown stop event arrives before the encounter starts. A stop without an initiator now triggers the pending proc. A manual cancellation still stops it.
• Use the player's realm API for the local message identity. Missing realm data for a remote group member is still rejected.
• Play the local Merlock and mage-food alerts before sending group messages. Local playback no longer requires a message identity.

Validation: 40 automated regression tests pass. The new tests count rolls across repeated pulls with different timer observers in raid, party, and instance groups. They also cover missing local realm data, early countdown stops, manual cancellation, and Merlock sound playback and group delivery. Live in-game checks are still pending.

API checks: installed Midnight 12.1.0.69814, BigWigs v424.8, and NorthernSkyRaidTools 12.1.23. Blizzard's countdown event handler confirms the initiator payload. The installed BigWigs pull handler treats a stop without an initiator as combat.

The installed BigWigs pull plugin can reject a timer before it sends BigWigs_StartPull, including for different zones. Loading BigWigs alone does not prove that a client observed the countdown. Group members must use this update together: roll selection now requires the observed deadline in the BossMods announcement.

v2.1.1

• Fixed a nil realm error during group messages and BossMods announcements.
• Skip unit names with missing realm data. Check the local realm before adding it to a message sender name.

Validation: 31 automated regression tests pass, including missing realm data and recovery. Live in-game checks are still pending.

v2.1.0

Updated for WoW 12.1.

All group members must update together. This release changes the shared-message format. Earlier versions cannot share procs or facts with this version.

• Fixed missed chudding-time procs, including cross-realm groups and messages that arrive before the local BigWigs timer.
• Fixed roll leader selection after zoning, disconnection, or a setting change. Procs are now shared in raid, party, and instance groups.
• Fixed early-pull playback, duplicate decisions, and old cancellations that affected a new pull.
• Made L'ura windchime facts independent of BigWigs and the pull-sound setting. Fixed duplicate facts at clock boundaries and recovery for late receivers.
• Fixed bingo board and mark restoration after reload.
• Delayed Mythic+ completion reads and added bounded retries for key updates. Reminder data is read again after combat.
• Included the required libraries so the addon can load on its own.
• Added message sender checks, temporary send retries, and expiry for old messages. Removed duplicate local mage-food and Merlock alerts from delayed message echoes.

Validation: 28 automated regression tests pass, including a simulated 40-player raid and loading with no other addons. Live in-game checks are still pending.

At least one enabled BigWigs client is needed to produce a chudding pull roll. Receivers and windchime facts do not need BigWigs.