Dry Run reconnect stall · Week 250–251 current-player evidence boundary
ICARUS Dry Run Drill Stuck After Reconnect: What Changed
Quick Answer
If the mission drill in ICARUS Dry Run stops progressing after a reconnect, first confirm that both the client and host are on Week 246 build 3.0.23.156115 or later. RocketWerkz identified the cause as the drill’s electricity state not updating correctly after reconnecting, which could stall the mission. Week 246 changes that state so it updates appropriately. Rejoin only after confirming the shared build, inspect the current objective and drill power state, and give the live tracker time to acknowledge the corrected state. The official note does not publish a console command, a manual wiring sequence, a guaranteed repair for a prospect already damaged on an older build, or an exact checkpoint-reset procedure. Preserve the prospect and record the build, host, objective text, power indication, and reconnect order before trying any destructive recovery.
- Reading time
- 8 minutes
- Difficulty
- Version and reconnect-state diagnosis
- Checked
- 2026-10-04
On this page
Guide details
Before you begin
Diagnose the Dry Run mission drill reconnect stall with the Week 246 electricity-state fix, without inventing reset commands or hidden triggers.
Week 246 Dry Run drill reconnect electricity-state fix; no invented power layout, reset command, save edit, hidden trigger, or guaranteed old-prospect recovery.
- Status
- Official ICARUS release evidence plus bounded exact-query review
- Edition
- Week 250–251 current-player evidence boundary
- Platform
- PC · Steam
- Checked
- 2026-10-04
- Check note
- Only the cited release facts are verified. Search volume, keyword difficulty, external SEO score, unsupported recovery methods, numeric values, and later changes remain Unknown.
Before you set out
Prerequisites#
- Use Week 246 build 3.0.23.156115 or later on both the player client and the session host.
- Identify the Dry Run mission, also named Canyon_Expedition in the official changelog, rather than applying this fix to every powered drill.
- Record the active objective and visible drill electricity state before disconnecting or changing the prospect.
- Keep the current prospect intact while diagnosing; the official source does not authorize deletion, save replacement, or a hidden reset command.
Why the Dry Run mission could stall after reconnecting#
The Week 246 release isolates a specific mission-state defect. In Dry Run, the mission drill has an electricity state that must be reflected correctly when a session reconnects. Before the fix, that state could fail to update after the reconnect, leaving the mission stalled even though the player had returned and expected the drill step to continue. The changelog names the mission internally as Canyon_Expedition and says the electricity state now updates appropriately. That is narrower than a claim that every powered device, mission drill, or connection problem was fixed. It also does not establish that the underlying power supply was always correct, that the objective must advance immediately, or that an older damaged prospect is guaranteed to repair itself. Treat version, mission identity, drill power indication, and objective state as separate checks. If the session runs an older build, the official defect is still a plausible explanation. If the current build is Week 246 or later, the supported expectation is that the electricity state survives or re-establishes correctly through reconnect; any remaining stall needs an observation rather than an invented trigger.
Route 02
Check an ICARUS Dry Run drill reconnect stall safely#
Use this order to separate the documented reconnect defect from ordinary power, version, or objective-state problems.
Confirm the mission name#
Verify that the active prospect is Dry Run. The official changelog calls it Canyon_Expedition, so keep that internal name with the visible mission name when recording evidence.
Record the live objective#
Write down the exact tracker text before changing anything. A drill step, travel step, and later objective are different states even if they occur in the same mission.
Check both running builds#
Confirm the player client and the host or dedicated server are on Week 246 build 3.0.23.156115 or later. Do not assume the client updating also updated the host.
Inspect the drill electricity indication#
Use only the visible in-game state to determine whether the drill currently shows power. The patch fixes state updating; it does not publish a universal wiring diagram for this mission.
Reconnect once under the current build#
If a reconnect is operationally necessary, do it once after the shared build is confirmed. Preserve the order of host start, player join, and drill observation so the result is reproducible.
Wait for the tracker to acknowledge state#
After joining, observe the drill and mission tracker before dismantling or replacing anything. The official fix concerns state synchronization, so immediate extra changes can hide what actually happened.
Separate no power from stale power state#
A genuinely unpowered drill and a powered drill whose state failed to update are not the same diagnosis. Record what the game shows instead of calling both a reconnect bug.
Preserve a remaining failure#
If the mission still stalls on the fixed build, save the exact build, session type, objective text, power indication, reconnect sequence, and whether the prospect began before Week 246.
Avoid unsupported resets#
Do not delete the prospect, edit saves, run an undocumented console command, or promise a hidden interaction. None of those actions appears in the cited release.
Pocket list 03
Verified Dry Run reconnect boundaries#
- Affected mission — Dry Run, identified as Canyon_Expedition in the changelog.
- Affected state — the mission drill electricity state after reconnect.
- Observed consequence — the incorrect state could stall the mission.
- Fix boundary — Week 246 build 3.0.23.156115 makes the electricity state update appropriately.
- Not established — exact wiring, coordinates, objective duration, host-only behavior, console commands, save editing, or a guaranteed old-prospect recovery.
- Search volume, keyword difficulty, and external SEO score remain Unknown.
Fault ledger
If Dry Run still does not advance#
- The host and client show different builds
- Update and restart the out-of-date side before judging the reconnect fix. A client-only update does not establish that the session host runs Week 246.
- The drill visibly has no electricity
- Treat that as a current power-state observation first. The release fixes state updating after reconnect; it does not say that the patch supplies power automatically.
- The drill shows power but the tracker is unchanged
- Preserve the fixed-build evidence, active objective wording, and reconnect sequence. Do not invent a second trigger or claim that replacing the drill is officially required.
- The prospect began before Week 246
- Note that boundary explicitly. The source confirms the software fix but does not guarantee repair of every older in-progress mission state.
- A guide recommends a console or save-file reset
- Require separate current authoritative evidence before using it. The Week 246 source publishes no such recovery method.
Field questions
Dry Run reconnect questions#
- What caused the Dry Run drill stall?
- The official Week 246 note says the drill electricity state was not updating correctly after reconnecting.
- Which version contains the fix?
- Week 246 build 3.0.23.156115-rel-DangerousHorizons is the verified boundary.
- Does reconnecting always repair an old prospect?
- That guarantee is not in the source. Confirm the build and preserve evidence if an older in-progress prospect remains stalled.
- Is there an official reset command?
- No reset command is documented in the cited release, so this guide does not provide one.
- Does this fix every ICARUS drill?
- The saved evidence is specific to the Dry Run mission drill and its reconnect electricity state.