WarlordsPvP

2.4.7

Bug fix

• Typing /wl points now opens the leaderboard on the first try. Previously the very first time you ran the command after logging in, nothing visible would happen — you had to type it again to see the window. The window was being created and then immediately hidden by the toggle logic. Fixed.

2.4.6

Critical bug fix

• The achievement leaderboard now actually shows your guildmates. Since the leaderboard feature shipped in v2.4.0, every message the leaderboard received from other guild members was being silently dropped because of a parsing bug. Your own client correctly broadcast your points to the rest of the guild, but couldn't read anything coming back. That's why — even with everyone on the same recent version — the leaderboard only ever showed one entry: yours. After updating to v2.4.6, your guildmates' data will actually arrive and the leaderboard will populate as designed.

After updating, click the "Refresh" button on the leaderboard window. The receive code now works, and any stale-looking entries left over from prior sessions will be overwritten with current data within a few seconds.

2.4.5

A leaderboard improvement and a diagnostic, companion to v2.4.4. (Note: the real underlying leaderboard bug turned out to be the parser issue fixed in v2.4.6 — the changes in this release are still useful but did not on their own make the leaderboard work end-to-end.)

Improvement

• Opening the achievement leaderboard now also shares your points with the guild, not just asks the guild to share theirs. Helpful for the case where a guildmate came online after you did and never saw your initial broadcast.

Diagnostic

• The Refresh button on the leaderboard reports back what happened. Instead of just refreshing silently, it waits up to 10 seconds after you click and tells you how many guildmates actually responded. If nobody did, it lists the most likely reasons (you're the only one online with the addon, others are on a too-old version, etc.) so you can troubleshoot without guessing.

2.4.4

A small follow-up release with one bug fix and a matching diagnostic for raid-warning sync.

Bug fix

• The "Sync to Officers" button in the raid warnings window can no longer create an infinite back-and-forth between officers. The way the button worked, two officers in a guild together would have bounced sync messages back and forth every few seconds forever once both had the addon installed. The bug was masked in v2.4.0 because broadcasts didn't work at all, and in v2.4.1+ no one had a second officer with the addon to trigger it. Fixed now before it could bite anyone.

Diagnostic

• "Sync to Officers" reports back what happened. Instead of just printing "Raid warnings synced with guild officers" and leaving you wondering whether anyone heard you, it now waits up to 10 seconds and tells you how many officer responses came in. If none arrive, it lists the most likely reasons (you're the only officer online with the addon, other officers are on a too-old version, or other officers aren't online).

2.4.3

A cleanup release. One real bug fix; the rest is internal restructuring that pays off the next time someone touches the code. Nothing changes from a player's perspective except as noted in "Bug fixes" below.

Bug fixes

• Bounty init no longer re-runs on every loading screen. The bounty system was re-initializing its data structures and rebuilding its lookup cache every time you crossed a zone, took a flight, or entered a dungeon. It now does that work once at login, like the rest of the addon. Same fix applied to the guild settings sync system.
• Dead retry loop removed. The achievement leaderboard had a fallback that retried registering itself with the addon's communication channel if the first attempt failed. After the v2.4.2 namespace fix, the first attempt always succeeds — the retry was dead code and is now gone.

Behind the scenes

• Settings panel layout was reworked with a new helper that places sections and checkboxes by relative position instead of by hand-tuned pixel offsets. Three of the four content tabs (General, Battlegrounds, Milestones) now read top-to-bottom like a recipe instead of a coordinate puzzle. Visual layout is unchanged; the win is for the next person who wants to add a setting.
• Four sync subsystems (bounty, raid warnings, achievement leaderboard, guild settings) had their public API moved into proper namespaces (WLP.Bounty, WLP.RaidWarnings, WLP.AchievementLeaderboard, WLP.GuildSync) with backward-compatible aliases for the old names. No external integration breaks.
• Two shared helpers added for code that runs once per session and code that needs to delay slightly to avoid all guild members responding at the exact same instant. The four sync subsystems were migrated onto the helpers, eliminating six copies of the same delay-math expression.

Deferred indefinitely

Two long-standing internal-cleanup items were considered and explicitly deferred:

• Replacing the addon's communication format with a standard library serializer (AceSerializer) was deferred. It would require a multi-release rollout so that members on mixed versions can still exchange bounties / raid warnings / leaderboard data, and the existing format works fine. Revisit if the format ever becomes a pain point.
• Renaming all the addon's WLP_* global helper functions into a WLP.X.Y namespace style was partially completed (the four sync subsystems are done) and the rest is left as incremental future work. There are about 200 more call sites scattered across the achievement-definition data tables; doing them all at once is high-churn work for low payoff. Apply the established pattern to individual helpers as you happen to be in the file.