Quick answer
When a mining building refuses a road or connection, inspect both endpoints and the resource node before replacing the whole route. Mining nodes often sit across elevation changes, so a visually close path may still lack a valid connection point.
Version and source notesUpdated 2026-09-05 · Current for this version
- Updated
- 2026-09-05
- Works with
- PC mining nodes, connections, and cliff routes
- What this guide covers
- Endpoint and elevation checklist grounded in system references
- Version notes
- Connection tools and node behavior may change after updates
- Update status
- Current for this version
Connection checklist
- Select the mining building and confirm the node is active and in range.
- Start the connection from the building's actual endpoint, not its wall.
- Use the appropriate path, rope, bridge, or ladder across the cliff break.
- Check that the destination camp and warehouse can receive the output.
- Reload once if the route preview and placed connection disagree.
If every point fails
Test a short connection on a fresh save or another building. If only one node fails, record its location and build number. If all connections fail, check the patch, input mode, and whether a previous path is blocking the endpoint.
FAQ
Is a short distance always a valid route?
No. Elevation, endpoint angle, camp range, and existing connections can matter more than distance.
Should I demolish the node?
No. Preserve the save and test another endpoint first; demolition may remove evidence or resources.
Next step
Read connection and missing resources, warehouse logistics, and how to get Fetchers working.