Overlord

6.3.6

Sync fixes — zones, capitals, Guild Keep, wood contribution

Fixed

• Ghost capture at 0:00: Remote observers can revert a stale in_progress zone after 45s without fresh ZS when physically on the disk, without requiring interpolated holdTimeElapsed to reach the full hold time (6.3.0 regression).
• Capital siege timer reset: Allies joining an advanced in_progress capital no longer cap remote holdTimeElapsed to ~15s; anti-exploit cap applies only when becoming active on a new capture, not when resuming an ongoing siege.
• Guild Keep desync: GC and post-capture GK use full community relay (40 whispers + 2.5s retry), raid/group path, and 1-hop community relay after accepted GC/WB. SR always includes GK snapshots (no community-club gate). Held keeps with claimedAt but updatedAt=0 sync via claimedAt timestamp; same-faction held conflicts tie-break on claimedAt. Wood regen no longer bumps updatedAt for non-local sensors.
• Wood contribution ladder: WB broadcasts match GC coverage (group + community + retry + relay); SR WB rows include site and guild when a keep is held so remote clients can record contribution.
• Guild Keep leaderboard: Opening the panel invalidates tenure cache and refreshes immediately (no stale tenure display).

Unchanged

• Zone sync payload formats (ZS/ZA), gold mines, Check PvP export, and primary capture channel behavior unchanged from 6.3.5.

Recommended after updating

• /reload on all clients after updating. After login, wait a few seconds for SR/GK catch-up. If a keep or contribution column still looks wrong, reopen the leaderboard or recapture once so GC propagates.