aussie/EscapistsReintroduced
1
0
Fork 0
forked from escapists/EscapistsReintroduced
Code Pull Requests Activity

Capture current mission, AI, map and administration development

Browse Source 
Include the current addon, terrain integrations, tools, regression tests and recorded development evidence.
This commit is contained in:
jakub
2026-10-13 22:52:53 +02:00
parent a951a96edc
commit 6a667d8deb
8104 changed files with 2124945 additions and 2061 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/migration.md
+5 -5
View File
@@ -12,13 +12,13 @@ The source review confirms that several AI helpers are already migrated (HQ radi
- `EAI_ImprovisedPrisons.c`: reuse applicable camp layout, finite starter supplies and placement ideas when expanding starts. Its `SCRTC_BaseGameMode` / `ESCT_PrisonComponent` integration must use successor services. Keep the current playable prison available while adapting it.
- `EI_IntelService.c`, `EI_IntelLifecycle.c`, `EI_MapDiscoveryUI.c` and `EI_PlayerBriefing.c`: compare inventory assignment, recovery, discovery feedback and briefing behavior with the successor. The extension README also documents an administrator reroll operation beyond the successor's current carrying/reveal settings; migrate it deliberately with its cohort, ownership and duplicate-prevention semantics.
- AI logistics, convoy and air-support implementations: adapt independently authored behavior around the successor HQ and finite physical forces. Remove original game-mode/location dependencies and keep the first release's vanilla asset scope. Source availability alone does not establish migrated or verified behavior.
- AI logistics, convoy and air-support implementations: adapt independently authored behavior around the successor HQ and finite physical forces. Remove original game-mode/location dependencies. The owner subsequently authorized RHS: Status Quo, WCS Armaments and WCS BMP-1; use the recorded external dependency/resource catalog. Source availability alone does not establish migrated or verified behavior.
Do not restart prolonged prison/input or experimental aircraft proof work merely to investigate these sources. Prioritize concrete gameplay gaps and retain explicit human and multiplayer validation limits.
## Implemented foundation
- Five projects, dependency isolation, new source resource identities and a new scenario identity.
- One combined successor project with separate Core/AI/Intel/Chat/Map classes, dependency isolation, new resource identities and a new scenario identity. Earlier evidence retains the historical five-project layout.
- 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.
@@ -50,8 +50,8 @@ Native and human validation limits for this increment are recorded in `owned-ai-
Core now owns the `/esc` command transport, native administration menu, authenticated sessions, settings and player tools in dedicated classes. AI and Intel register providers through `ERR_AdminProvider`; Core does not depend on either companion or the Chat wrapper. See [mission-owned chat administration](chat-integration.md) for supported commands and class boundaries.
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. Applicable original menu, journal and player-tool behavior is adapted; commands for deferred gameplay systems remain explicitly unavailable.
Settings live in the `mission` section of `$profile:Escapists.json`, with checked temporary writes and a shared backup. The six former Escape profile files are automatically imported on first start; see [unified configuration](configuration.md#one-server-configuration). 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. The older predecessor AI/intel files still require this explicit import tool. Its output is a legacy-format mission section: seed `rereintroduced.json` before the first unified migration, or merge those values into the existing `mission` section while the mission is stopped. Applicable original menu, journal and player-tool behavior is adapted; commands for deferred gameplay systems remain explicitly unavailable.
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.
RHS: Status Quo, WCS Armaments and WCS BMP-1 are now declared dependencies, together with Parachute Framework. Everon remains the first-release target; additional terrain experiments, complete feature parity and virtual distant units are not release-qualified. 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.
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) provides editable authored source. The separate [current development playtest handoff](playtest-build.md) also contains native runtime artifacts; its strict packaging limitations remain explicit and it is not a published or qualified release.