Auto Explore and Auto Repair Guide

Map automation becomes useful only when it makes a complete trip observable: choose a destination class, define when the machine should leave, provide room for the result, and watch one full visit before letting the route run alone.

This guide uses the behavior reviewed through v1.0.8. If your version is older, update before treating a skip, jitter, or early departure as a layout problem.

Set up one measurable route

1. Confirm the automation controls are unlocked. These controls belong to later progression. Use the current Augment tree as the authority for their node and cost rather than an old screenshot or remembered value.
2. Choose one purpose. Start with either resource collection or infrastructure repair. Mixing every destination and repair option makes an unexpected stop difficult to diagnose.
3. Select a leave condition intentionally. If METAL AND BIOMASS EXHAUSTED is selected, the current behavior should wait for both resource categories rather than leaving as soon as only one is empty.
4. Provide working capacity. Leave inventory or storage room for the item or resource you expect. A correct route cannot make a full destination accept more output.
5. Watch a complete visit. Confirm travel begins, the selected POI is reached, work actually starts, and the chosen leave condition becomes true before the next destination is selected.

Use the connection diagnostic when the route arrives correctly but a Harvester, Salvager, Grabber, or storage chain does not do its job.

Auto Repair needs a different success check

Auto Repair is not complete when the machine merely reaches a Reactor. The current route should remain there while the repair runs, then evaluate energy and Biomass after the repair finishes.

A safe test is:

1. turn off unrelated POI destinations;
2. enable only the repair target you want to observe;
3. begin with enough energy and Biomass for the visible requirement;
4. verify that the repair countdown starts;
5. wait for completion before judging the departure decision;
6. confirm the repaired state before adding more automation options.

The wait-before-leaving behavior was corrected in v1.0.5. If a current build still departs during the countdown, record the version, selected options, resource levels, and target type before changing the body grid.

Version-aware symptom check

Keep the route safe to leave running

• Keep a positive energy rate under active work, not only while every machine is idle.
• Decide what should happen when storage fills before enabling a long route.
• Use one leave condition you can recognize from the Map and resource panels.
• Do not combine a newly unlocked repair option with a newly rebuilt grid in the same test.
• After a patch, recheck one short route before restoring a long unattended sequence.

When the route is slow, crashes, or cannot select a target

• If the game crashes while Map rendering, energy text, or another screen is active, preserve the route state and use the crash and performance checklist.
• If two POI markers occupy the same position, temporarily use Map Settings to highlight a different POI type and test whether the intended marker becomes selectable. This is a temporary selection test, not a confirmed Map fix.
• If a delivery reaches its destination but Task Items remain, verify v1.0.8 and follow the Task Items delivery checks.
• If automation works but the active energy rate turns negative, diagnose the energy rate and capacity before extending the route.

For manual travel prerequisites and POI roles, use the Map and POI guide. For the permanent-progress side of infrastructure repairs, continue to Reactors and Spires.