36 lines
5.2 KiB
Markdown
36 lines
5.2 KiB
Markdown
# Migration status
|
||
|
||
The old workspace is a read-only migration reference. `dependency-audit.json` records legacy symbol references discovered during the audit. `migration-provenance.json` records the selected independently authored helper sources and their original hashes. `vanilla-resources.json` records exact GUID/path pairs resolved against the installed vanilla resource database. None of these records proves complete behavioural parity.
|
||
|
||
The base replacement has priority over extension feature migration. [Base responsibilities and implementation order](base-replacement.md) distinguish prototype coverage from remaining gameplay work.
|
||
|
||
## Implemented foundation
|
||
|
||
- Five projects, dependency isolation, new source resource identities and a new scenario identity.
|
||
- New mission state rules, scenario assembly, location/discovery state, vanilla faction catalog, native spawning, settings owner and once-per-round world-clock configuration.
|
||
- Independent extraction ownership, physical capacity checks, partial identity results, controller-based result presentation, early vehicle-loss handling and preparation rollback.
|
||
- Physical radio network, visual observation intake, report snapshots, bounded HQ journal and an initial infantry response coordinator.
|
||
- Core-owned document recovery and objective map markers, optional enemy-carried intel and shared field map, replicated discovery markers and a limited administration command surface.
|
||
- New Everon child world, definition-driven prison, two independent clue caches, medical stash, guarded outpost, radio and extraction sites using referenced vanilla resources.
|
||
|
||
## Incomplete milestones
|
||
|
||
| Milestone | Current evidence | Remaining work |
|
||
| --- | --- | --- |
|
||
| Dependency audit/setup/interfaces | Projects and automated isolation checks exist | Complete provenance review; mature player/objective service interfaces |
|
||
| Playable Everon loop | Archived Core 085442 (586 assertions) and companion 092512 (96 assertions) each pass two scripted rounds; ordinary Chat 093115 startup/admission and prison breach 092923 pass at their own sources | Manual route/stock balance, gameplay presentation, multiplayer lifecycle and clean runtime |
|
||
| HQ/support/companion integration | Genuine perception/radio/HQ/physical infantry response, finite mortar firing/expiry and exact inventory-transfer checkpoints pass | Complete and qualify aircraft, finite logistics, broader support failures, applicable commands/settings and full integration |
|
||
| Multiplayer/performance/release | Ledger, regression tools, isolated empty Linux server preparation and deterministic development-source handoff exist | Authenticated dedicated/client and 12-player sessions, broader failures/restarts, equivalent-workload FPS evidence, qualified native packaging/publication |
|
||
|
||
The prison/site layout is a prototype. Terrain heights were checked, but collision, slope, navmesh accessibility, vehicle seating and extraction takeoff have not passed gameplay acceptance. Two separate marked supply caches each hold two guaranteed radio documents. The western cache provides another route if the southern cache is lost; optional medical and guarded outpost stock add detours. Progression does not require random enemy intel. Geometry diagnostics replaced the sloping footprint with an open surveyed site and resized the gate to its opening. Normal gate-action completion and scripted victory rounds pass. The later destroyed-gate fixture applies real native damage/deletion and deliberately repositions the admitted body across the boundary; it does not prove walking through the opening or debris. Manual gameplay acceptance remains outstanding.
|
||
|
||
## Commands presently implemented
|
||
|
||
Core alone provides `/esc status`, `/esc settings`, `/esc mission radio show` and `/esc mission radio set N` for administrators, plus `/esc spectate next|previous` for spectators. With companions loaded, administrators also retain `/esc hq show`, `/esc hq log`, `/esc hq interval|squads|radius show`, `/esc hq interval|squads|radius set N`, `/esc intel carrying|reveal show` and `/esc intel carrying|reveal set N`.
|
||
|
||
Settings live in `$profile:rereintroduced.json`, with checked temporary writes and a backup. Names and defaults are explicit in `ERR_Settings.c`. `tools/import_settings.py` previews conversion of supported legacy AI/intel settings and explicitly reports deferred fields. Writing requires `--out` and refuses to overwrite an existing file. Old settings files are not silently imported. Existing tools, admin menus and other commands are not yet fully migrated; this subset is not a claim of preserved compatibility.
|
||
|
||
RHS, additional terrains, complete feature parity and virtual distant units remain deferred as agreed. The project's initial estimate of 160–280 hours described the entire successor; this foundation does not constitute all of that work.
|
||
|
||
See [current status](current-status.md) and the append-only [validation ledger](validation.md) for exact archive/source limits. All seventeen release cases and current-source clean-runtime qualification remain pending; prior passes cannot cover subsequent production changes. [Development source bundling](development-source-bundle.md) hands off editable authored projects only, not a native `.pak` or published release.
|