- Pick the vehicle that removes the repeated travel failure.
- Do not upgrade a vehicle before the base is steady if the base is still the real problem.
- Use vehicle support to extend the run, not to replace route planning.
Shelf-style database
Vehicle pages should answer what kind of travel blocker they fix.
Use this shelf when the vehicle topic is named and the real question is range, depth, upgrade order, or whether vehicles should come before more base work.
Vehicle entries
Use the row that matches the travel problem.
| Vehicle topic | Main value | When it matters most | Best next page |
|---|---|---|---|
| Base or vehicle first | Stops wasteful upgrade timing | When home flow still might beat range as the real blocker | Base or vehicle first |
| Vehicle upgrades | Improves repeated route distance | When the route already works but still feels too long | Vehicle upgrades |
| Depth support | Protects deeper pushes from premature upgrades | When the next move looks deeper than the current loadout supports | Depth upgrade check |
Vehicle shelf notes
What this vehicle shelf should answer before you leave.
Vehicle pages are most useful when they explain which travel problem the vehicle actually removes. A good shelf should tell you whether the run needs range, depth, or a cleaner return trip.
- Choosing a vehicle because it looks powerful instead of because it fixes a blocker.
- Mixing depth support and route distance in one decision.
- Upgrading before the current travel loop is already working well.
- Open Vehicles Center for the broader vehicle decision.
- Open Upgrade Planner when the next spend is the real decision.
- Open Map if travel safety, not vehicle power, is the blocker.
Vehicle value check
What the shelf should decide after the name is already known.
When the vehicle topic is already clear, the shelf should answer whether the vehicle is worth the spend now, whether the route still needs cleanup first, and what the next support step should be.
- Use the vehicle that makes the current route safer or shorter.
- Prefer one support answer over three partial upgrades.
- Return to base or route planning if the vehicle is not the main blocker.
- Assuming every travel problem needs a vehicle fix.
- Ignoring route safety when the trip still feels unreliable.
- Upgrading before the run has told you what is actually failing.
- Open Route Planner if the trip shape is still unclear.
- Open Base Building Center if the home loop still needs work.
- Open Vehicle upgrades if the vehicle itself is the answer.
Vehicles database depth
What the vehicle shelf should clarify before the player invests again.
Vehicle pages should say what travel problem the machine solves, how far it can go, and whether the next step is an upgrade or a different route. That turns a vehicle from a name into a useful choice.
- Use vehicles for distance, depth, or safer return timing.
- Compare the current travel blocker against the vehicle role.
- Move to the upgrade page when the machine already fits the task.
- Treating every vehicle as a universal fix.
- Spending on travel before the route problem is clear.
- Ignoring the depth or range rule that decides whether the vehicle helps at all.
- Open Vehicles Center for the fuller comparison view.
- Open Upgrade Planner when the next vehicle step is a better part.
- Open Route Planner when the machine choice depends on the trip.
Vehicle shelf triage
How to tell whether the vehicle is the real answer.
A vehicle page is low-value if it only says the vehicle exists. It becomes useful when it tells the player whether range, depth, storage, safety, or base friction is the actual blocker.
| Travel problem | Likely answer | Open next |
|---|---|---|
| The route is unsafe even with enough range | Fix the path, not the vehicle | Route Planner |
| The route stops at a depth wall | Compare depth support | Depth upgrade check |
| Trips are safe but too short | Plan vehicle range or storage support | Vehicle upgrades |
| Every trip ends at home cleanup | Fix base flow before upgrading travel | Base Building Center |