System shelf
Use this page for named system lookups once the blocker is clearly scanner, power, storage, or vehicle support.
Shelf-style database
Systems should answer what problem they remove, not just what they are called.
Use this shelf when the topic is a named system and you need the shortest path to its value, timing, and next upgrade decision.
Best fit
Open this page when the system name is already known, but the value, timing, or upgrade order still feels unclear.
System entries
Use the system row that matches the friction you keep repeating.
| System | Main value | When it matters most | Best next page |
|---|---|---|---|
| Scanner Room | Reduces repeated search time | When route shape already works but scouting still wastes trips | Scanner decision |
| Storage support | Makes returns and crafting cleaner | When the base works, but hauling still turns into clutter | Storage upgrades |
| Base power | Keeps utility from collapsing mid-run | When the base exists but still feels fragile or annoying | Base power |
| Vehicle support | Turns longer routes into reliable travel | When home flow is stable enough that travel is now the real blocker | Vehicle upgrades |
Upgrade Planner
Use this when several systems all sound useful and you need the one that fixes the repeated failure first.
Base Building Center
Use this when the system question still depends on site choice, layout, or cleanup order.
System shelf notes
What this system shelf should answer before the player spends materials.
System pages are only useful when they show what problem the system removes. A shelf that only names the system without the effect still leaves the player guessing.
- Spend on the system that fixes the repeated failure first.
- Check whether the base or vehicle is already doing enough work.
- Use the smallest upgrade that solves the bottleneck.
- Spending materials on a system before knowing what broke.
- Upgrading for comfort instead of for removal of a real problem.
- Letting multiple systems compete for the same batch without a priority order.
- Open Upgrade Planner when the spend order matters most.
- Open Base Building Center if home friction is still the issue.
- Open Vehicles Center if range or depth is what actually needs fixing.
System value check
What the shelf should decide after the system name is already known.
The system shelf should help the reader decide whether the system solves the current blocker now, whether a different support page should come first, and what the next upgrade step should be if the system is worth building.
- Spend on the system that removes the biggest repeated failure.
- Check whether base or vehicle support would solve more of the problem first.
- Keep the system choice tied to the current run, not to a generic build list.
- Choosing systems by prestige instead of usefulness.
- Buying support tools before the core failure is identified.
- Letting one upgrade batch try to fix every problem at once.
- Open Upgrade Planner for the spend order.
- Open Base Building Center if home friction is still the issue.
- Open Vehicles Center if the run is now limited by range or depth.
Systems depth
What the systems shelf should explain before the reader uses it.
System pages are strongest when they name the problem they solve: storage, power, scanning, vehicles, or base timing. That keeps the shelf from becoming a list of labels without practical value.
- State the problem the system removes before the feature name.
- Point readers to the page that shows how the system changes a run.
- Keep the shelf focused on comparison and handoff, not long background.
- Explaining a system without saying why it matters now.
- Letting the page become a loose glossary entry.
- Forgetting to point toward the base or upgrade page if the system is really a planning choice.
- Open Base Building Center for build flow.
- Open Upgrade Planner when the system is tied to spending.
- Open Glossary if the term itself still needs a plain-English definition.
System shelf rule
Every system entry should say what friction it removes.
If a page cannot connect the system to a real blocker, it is not helping the reader yet. The shelf should translate feature names into practical run changes.
Storage
Use when cleanup trips are the problem.
Power
Use when the base or tool chain cannot stay online.
Scanning
Use when the player needs a better information loop.