Workshop return bug · Week 250–251 current-player evidence boundary
ICARUS Workshop Items Missing After Return: Week 240 Fix
Quick Answer
ICARUS Week 240 fixed one reproduced cause of Workshop or Meta items disappearing while being sent back to space. The documented trigger required multiple characters on the same prospect: one character brought the Workshop item down, while another character returned it through an Exotic Delivery Pod or Dropship. In that case, the item could be silently deleted from both the prospect and the space loadout. The Week 240 fix is intended to make returned items reach their destination. Confirm that every participating client and server is current, identify which character deployed and returned the item, and then inspect both the prospect and space loadout before diagnosing a new failure. The official update does not promise automatic restoration of items lost before the patch, compensation, a recovery command, or a fix for every unrelated missing-item cause.
- Reading time
- 8 minutes
- Difficulty
- Identity and inventory-state diagnosis
- Checked
- 2026-10-02
On this page
Guide details
Before you begin
Diagnose the documented multi-character Workshop-item return bug, understand what Week 240 fixed, and avoid claiming that every missing item is automatically recoverable.
Week 240 multi-character return-loss case and verification steps; no invented restoration, compensation, insurance, support result, or universal cause.
- Status
- Official ICARUS Week 240 evidence plus exact Bing gap review
- Edition
- Week 250–251 current-player evidence boundary
- Platform
- PC · Steam
- Checked
- 2026-10-02
- Check note
- Only facts stated in the cited Week 240 update are treated as verified. Search volume, keyword difficulty, external SEO score, unsupported values, and later changes remain Unknown.
Before you set out
Prerequisites#
- Use Week 240, build 3.0.18.154111, or later on every relevant client and host.
- Identify the character that originally brought the Workshop item into the prospect.
- Identify the character and return method used to send the item back to space.
- Preserve screenshots or notes of the item, character, prospect, return method, and current inventory state before repeating the action.
The exact Workshop-item loss case Week 240 fixed#
The official release does not say that every missing Workshop item had one cause. It describes a specific reproduced scenario found after player reports: a single player had multiple characters on the same prospect, one character brought a Workshop item down, and another character returned that item through an Exotic Delivery Pod or Dropship. Under those conditions, the item had a chance to be silently deleted in transit, disappearing from both the prospect and the space loadout. Week 240 corrects that case so returned items reach their destination. Keeping the scope exact matters. A missing item can also involve an item left in a world, a failed or incomplete objective, a mismatched server version, a different inventory, a return action that never completed, or a later defect. None of those is proven by this release note. Likewise, “fixed” does not mean an item lost before the patch is automatically restored. Diagnose identity, version, location, and return method before making a recovery or compensation claim. “Same prospect” is also part of the scope: this was not described as an account-wide disappearance during ordinary Workshop browsing. Preserve the return screen and the item’s last confirmed location when possible, because those observations separate a completed transit failure from an item that never entered the return path.
Route 02
Verify a Workshop item return without repeating the loss#
Collect the state once, check both endpoints, and separate the fixed multi-character case from other inventory paths.
Confirm all versions first#
Record the client and host build. The verified fix begins at Week 240; a mixed or older dedicated server cannot be assumed to have the corrected behavior.
Name the original deploying character#
Identify which character placed the Workshop item into the prospect loadout. This is the first half of the documented multi-character trigger.
Name the returning character#
Identify which character used the Dropship or Exotic Delivery Pod. If it differs from the deploying character, the incident matches the identity pattern addressed by Week 240.
Record the exact return method#
Distinguish a Dropship return from an Exotic Delivery Pod and from leaving an item in storage. The official case concerns an actual return action through one of those two paths.
Check the prospect state once#
Inspect the relevant character, container, pod, Dropship, and nearby storage without repeatedly triggering transfers. Confirm whether the item is still physically present.
Check the space loadout#
Return to the appropriate Workshop or loadout interface and look for the exact item. Do not confuse a similar item, insurance state, or another character’s equipment with the returned instance.
Compare against the fix boundary#
If the incident occurred before Week 240, the update can explain the cause but does not prove retroactive restoration. If it occurred after, preserve the full version and identity sequence as a possible new report.
Avoid risky reproduction#
Do not send another valuable item through the same sequence merely to test a theory. Use a low-value case only if the live game explicitly supports it and you accept the risk.
Report only observed state#
When escalating, state the item, characters, prospect, method, version, and two checked locations. Avoid claiming deletion, recovery, or compensation until those facts are actually observed.
Pocket list 03
What the Week 240 fix does and does not prove#
- The documented item class is Workshop or Meta equipment.
- The reproduced case uses multiple characters on the same prospect.
- One character brings the item down and another returns it.
- The return path can be an Exotic Delivery Pod or Dropship.
- The bug could remove the item from both prospect and space loadout.
- Week 240 fixes that reproduced transit case.
- Automatic restoration of pre-patch losses is not stated.
- Compensation, insurance behavior, support response, and a recovery command are not stated.
- Other missing-item causes are not automatically covered by this one fix.
Fault ledger
If a Workshop item still appears missing#
- A different character returned the item
- Confirm Week 240 or later on all sides and record both character identities. That is the exact trigger pattern addressed by the official fix.
- The item is absent from the space loadout
- Check whether the return action completed, then inspect the prospect inventory, pod, Dropship, containers, and the correct character before concluding it was deleted.
- The incident happened before Week 240
- Treat the update as cause evidence, not a recovery receipt. The release does not state that previously lost items are restored automatically.
- The incident happened after Week 240
- Preserve the exact build, host version, item, characters, prospect, timestamps, and return method. It may be a different path or a regression and should not be collapsed into the old case.
- Only one character was involved
- The documented reproduction does not cover that sequence. Check other inventory locations and current support guidance rather than claiming the same bug.
- You want to repeat the transfer to prove it
- Do not risk another valuable Workshop item. The official fix already establishes the old trigger; a new incident needs careful state capture, not repeated loss attempts.
Field questions
ICARUS Workshop items return questions#
- What exactly caused the documented deletion?
- One character brought a Workshop item down and another character on the same prospect returned it through a Dropship or Exotic Delivery Pod.
- What did Week 240 change?
- It fixed that reproduced case so returned items should reach their destination instead of being silently removed from both locations.
- Will the patch restore an item already lost?
- The official post does not promise retroactive restoration, compensation, or an automatic recovery process.
- Does every missing Workshop item come from this bug?
- No. The release documents one cause. Version mismatch, location, incomplete return state, and unrelated defects require separate evidence.
- Should I test with another valuable item?
- No. Verify version and existing state first, and avoid risking another item solely to reproduce a historical bug.