What the sources establish
The 8 October plan distinguishes blue loaded loot from yellow sent contributions, adds Amount / Quota, and announces an exit hatch that opens when the quota is met.
Developer update · 8 Oct 2026 ↗Sourced details and our suggested next steps follow. Linked reports are observations, not verified fixes.
01 Read the labels, not just the colour
Read the actual Amount / Quota values and distinguish sent contribution from loot still loaded. The public bug board has a player report about a display reaching 100% before the full amount is met. That report is not a confirmed diagnosis of your run. If the amount is short, record the difference; if it meets the target but the hatch stays closed, record both states.
Developer-linked player reports · Checked 23 Oct 2026 ↗02 Use a two-step team callout
Try ‘contribution checked’ followed by ‘exit located’. Keeping the two calls separate stops a teammate from hearing ‘done’ and assuming every remaining step is already resolved. This is an editorial coordination method, not a required game command.
03 Choose who confirms the transition
One person reads the objective state; another confirms where the group is going. For a small team, one person can cover both. The benefit comes from saying the decision clearly, not from creating permanent roles or assuming an optimal team size.
04 If the exit does not behave as expected
Record the current objective display, the build, and what the hatch actually does. Compare those observations with the dated announcement. Do not keep repeating a beta interaction just because it appears in an older walkthrough. Use the official bug-report route if the current behaviour appears inconsistent.
Limits of this guide
No fixed quota value, hatch-opening delay, gas countdown or guaranteed escape window is documented here.