Quick answerTreat every loot run as a risk budget: search high-signal containers first, leave when your pack is full or a hazard escalates, and log what you actually found by version. The screenshots are authorized community assets, not proof of universal drop rates.

Media: user-provided authorized asset pack · Community demonstration. This image supports context, not every mechanic described on the page.
Field notes
- Plan a small route and a return point before entering a ruin.
- Prioritize supplies that support the next run, not only valuable-looking items.
- Capture unusual finds with the location and version.
- Keep a personal ledger instead of publishing fixed drop-rate claims.
Evidence boundary
| Evidence level | Authorized community demonstration imagery; loot behavior remains to be independently verified. |
| Safe wording | Use “found in this demonstration” rather than “always spawns”. |
Questions players ask
Is there a confirmed loot table?
Not yet in this starter build. We will add tables only from repeatable evidence.
How do I avoid overloading?
Reserve space for higher-value or mission-relevant items and return before the pack becomes a liability.

