Lost & Found

What the Evidence Confirms

The supplied GRAIN ROT material confirms an extraction loop where carried resources and equipment can be placed at risk when a run fails. It also supports storing valuable gear at the Outpost before a dangerous or experimental descent. These facts make prevention and careful post-run checking important.

The evidence does not confirm a named automatic “Lost and Found” system that reliably returns missing equipment. This guide therefore separates supported recovery steps from assumptions. It can help you check normal locations, identify a synchronization problem, and prepare a useful bug report, but it cannot promise that an item lost during a failed run will reappear.

What Is Not Yet Verified

No supplied source establishes a universal recovery box, fixed return timer, guaranteed insurance system, or exact rule for every disconnect and multiplayer state. Community descriptions may refer to a different version, demo, save, or unrelated game.

When evaluating a claim, ask:

• Does it apply to the full current release or an older demo?
• Is the item carried, stored, dropped, or attached to a vessel?
• Did the run end normally, through death, or through a disconnect?
• Was the player hosting or joining multiplayer?
• Can the result be repeated with a low-value item?

These details change the problem. Without them, “my item disappeared” does not identify a single mechanic.

Preventing Equipment Loss

Prevention is the strongest recovery strategy. Store rare tools before testing new routes, controls, or systems. Carry only equipment required by the run goal, power the elevator early, and extract after the valuable tool has completed its purpose.

Use a simple equipment plan:

1. Name every rare item entering the layer.
2. Assign who carries it and why.
3. Decide when that item makes extraction mandatory.
4. Avoid putting all critical gear on one fragile vessel.
5. Return optional equipment to storage before the next experiment.

In co-op, announce transfers and drops. An item may appear missing because another player carried it, placed it near salvage, or stored it in a different normal location.

Checking the Outpost After a Run

After equipment appears missing, slow down and check the ordinary state first. Review the player inventory, equipped slots, storage, relevant room, shop or preparation area, and any normal place where the team moved items before descending. Ask teammates to check their inventories and storage as well.

If a vessel broke but the run continued through Spark possession, distinguish the old vessel location from the new body’s inventory. Possession recovery and equipment transfer should not be assumed to be the same system. Return to the previous location only when the route is safe and the item’s value justifies another risk.

Avoid changing many things while investigating. Buying replacements, moving storage, reconnecting several times, and starting another run can erase useful evidence about the original state.

Responding to Missing Gear

Use an evidence-first sequence:

• Confirm the exact item name and last known location.
• Check every normal inventory and storage location.
• Ask each teammate whether they moved or carried it.
• Note whether the expedition extracted, failed, or disconnected.
• Record whether the player changed vessels.
• Confirm the game version and whether the save is from the full release or demo.

If the item remains missing, decide whether recovery is supported by current in-game information. Do not repeatedly enter danger searching for an object when the run state suggests it was lost normally.

Multiplayer and Synchronization Checks

Multiplayer introduces host and client state. One player may see an item in a different place, or a transfer may not appear as expected after a connection problem. Ask all players to check the same location and describe what they see before restarting.

Record who hosted, who carried the item, when the connection changed, and whether the team extracted. If a safe reconnect is attempted, check the normal locations again before moving other equipment. The supplied evidence does not guarantee that reconnecting restores items, so describe it as diagnosis rather than a fix.

When the issue occurs repeatedly, reproduce it with inexpensive equipment. Use the same transfer, vessel change, or disconnect sequence and stop as soon as the result is known.

Distinguishing Loss from a Bug

Normal loss is plausible when valuable gear was carried into a failed run, left behind during extraction, or abandoned with a broken vessel. A bug becomes more plausible when stored equipment disappears without a run, different players see contradictory state, or the same controlled action repeatedly removes an item against current game feedback.

Do not label every confusing result a bug. First eliminate normal storage, teammate transfer, and version mismatch. Equally, do not invent a hidden Lost and Found mechanic to explain a real defect. Use only what the game and reproducible evidence show.

Reporting a Possible Bug

A useful report includes the item, game version, full-release or demo state, solo or multiplayer status, host, vessel state, last known location, expedition outcome, and exact reproduction steps. Add screenshots or video when they show the inventory before and after.

Use a concise sequence:

1. Start with the item in a known normal location.
2. Perform the smallest action that causes the loss.
3. Check inventories and storage without other changes.
4. Repeat once with a low-value item if safe.
5. Send the evidence through an official or supported community channel.

Avoid including account secrets, unrelated logs, or guesses presented as facts.

Planning Around Uncertain Recovery

Until the game clearly confirms a recovery rule, plan as though carried rare equipment can be permanently lost. This conservative assumption improves extraction decisions without claiming that every loss is intended.

Build replaceable loadouts, keep a recovery reserve, and use valuable gear only when it solves a specific problem. If an item is important enough to change the next several runs, it is important enough to trigger an early extraction.

Equipment Recovery Checklist

• Check inventory, equipped slots, storage, and normal Outpost locations.
• Ask teammates about transfers and carried items.
• Separate vessel recovery from item recovery.
• Record run outcome, connection state, and game version.
• Do not rely on an unverified automatic Lost and Found system.
• Reproduce only with inexpensive equipment.
• Report a repeatable issue with a clear timeline.

Lost and Found FAQ

Is there an automatic Lost and Found system?

The supplied evidence does not confirm a named automatic system that reliably returns missing equipment.

Can I recover gear after my vessel breaks?

Possibly, depending on where the item remains and whether the route is safe, but Spark possession does not by itself prove that carried gear transfers.

What should I check first?

Check normal inventory, equipped slots, storage, relevant Outpost locations, and teammate inventories before changing the game state further.

When should I report a bug?

Report one when normal explanations are eliminated and a controlled sequence repeatedly produces the same unexpected loss. Include version, multiplayer state, item, location, and reproduction steps.