Feature status.

The 31 October Battle Value correction includes active crewed towers in Overview and adds server BV subtotals numerically. Compatible client/server publication remains pending. Unified interface remains 100%; review totals are unchanged. See Battle Value correction.

The 31 October licence catalogue filter hides designs the requesting empire can manufacture through completed research. Incomplete research stays eligible; existing agreement exclusions remain. Database regression passes; strategic rollout is pending. Licensing stays 100%. See research filter.

The 31 October review allows manufacturing licences between distinct eligible empires on the same account. Faction/world membership, separate party consent and royalties remain required. Server regression and build pass; strategic rollout is pending. Licensing remains 100%; totals remain 50 records (33 done, eight partial, nine planned). See same-account licences.

Licensed designs now appear in the left Available Manufacturing list with progress and per-agreement production limits. Reserved allowances and unfinished expired/revoked work stay visible; licence-only controls remain in Queues. Compatible client/server publication is pending. Licensing stays 100%. See catalogue visibility.

The 30 October visibility correction prevents large Land War firing updates from clearing the force. Projection and transport retain complete authorized contacts within matching bounds; ordinary arena limits stay unchanged. Tests/build pass and the local battle view is restored. Production publication is pending; Land War stays 35%. See fog capacity and recovery.

The 30 October initial-deployment update defaults air drops to the end of Turn 1 Movement. Transport deadlines and later chosen schedules still apply. Tests/builds pass; compatible strategic/client publication is pending. Land War stays 35%. See initial arrivals.

The 30 October timing update removes the overall Land War timeout, including for restored battles. Phase timers remain active and the client shows No time limit. Tests and build pass; compatible publication is pending. Land War stays 35%. See untimed battles.

The 30 October landed-force correction adds arriving units to your own roster with AI/Human controls and retains detected enemy contacts. A saved battle replay renders 34 own and 47 enemy markers. Client publication/reload is pending; Land War stays 35%. See landed-force visibility.

The 30 October Land War incoming-force notice explains empty pre-drop views using wave counts and landing timing, without revealing hidden opponents or landing hexes. Landing, fog and socket regressions pass; compatible battle/client rollout is pending. Land War stays 35%. See incoming-force notice.

The 30 October Military update displays committed Land War flights, destinations and arrival times, then battle and settlement status. Scoped server pushes cover staggered arrivals; ordinary transport stays separate. SQL/client regressions and build pass; compatible rollout is pending. Land War remains 35%. See Military deployment status.

The 30 October Land War entry correction removes duplicate error dialogs, suppresses repeated pending entry clicks and enables Enter battle at the transport deadline without polling. Direct-air reinforcements remain supported. Client rollout/reload is pending; Land War stays 35%. See entry error handling and checks.

The 30 October Land War chat correction adds a single Allied forces channel with current combat-side authorization and pushed entry history. Enemy and revoked access are denied; normal chat returns on exit. Client/strategic rollout and migration 115 remain pending. Land War stays 35%. See allied chat behavior and checks.

The 30 October Land War entry correction widens checkpoint and result storage for full battle states above 16 MB. Migration 114 preserves reserved deployments; 18 MB save, restore and result-replay checks pass. Migration application remains pending and Land War stays 35%. See checkpoint capacity and recovery.

The 30 October War Room correction keeps large battle snapshots out of database sorting, restoring the list and automatic dispatch without increasing server memory settings. Strategic rollout remains pending; no migration is needed for this correction. Land War stays 35%. See sort-memory evidence and verification.

The 30 October Land War correction admits defending mechs, vehicles and infantry, with a 100-defender default and recovery for orders blocked by the former BattleMech-only gate. Mixed-force launch, charging and checkpoint checks pass; compatible server rollout and migration 113 remain pending. Land War stays 35%, with 50 records: 33 done, eight partial and nine planned. See mixed defenders and recovery.

The running-rematch no-show correction preserves current attendance and prevents cancellation of durable countdown/live/terminal battles. MySQL lifecycle and race checks and the strategic build pass; strategic-server rollout and wiki publication remain pending. Monthly tournaments stay 100%. See the incident and saved combat evidence.

