Finish airborne extraction after 30 seconds and hold rescue aircraft; record Workshop 0.0.134

2026-10-31 15:01:51 +01:00
parent d21adb90d5
commit 2c2158702d
14 changed files with 981 additions and 22 deletions
@@ -40,7 +40,7 @@ Record the game/Tools versions, repository tree hash, addon list, player count,

 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.
+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 rescue helicopters and remain aboard through 30 continuous seconds of airborne evacuation. Verify statistics open and the occupied aircraft remain stable throughout the results screen. 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. 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.