Check these states in order
| What you see | What to check next |
|---|---|
| Barry contains enough loot, but it has not been sent | Use the send interaction, then check delivered progress. |
| The percentage says 100, but the delivered amount is below the target | If time and conditions allow, send another small amount and check again. |
| The delivered amount meets the target, but the hatch stays closed | Treat this as a possible hatch or session fault and record the state. |
| Teammates see different progress | Compare the amount/target values each player sees; do not rely on one player’s percentage alone. |
Barry’s cart and quota gauge in an earlier interface.
Earlier quota interface shown. Your current labels may differ.
Separate a shortfall from a hatch fault
Blue progress is the load waiting in Barry; yellow progress is the amount sent. Deliveries should be counted against the quota before the hatch opens. If another delivery changes the total and opens the hatch, the team can continue without a separate manual-opening step.
If the delivered total already meets the target, a closed hatch is a different problem. Avoid spending the remaining time repeatedly searching for a switch that the normal completion flow does not require.
Record a persistent problem
Capture the amount/target display, the closed hatch, the shift, and any difference between players’ screens. Include whether the last load was actually sent. These details make a bug report more useful than a screenshot containing only a 100 percent icon.
There is no verified in-run fix that guarantees the hatch will recover. Restarting or rehosting should not be presented as a way to preserve the current run’s progress.
Related guides
Sources and version notes
Prepared from research collected on October 22, 2026. Early Access rules and availability can change. Launch information takes precedence over older beta instructions. These official links provide current product information and updates; they do not verify every gameplay tip.