Harden base progression and cleanup; validate finite physical resupply
This commit is contained in:
@@ -4,7 +4,7 @@ An independently authored replacement for the abandoned Escapists base mission,
|
||||
|
||||
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 optional AI, Intel, Chat and Map addons extend its interfaces. HQ coordinates enemy responses through physical radios and available forces.
|
||||
|
||||
See [current development status](docs/current-status.md) for verified checkpoints and the prioritized remaining work. Ordinary Core and companion startup now admit a real local prisoner cleanly; focused casualty-loading and physical mortar tests also pass. A later companion restart retains support-station cleanup errors. Manual gameplay, real multiplayer, complete HQ support, measured FPS improvement and release qualification remain unfinished. The [original responsibility inventory](docs/original-feature-coverage.md) is a scope map, not proof that every original behavior has been replaced.
|
||||
See [current development status](docs/current-status.md) for verified checkpoints and the prioritized remaining work. Ordinary Core and companion startup now admit a real local prisoner cleanly; focused casualty-loading and physical mortar tests also pass. The latest archived companion restart passes two rounds with diagnostics disabled after scoped station cleanup; the earlier failure remains preserved. Real-perception HQ response and destroyed-gate progression have focused native checks, with arranged/scripted movement explicitly disclosed. Manual gameplay, real multiplayer, complete HQ support, measured FPS improvement and release qualification remain unfinished. The [original responsibility inventory](docs/original-feature-coverage.md) is a scope map, not proof that every original behavior has been replaced.
|
||||
|
||||
## Projects and scenarios
|
||||
|
||||
@@ -29,4 +29,4 @@ For bounded hidden, muted local native tests, see [runtime testing](docs/runtime
|
||||
|
||||
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](docs/current-status.md) separates those gaps from demonstrated development behavior. [Validation evidence](docs/validation.md) preserves exact source checkpoints and failed iterations; `docs/acceptance.json` keeps unverified release requirements pending.
|
||||
|
||||
No release package has been published.
|
||||
The [development source bundle tool](docs/development-source-bundle.md) previews a deterministic handoff of the five editable projects 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.
|
||||
|
||||
Reference in New Issue
Block a user