How to Fish Disappearing Guns and Items: Safe Response
Updated 2026-08-25
Reduce the chance of losing loose gear, distinguish inventory loss from physics movement, and document item disappearance without overwriting your save.
Identify which kind of loss occurred
Launch-week players report several different symptoms under the phrase 'items disappeared': ground objects gone after exit, equipped or inventory weapons absent after loading, items falling slowly and becoming unusable in multiplayer, and loss following death or a crash. These may not share one cause. Record whether the item was equipped, in inventory, stored, held by another player or loose in the world. That classification determines the safest next check.
Search before saving again
Pause normal play and inspect the boat, storage, hotbar, inventory pages and the ground near the last interaction. Physics can move an object downhill, into water, below another body or away from an explosion. Ask co-op players whether they see or hold it. Do not buy a replacement or create a new pile until you know the current state, because more objects make the timeline harder to reconstruct.
Protect valuable equipment
Keep upgraded weapons in assigned inventory or hotbar slots instead of leaving them loose between sessions. Sell or discard low-value clutter so essential gear is visually obvious. Before using Save, Main Menu or Quit, verify every protected slot. The official patch notes describe updated save behavior, but no guide can promise that every physics object persists. Treat the world floor as temporary unless the game explicitly demonstrates otherwise.
Handle co-op desync
If one player sees the item and another does not, let the host control the next step. Avoid both players grabbing, throwing or selling the same object. Save only after the group agrees on the visible state. If the object falls slowly, cannot be picked up or shows another player's appearance, record host/client roles and connection state. Recreate the issue with an expendable item before risking upgraded gear.
Recover without compounding damage
Follow the save-protection checklist: preserve the current file, check the installed patch, and perform only one deliberate reload after recording the state. Verification of game files may repair code but cannot guarantee an item returns. Do not install inventory editors or unknown save downloads. If a valuable item remains absent, report item type, location, last interaction, session role, exit type and build through an official developer channel.
Use a prevention routine
End each session at a stable location, collect loose equipment, confirm inventory, save through the menu, wait, then exit normally. After a crash, check state before saving. In co-op, keep one owner per expensive item and avoid passing it during lag. This routine does not prove the bug is solved; it limits ambiguity and gives developers a reproducible sequence if loss occurs again.
How to apply this guide safely
Begin with “Identify which kind of loss occurred” and compare it with the objective, inventory, and controls shown by your installed build. Do not change several variables at once. If the guide concerns progression, complete one dialogue or hand-in and confirm the objective changed before sailing away. If it concerns combat, test the control or equipment choice on an ordinary encounter before spending a boss trigger. If it concerns troubleshooting, preserve the save and start with reversible checks such as restarting the session and verifying files.
Keep a short run record with the game version, solo or co-op state, host identity, starting objective, relevant equipment, steps taken, and outcome. Physics, network state, and retail patches can make two attempts look different even when both players describe them honestly. A controlled record lets you identify which condition changed. It also gives the developer a useful reproduction if the result points to a defect rather than a missed quest step.
Evidence and version check
This article uses Steam Community Hub — official announcements, Steam Discussion — saved game and lost items. Official store text and developer announcements establish supported features and broad progression. Steam achievement wording establishes that a named action exists, but it does not prove an exact coordinate, probability, price, damage value, or hidden timer. Community discussions can reveal a repeated problem and possible workaround, but one reply is not treated as a universal mechanic. Where evidence stops, the guide uses cautious testing steps instead of inventing a precise answer.
Before relying on an older route, check the Steam news and discussion dates against the updated date at the top of this page. Prefer the current in-game objective when it conflicts with a video or forum post. Avoid unknown executables, replacement saves, cheats, or destructive file edits offered as shortcuts. A legitimate workaround should be explainable, reversible, and testable without surrendering account credentials or deleting the only known-good save.
Completion check
Finish with “Use a prevention routine,” then verify the result in the system that matters: quest log for progression, inventory for items, Steam for achievements, or a repeatable symptom check for a technical fix. Do not treat a visual animation alone as proof that the save registered the event. Wait for a normal transition and inspect the state before selling items, changing hosts, or starting another objective. If the result differs from this page, send the URL, build number, exact steps, and observed result through the contact page; that evidence is how we correct guides without turning uncertain reports into false facts.
Sources & Evidence
Claims are backed by the following sources. Unknowns are marked explicitly.
- Steam Community Hub — official announcementsOfficial / Tier 1Checked 2026-08-25
- Steam Discussion — saved game and lost itemsCommunity / Tier 2-3Checked 2026-08-25