Development overview
Feature status.
What is built. What is taking shape. What comes next.
Register review
Reschedule Match reopens contestant availability in the fixed rematch window for an unplayed primary under review. Client/strategic publication, operator restart and live acceptance remain pending. Tournament core stays 100%; counts remain 49 (30 done, seven partial, 12 planned). See evidence and verification.
Shared match availability now anchors full reservations even for short overlaps. Either opponent can report a conflict; match windows and division/series prize amounts have distinct labels. This update awaits client/strategic and wiki/dashboard publication. Core estimates and counts are unchanged. See the implementation.
Empire and emperor rename/delete maintenance now covers tournament and later feature references, with atomic charges and pushed identity snapshots. Migration 95 and compatible publication are pending. Six browser checks and real API database regressions pass; core estimates and counts are unchanged. See the reference audit.
Waiting tournament reentry now clears checkout through strategic admission. Exactly one checked-in contestant automatically wins when the arena window closes; earlier deadlines preserve the waiting arena. A guarded migration prepares Lyran Commonwealth's historical victory and bracket restoration. Compatible release and migration application remain pending. The 49-feature counts and core estimates are unchanged. See the fixes and verification.
The UTC tournament correction is verified in the running strategic container. Event-date daylight-saving checks, one-hour database offset regressions and 15 browser checks pass. Black Ice's recorded NZDT appointments are consistent; the original advertised date/time and browser timezone remain unconfirmed. Core completion and counts are unchanged. See the daylight-saving follow-up and original UTC investigation.
Public tournament starts, finalized match results and division champions are included in World History, with a Tournaments filter, source navigation and direct server updates. Private/test/provisional events are excluded. Migration 90 and compatible rollout remain pending; feature counts and core estimates are unchanged. See implementation.
The tournament header countdown is implemented locally, showing applicable real-world deadlines only within two hours with pushed state and local ticking. Early-start consent, waiting checkout, fallback-time acceptance/conflict reporting and admin rescheduling are also implemented. Compatible client and both servers, migration 89 and publication remain pending. See the phase contract.
Completed battles record wins and losses without a loser concession. Provisional outcomes are visible and incompatible concession actions are hidden. Focused browser, worker and disposable MySQL checks cover the new controls. See the investigation and implementation. Counts and core completion estimates are unchanged.
The Ignis SRM tank silhouette correction awaits client publication. Infantry-support vehicles use tank artwork in map markers and unit details. Battle client remediation remains 80%; counts remain 49 (30 done, 7 partial, 12 planned). See implementation.
Arena unit and movement-preview facing arrows now use bright gold with a dark edge for visibility against dark green woods and light terrain. Client publication remains pending; terrain stays 100% and counts remain 49 (30 done, 7 partial, 12 planned), reviewed 10 October 2026. See implementation.
Military commissioning and decommissioning use server updates without duplicate reads after acknowledgement. Commissioning closes its dialog on confirmed success and retains choices on rejection. Fifteen focused browser checks pass; client/wiki/features publication remains pending. Military force support stays 80%.
The admin AI arena View correction and smoke-only inspection are verified locally and await compatible rollout. Feature completion estimates and counts are unchanged.
Three player-request additions are implemented locally: confirmed manufacturing reset using current cancellation rules, attacker firing arcs/ranges over actual hexes, and tournament pools using 50% scheduling compatibility and 50% current skill. Arc/range display has an account-saved Game Settings / Combat option, on by default. The target popup stays within the visible map with scrolling weapons and fixed actions; extra arc/distance/range row text is removed. Compatible rollout, migrations 82/83 and future-event validation remain pending. The register contains 49 capabilities: 30 done, 7 partial, 12 planned. See the implementation and verification.
The day-change worker-assignment correction passes local concurrency and progress checks. Strategic-server rollout and wiki publication remain pending; Administration stays 100%.
The vehicle incoming-hit correction is verified locally, including the reconstructed Catapult shot and right-armour damage. Battle Server rollout and wiki publication remain pending; Arena expansion stays 15%.
The public player wiki brings together 21 guides, all with images, plus full-text search and topic filters. Thirty-five SVG diagrams explain workflows and comparisons, including mech examples of crossed LOS hexes, hexside choices and combined woods/smoke, plus a mech/tank unit-height comparison and replacement side views for both elevation scenarios, with full-size views. The illustrated LOS expansion awaits wiki publication. Feature instructions identify availability and unfinished integrations.
New account Premium conversions with multiple annual empire plans now start a fresh year and credit all remaining paid time, with any surplus refunded. Local transaction and replay checks pass; matching deployment and migration 69 remain pending. The named-account migrations 67/68 are a separate reconciliation.
Temporary research boosts are implemented: a single on/off toggle, immediate end-time updates and one-click stopping that recovers automatically if the server state changes. Ordinary Research buildings gain 50% output with staffing-based extra upkeep; Research Complexes are excluded. The register tracks 49 capabilities. The features page publishes together with the corresponding rollout; ongoing enablement requirements and future extensions are listed separately.
The 6 October retention repair restores startup catch-up and daily cleanup for 14-day fire diagnostics and 365-day cash history. Server rollout remains pending. See the retention implementation note. Current counts are 49 capabilities: 30 done, 7 partial, 12 planned.
Push now stays below Fire and above Punch while the weapon list scrolls, with matching styling and percentage hit chance. This control is included in the coordinated terrain release. See the Push control note.
Implementation register
Explore the features
No matching features
Try a broader search or reset the filters.
Estimate notes
Scope, not a countdown.
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%.