WN Bluemap

wn-bluemap: 1.2.2 (2026-08-15)

Fixed
- Rebuilds (a periodic full recompute in particular, and any burst of claim/war/nation changes) did every nation's per-block ground-height scanning in one synchronous main-thread call, risking a multi-second tick stall; now paced across ticks (nationsPerTick, default 3).
- The periodic full-rebuild mechanism existed only to catch a nation's color change; color changes are now detected directly and cheaply every pass, and the periodic interval is now pure paranoia insurance (raised from 20 to 500).
- Leader/member display-name resolution is now cached per nation, invalidated only by membership changes, instead of re-resolving every nation's full roster on every pass regardless of trigger.
- A real memory leak: color/name caches had no eviction; a disbanded or reclaimed nation's entries lingered forever. Now evicted the same pass its territory cache entry is.
- The war-overlay pass rebuilt the entire nation roster from scratch once per at-war nation per dimension instead of once per pass.
- A per-dimension rebuild loop computed the same dimension-key string twice per iteration.
- MarkerService#beginPass could NPE on a null ServerLevel for a dimension FTB claim data still references but isn't loaded; because failed passes retry, this permanently blocked map updates for every dimension, not just the broken one. Now skips only the affected dimension.
- The member-name cache's dirty-invalidation flag was cleared before the actual re-resolution ran, not after; any exception mid-pass silently dropped a pending invalidation, showing a stale roster indefinitely.

Changed
- Config file relocated to config/warring-nations/wn-bluemap-server.toml; migrated automatically on first boot.