The 10 October Division C correction prevents one unresolved match from cancelling the division. Automatic decisions use surviving BV, then unit count, with remaining rematch or both-out fallback and a full hour of administrator review. Guarded manual SQL and ordered migration 87 restore exactly 19 erroneous cancellations and one prize reservation under a hold until the fixed server can resume it. Local database checks pass; rollout and production recovery remain pending. Monthly tournaments stay 100%; the register remains 49 capabilities (30 done, seven partial, 12 planned), reviewed 10 October 2026. See incident and recovery instructions.

The 10 October concede and no-show request correction preserves match revisions through transport and server validation. Six browser checks, lifecycle regressions and the server build pass; compatible client/server rollout and wiki publication remain pending. Monthly tournaments remain 100%, with 49 capabilities: 30 done, 7 partial, 12 planned. See the investigation and verification.

The 8 October database lag patch reduces background payroll writes, scopes reclamation by world, fixes tournament lock ordering and paces cleanup. Both server builds and focused MySQL checks pass; compatible rollout and migration 81 remain pending. Feature completion and review counts are unchanged. See the query remediation evidence.

The 8 October tournament completion correction fixes rejected timeout draws and reordered result retries. Focused regressions and both server builds pass; server rollout and live recovery remain pending. A primary draw keeps its 60-minute review before the conditional rematch. Monthly tournaments stay 100%, with counts and review date unchanged. See the timeout completion evidence.

The 8 October phase-ordering correction prevents an older waiting Move frame from overwriting Fire during initialization or reconnect. Private/betting/tournament phase updates now apply in order and retire on disconnect. Two Node regressions, six new browser checks and three All Done phase-binding checks pass; an older missing-popup completion fixture also fails on HEAD. Client/wiki publication and live acceptance remain pending. Scope, counts and review date are unchanged. See the phase-ordering evidence.

The 8 October tournament entry correction accepts the registered account despite differences in letter casing, retaining exact empire and attempt guards. Lifecycle, disposable-MySQL entry and battle-access tests and both server builds pass; compatible rollout and wiki publication remain pending. The 38-minute availability warning reflects the recorded fallback schedule. Blank spectators, AI-play and firing timeouts remain unconfirmed. Completion, counts and review date are unchanged. See the entry investigation.

The 8 October battle reservation correction clears prior-round weapon and physical locks and rejects retired detail responses. The Node regression and twelve focused browser checks pass; client/wiki publication remains pending. Related tournament firing-timeout and movement-clock reports remain under investigation. Battle client remediation stays 80%, monthly tournaments 100%, with the same 46 features and 8 October review date. See the round-state investigation.

The 8 October tournament selection fix opens an enrolled ongoing series ahead of future scheduled events and returns My Tournament to that enrollment. Six focused browser regressions pass; client/wiki publication remains pending. Monthly tournaments remain 100%, with counts and review date unchanged. See selection fix and verification.

The 8 October tournament update retains voluntary Join Battle during the current primary/rematch fight window, including availability collection. Each opponent must choose early entry themselves. Automatic entry runs only from the assigned match start through its 15-minute grace period, including roster-presence and reconnect retries. Local MySQL boundary/consent regressions and browser documentation checks pass; compatible client/server rollout and wiki publication remain pending. Monthly tournaments stay 100%, with 46 capabilities: 27 done, 7 partial, 12 planned, reviewed 8 October 2026. See investigation and verification.

The 8 October startup recovery update waits for matching empire details, retries transient failures within bounded deadlines and exposes Retry after failure. Session/selection changes cancel recovery and fence late replies; reconnect identity checks remain in place. Client 0.25.5 rollout and wiki publication are pending. Authentication stays 100%; counts remain 46 capabilities: 27 done, 7 partial, 12 planned, reviewed 8 October 2026. See implementation and verification.

The requested Game Updates login revert restores direct notices and once-per-event receipt delivery, removing pending reads, interruption queues and dismissal acknowledgements from the shell. Startup recovery and the Game Updates archive remain. All 42 focused browser cases, disposable MySQL and the strategic build pass. Compatible client/server rollout remains pending; no new migration is required. Authentication stays 100%; counts remain 49 capabilities: 30 done, 7 partial, 12 planned, reviewed 10 October 2026. See implementation and verification.

