Harden participant and map ownership and validate bounded physical flight

This commit is contained in:
2026-09-19 12:17:01 +02:00
parent dfd7cc49e2
commit 4125018d04
120 changed files with 20043 additions and 47 deletions
+3 -1
View File
@@ -18,12 +18,14 @@ The command-line conventions follow the [official startup parameter documentatio
## Acceptance sessions
Use the [player route playtest guide](player-route.md) for the intended normal-input sequence. It is derived from source and is not a record of a completed manual run. Packed Core and five-addon Chat each have artifact-bound ordinary startup evidence; this does not resolve the baseline packaging UI shutdown errors or qualify later source changes. See [current status](current-status.md) and the [packaging control](native-packaging-control.md).
Record the game/Tools versions, repository tree hash, addon list, player count, AI/vehicle counts, settings, map positions and complete logs for every run. Start from an isolated profile.
1. Join with 1, 2 and 12 players; verify one controlled prisoner each. Join late during every phase. Reconnect with the same identity both within and after native reconnect reservation expiry. Voluntary departure must not create a free extra life. Test reused transient player IDs.
2. Test conscious, unconscious, revived and dead players; forbidden respawn requests; spectators; nobody connected; all survivors dead; partial extraction; defeat; restart. Voluntary reconnect reservation and spectator following are implemented; actual remote-client verification remains required.
3. Pick the prison lock, leave the enclosure, scavenge physical folders, reveal/identify the radio, hold its area for the full continuous defence period, locate the helicopter and cross the escape boundary aboard it. Test every interrupted stage and a destroyed extraction vehicle. Check that moving or collecting objective objects cannot move the objective.
4. Observe a player, interrupt a radio hop, remove/capture a relay, let a contact expire, lose a support group and deplete support ammunition. Verify orders reach only existing forces, are not duplicated and do not use undelivered knowledge. Aircraft/mortar/logistics cases remain blocked until their controllers are migrated.
4. Observe a player, interrupt a radio hop, remove/capture a relay, let a contact expire, lose a support group and deplete support ammunition. Verify orders reach only existing forces, are not duplicated and do not use undelivered knowledge. Current native snapshots pass refreshed full-salvo firing (55 assertions), stale-report expiry (48), finite courier delivery, and an isolated vertical-flight mechanism (81); [current status](current-status.md) links their exact evidence. Operational HQ aircraft routes, broader loss cases and manual/multiplayer support acceptance remain pending.
5. Repeat restarts and long empty/occupied server periods. Compare entity, AI group, callback, waypoint, inventory and journal counts. Check JIP marker state and shared-map ownership/visibility.
## Performance