Merge owned systems into one addon while preserving resource identities. Gate player admission on the replicated prison scene, restore the original framed door, and hold enemy AI until escape. Correct scenario branding and author metadata, include publishing assets, and retain regression and native verification evidence.
Escapists Reintroduced
Author: Jakub Jim Žáček.
An independently authored replacement for the abandoned Escapists base mission, targeting 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 current base supplies prison spawning, two independent scavenging/clue routes, finite medical and outpost stock, an optional ground vehicle, physical radio documents, named discovery markers, native objectives, a separate radio-defence service, capacity-checked helicopter extraction, identity-based partial results, early helicopter-loss defeat, saved mission time/speed, 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 AI, Intel, Chat and Map modules extend its interfaces inside one addon. HQ coordinates enemy responses through physical radios and available forces.
The local development playtest handoff contains the earlier 5e74269 checkpoint: five native addon packages, matching source and separate manual launch scripts. It does not contain the newer HQ memory or RHS/WCS/BMP integration. Two scripted Core escape/restart rounds pass616 assertions; packaged Core and full-companion startup both pass. Full human completion and multiplayer remain to be tested.
The AI migration checkpoint adds delivered-report memory, bounded trajectory prediction, physical infantry pursuit, status checks, body observations and finite equipment. Native memory and actual-sighting response fixtures pass their assertions, with four retained upstream localization errors. See current development status for source-bound checkpoints. The earlier five-addon checkpoint shows the real prisoner view and starting objective. Native tests cover scripted escape/restart, finite mortar support, physical radio delivery, shared-map ownership, and the reusable aircraft controller's vertical flight, airborne cancellation and an isolated 20 m fixed route. Archived five-addon packages pass ordinary Chat startup without loose successor source and compile/prepare the empty mission on an isolated Linux server. The latter retains four installed-asset errors reproduced by a vanilla control.
Native game-over now stops successor services and queued preparation before vanilla restart; unknown personal results use neutral wording. Two-round preparation/active-end regressions pass at their archived source checkpoint. Current Core/companion escape/restart and ordinary startup also pass after the guidance and route changes; the ordinary read-only sampler is separate from player-input acceptance.
Later ordinary input checks demonstrate walking, clean inventory interaction and selecting the original prison lock. Automated held-action testing and experimental AI aircraft work are paused in favor of concrete base gameplay bugs and a playable development build. The complete player-controlled escape, real multiplayer, operational HQ aircraft routes and measured FPS improvement remain unfinished. Native packaging still produces UI shutdown errors also reproduced by an empty-addon control; successful packed startup does not qualify that build process. All seventeen first-release acceptance cases remain pending. The original responsibility inventory tracks the unfinished scope.
Workbench project and scenario
Open addons/core/addon.gproj, titled Escapists Reintroduced. This is the
single project to develop, package and eventually publish as one Workshop mod.
Use Missions/ERR_Everon.conf ({C1E20667DCE324ED}) for the full scenario.
The Core directory and addon GUID 2528466DE220D91C are retained for continuity.
Scripts are organized under addons/core/Scripts/Game/ERR/:
00_Core: mission, players, settings and administration10_AI: HQ, patrols, logistics and support20_Intel: enemy documents and discovery feedback30_Map: shared field map40_Chat: command integration and full-scenario test fixtures
The prefixes preserve Enforce script extension order. All modules load together. Resources retain their existing paths and GUIDs within the combined project.
Register only this project and its external dependencies in Workbench. Remove stale AI/Intel/Map/Chat project entries if you previously added them. RHS: Status Quo, WCS Armaments and WCS BMP-1 (including their dependencies) remain separate, author-supplied mods; see external dependencies. Their assets are referenced, never redistributed.
See the single-mod migration and current commands. Earlier five-addon build reports below are historical evidence, not validation of the merged project. Nothing has been published to Workshop.
See the player route playtest guide, player lifecycle, manual gameplay gaps, release qualification, performance comparison tooling, configuration and commands, site authoring, architecture and migration priorities.
Validation
Run source/resource isolation and production-policy regressions with Python 3 and a C++17 compiler:
python3 tools/check.py
For bounded hidden, muted local native tests, see runtime testing. Recorded Workbench checkpoints include Core-only and companion-loaded escape/restart, finite stock and document-loss recovery, twelve physical prisoner/seat fixtures, real medical treatment, local result/objective widgets, patrol movement and HQ preemption/resumption. Clean environment/restart evidence exists after narrowing the vanilla vehicle catalogs; it does not qualify subsequent source changes.
These scripted local fixtures manipulate positions and selected native states. They do not establish manual escape/piloting, real remote reconnects, twelve connected players or improved FPS. Separate regular-game runs establish standalone startup/admission; an isolated native Linux run establishes empty-server preparation, with inherited resource errors reproduced by a vanilla control. Current status separates those gaps from demonstrated development behavior. Validation evidence preserves exact source checkpoints and failed iterations; docs/acceptance.json keeps unverified release requirements pending.
The development source bundle tool previews a deterministic handoff of the single editable project and writes only an explicitly requested new ZIP. It is DEVELOPMENT SOURCE BUNDLE, not a native .pak or qualified release; release-mode requests remain blocked by pending acceptance. No release package has been published.