The 8 October Buildings Destroy update accepts individual empty repair bays alongside ordinary buildings, with atomic rejection, revision checks and saved-command recovery. Compatible client/server rollout is pending. Construction stays 100%; Repair Bays stays 75%. The register remains 46 capabilities: 27 done, 7 partial, 12 planned, reviewed 8 October 2026. See implementation and verification.

The 6 October PayPal settlement repair installs the missing public HTTPS webhook proxy and verifies backend routing. A guarded recovery records the authorized recipient award once; migration and webhook replay cannot credit it again. PayPal processing remains 100%, with 46 capabilities: 26 done, 8 partial, 12 planned. See the settlement routing and recovery note.

Terrain and battlefield interaction is complete at 100%: recorded terrain profiles, Push and displacement falls, woods destruction, Calm fire/smoke, controls, icons and player guides. The features page publishes with the compatible rollout and wiki. Monthly FFA/PVE rotation waits for all player entries to leave, then uses gentle vehicle-accessible terrain, with settings migration 79. Counts are 46 capabilities: 27 done, 7 partial, 12 planned. See publication timing and monthly rotation and vehicle limits.

Forest woods targets are Low 30%, Medium 50% and High 70% before paths are cleared. The coordinated release includes the Forest phase of consolidated migration 77; saved maps retain their terrain. Catalogue migration 78 remains separate. Databases already at 77 or later do not rerun the merged phase automatically. See the Forest density implementation note.

World Map terrain changes after baseline 76 are consolidated into migration 77, including Mountain woods/rough defaults and saved-zone density corrections. The normal migration runner preserves layout-hook ordering, receipts, retry recovery and protected assets. See terrain migration details. Non-calm weather, additional terrain/equipment and persistent Land War settlement remain future work.

These are editorial estimates from the local source review and dated implementation records. Working foundations, player workflows and remaining integration are weighed together; the percentages are not calculated from document length, phase counts or completed tickets.

A feature can have substantial code and still lack its main playable workflow. Land War is one example. Each partial feature explains its estimate under Scope & evidence.

Features have different sizes and share foundations, so this dashboard does not average them into a project completion score. Supporting documents are grouped under their feature rather than counted separately.

The 5 October Land War design requires defender-wide recovery, cumulative loss limits and combined occupation/reparation and hostile-fragmentation safeguards before PvP. Balance and implementation remain pending; Land War stays 30%. See the defender recovery requirements. Counts remain 44 capabilities: 24 done, 7 partial, 13 planned.

The 5 October queue correction retains the 20-queue creation limit and existing queues above it. Remove Queue returns workers and cancels remaining jobs after confirmation; finite finished queues disappear automatically. Matching client/server deployment is pending. See the queue implementation note. Queue core remains 100%; counts remain 44 capabilities: 24 done, 7 partial, 13 planned.

The 5 October tournament update adds weekly registration-time defaults with per-round overrides. Monthly tournaments remain 100%; compatible deployment and migration 71 are pending. See the availability-defaults implementation note. Counts remain 44 capabilities: 24 done, 7 partial, 13 planned.

The 2 October World History implementation brings the current register to 44 capabilities: 24 done, 7 partial and 13 planned. The initial chronicle, completed-war visibility gates, verified imports and owner-approved world-firsts are implemented locally. Migration 63 and compatible deployment remain pending; historical evidence and unavailable territorial/alliance event sources are separate dependencies.

The 1 October review adds 19 feature technical specifications, including building repairs and military contracts, with shared engineering contracts and explicit release gates. Specifications remain planned implementation work. The register also tracks the local PayPal pending-payment correction and contains 44 capabilities: 20 done, 7 partial and 17 planned. The 2 October update completes local research/manufacturing queue implementation, including job and worker editing; migration 55, compatible deployment and enablement remain pending. Existing implementation estimates retain their dated source-review boundaries; the PayPal fix awaits production rollout. Client 0.21.9 prepares the Empire Planning claim fixes: water and already-owned zones are ignored, and ownership plus Military Support refresh after claiming. Thirty focused browser checks and server verification pass locally; compatible client/server deployment remains pending. The confirmed one-level uphill charge-displacement limit is verified locally; larger rises use the existing blocked-displacement destruction rule. Battle Server rollout is pending, and Arena expansion remains 15%.