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

Make the base escape mission independent and add native objectives

Browse Source
This commit is contained in:
jakub
2026-09-19 02:03:52 +02:00
parent 7a507a7371
commit 92fd23f274
54 changed files with 5271 additions and 52 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+4 -2
View File
@@ -2,7 +2,9 @@
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**.
Five independently identified Workbench projects live in `addons/core`, `addons/ai`, `addons/intel`, `addons/chat` and `addons/map`. Open `addons/chat/addon.gproj` to load the full development scenario and its companion addons. 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 primary deliverable is the rewritten base mission; companion migration follows it. See [base replacement responsibilities and gaps](docs/base-replacement.md).
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.
Run the background checks with Python 3 and a C++17 compiler:
@@ -12,7 +14,7 @@ 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.
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 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.
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.