escapists/EscapistsReintroduced
1
0
Fork 1
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Decouple base configuration and administration from companions

Browse Source
This commit is contained in:
jakub
2026-09-19 03:15:33 +02:00
parent 35daefa860
commit ce19ec68df
96 changed files with 9200 additions and 171 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+20 -11
View File
@@ -1,23 +1,32 @@
# Escapists Rereintroduced
Independent successor prototype for Arma Reforger, initially targeting vanilla Everon and up to 12 players. This repository is separate from the existing Escapists workspace. It is **not a completed or release-ready replacement**.
An independently authored replacement for the abandoned Escapists base mission, initially targeting vanilla Everon and up to twelve players. This is a separate repository and **not a completed or release-ready replacement**. The base rewrite is the primary deliverable; companion migration supports it.
The primary deliverable is the rewritten base mission; companion migration follows it. See [base replacement responsibilities and gaps](docs/base-replacement.md).
The current base supplies prison spawning, finite scavenging stock, physical radio documents, discovered map markers, native objectives, continuous radio defence, helicopter escape, defeat/restart, identity-based lives and local spectator following. Authored site definitions and an injected vanilla faction/asset catalog own the initial physical population. Core provides administration and startup diagnostics; the optional AI, Intel, Chat and Map addons extend its interfaces. HQ coordinates enemy responses through physical radios and available forces.
Five independently identified Workbench projects live in `addons/core`, `addons/ai`, `addons/intel`, `addons/chat` and `addons/map`. Open `addons/core/addon.gproj` for the independent base scenario (`Missions/ERR_Everon_Base.conf`), or `addons/chat/addon.gproj` for the full companion integration scenario. Core owns essential document recovery and objective markers; companions enhance the base. The only external addon dependency is vanilla Arma Reforger. Required successor source resources are local to this repository; vanilla assets are referenced, not redistributed.
The [original responsibility inventory](docs/original-feature-coverage.md) tracks all 299 original script entries across 18 unfinished areas. It is a filename-based coverage map, not proof of behavioral equivalence. Additional mission content, full support/logistics, manual gameplay, multiplayer, performance and release qualification remain unfinished. Native vehicle-resource errors and intermittent inherited catalog cleanup errors also remain.
Run the background checks with Python 3 and a C++17 compiler:
## Projects and scenarios
Five Workbench projects live in `addons/core`, `addons/ai`, `addons/intel`, `addons/chat` and `addons/map`:
- Open `addons/core/addon.gproj` for the independent base scenario, `{AD62322D5213C440}Missions/ERR_Everon_Base.conf`.
- Open `addons/chat/addon.gproj` for full companion integration, `{C1E20667DCE324ED}Missions/ERR_Everon.conf`.
Both use the newly authored Everon child world. The only external addon dependency is vanilla Arma Reforger. All required successor resources are inside this repository. Vanilla assets are referenced, not redistributed; original restricted Escapists code, compositions, UI and audio are not included.
See [configuration and commands](docs/configuration.md), [site authoring](docs/site-authoring.md), [architecture](docs/architecture.md) and [migration priorities](docs/base-replacement.md).
## Validation
Run source/resource isolation and production-policy regressions with Python 3 and a C++17 compiler:
```sh
python3 tools/check.py
```
These check the dependency graph, resource identities and isolated production policy functions. They do not replace Enfusion compilation or multiplayer testing.
For bounded hidden, muted local native tests, see [runtime testing](docs/runtime-testing.md). The Core-only fixture completes two escape/restart rounds with 102 assertions, including catalog injection, administration, finite inventory, objectives and unconsciousness/recovery. The full companion fixture completes two rounds with 96 assertions, including the existing HQ/Intel command aliases. A separate deliberate startup-failure fixture verifies that no population spawns and the mission cannot advance after invalid setup.
The development scenario is `{C1E20667DCE324ED}Missions/ERR_Everon.conf`. Its world is `{B6C516F86302C679}Worlds/ERR_Everon.ent`. Local Workbench tests now compile the successor and complete a scripted prison → carried documents → interrupted radio defence → physical helicopter occupancy → victory sequence. This exercises mission transitions and native systems; the test teleports the character and helicopter and does not prove a manually playable escape, multiplayer correctness or improved FPS. The enclosure was moved to a surveyed clear site, its gate passes a native passage check, and both victory and helicopter-loss defeat repeat across round restart. Native vehicle-resource errors, manual gameplay validation, full support controllers and multiplayer validation still need work. A separate scripted test now covers actual character death, local spectator activation, all-dead defeat and restart. The Core-only fixture completes two rounds with 38 assertions, including native objectives and radio progress, while all four companions are unloaded.
These fixtures teleport actors and the helicopter and manipulate native controller states. They do not prove manual escape/piloting, medical treatment, real remote reconnects, twelve-player correctness or improved FPS. [Validation evidence](docs/validation.md) preserves failed iterations and remaining engine errors. `docs/acceptance.json` keeps unverified release requirements pending.
See [architecture](docs/architecture.md), [migration status](docs/migration.md), [runtime testing](docs/runtime-testing.md) and [validation evidence](docs/validation.md). The acceptance ledger in `docs/acceptance.json` deliberately keeps unverified requirements pending.
No release package has been published. No licence has been assigned to third-party material. The original restricted Escapists implementation and mission compositions are not included.
The current base uses four authored site definitions and finite physical stock, including a separate supply cache. Mandatory documents target the radio explicitly. Core-only tests complete two rounds with 62 assertions covering stock loading, invalid definitions, cache depletion/loss, objectives and restart. See [site authoring](docs/site-authoring.md). These remain scripted checks; manual and multiplayer acceptance is pending.
No release package has been published.