A base-building RTS can make logistics matter when enemies can cut a route. Connect a depot to a frontline base with a main road and a secondary path. A raider severing the main line should change which units receive supplies, while a repaired backup restores access.
Map the depot, base and two routes
Use three nodes: depot, relay and frontline base. The main road runs directly from depot to relay; a longer backup path connects the same endpoints through a second edge. Keep one supply token available at the depot. Show route state and unit supply status on the map.

Keep the graph small enough to inspect. The backup should be visible before an attack so players can decide whether to protect the main road or prepare another connection.
Let an attack sever the main connection
In the intact state, the depot reaches the frontline base and its units are supplied. A raider cuts the main edge. If the backup is not active, the base becomes unreachable and units lose the supply token on the next update. Engineers can connect the secondary route to restore reachability.

Make the cut persistent until repaired. Do not silently reroute cargo if the prototype is meant to test player response. If automatic rerouting is part of the design, expose that rule and compare it separately.
Replay intact, cut and backup states
The local graph check compares three states. With the main line intact, the base receives supply. With the line cut and no backup, the base is unreachable. With the backup connected, reachability returns and the unit supply flag becomes active.
| Network state | Base reachable | Unit supplied |
|---|---|---|
| Main route intact | Yes | Yes |
| Main cut, backup off | No | No |
| Backup connected | Yes | Yes |
This deterministic test verifies graph connectivity and a supply flag only. It does not model combat AI, convoy pathfinding, production economy, unit attrition or a full RTS simulation. Test those systems after disruption and repair produce clear network states.

Prompt for a supply-network prototype
Ask an AI game maker for a small base-building RTS with a depot, relay, frontline base, main road, backup route and one supply token. Let a raider cut the main edge. Units lose supply if no path remains; engineers can connect the backup route. Show the graph and unit status, and add a reset for intact, cut and repaired cases.
Once this works, add convoy timing or combat response one at a time. Keep the first experiment focused on route reachability and its effect on supplies.
Start a base-building RTS prototype in SEELE
Frequently asked questions
Should supplies reroute automatically after an attack?
Choose one behavior and make it visible. For this test, units lose supply when the depot has no path to the base, and engineers restore it by connecting the backup. If automatic rerouting is intended, test that as a separate rule so players can distinguish system behavior from their own repair choice.
How many routes should the prototype include?
Use one main route and one backup that connect the same depot and base. This makes the cut and repair easy to compare without adding extra logistics rules. Add branches after players understand which path is active and how a severed connection changes unit supply.
What should I test before combat effects?
Compare the intact graph, the severed main route and the connected backup with the same depot token. Check base reachability and unit supply after each update. This isolates network state before combat, convoy pathfinding or resource production adds more variables.


