Build an Auto-Battler Where Resources Travel Before Spending

Make an auto-battler with resources that move across the map using AI. Route a courier, delay recruitment until delivery and test travel time.

Seele Editorial TeamUpdated November 19, 2026

A moving resource changes an auto-battler when the player must route it before spending. In the fictional game Relay Crown, a token appears in the arena center. A courier carries it to one of two roster pads; only delivered tokens can recruit a unit before the automatic battle.

Start with one token, one courier and two pads. Show the pickup, route and destination clearly. Let the player choose a lane, then compare when a recruit becomes available while the combat rules stay fixed.

A glowing resource token travels from the arena center toward two roster pads in an original auto-battler field.

Make delivery part of roster planning

Track each token as spawned, carried, delivered or spent. The courier follows a visible lane from the center to a roster pad. Keep a carried token unavailable until it reaches the pad; otherwise the player can recruit before the route has paid off.

At delivery, add the token to that pad's balance and let the player recruit a unit. After the roster locks, resolve combat automatically. Log route, courier speed, delivery time, unit purchase and battle start so a late recruit has a clear cause.

If you add obstacle avoidance, Godot's NavigationAgent2D reference describes path-following behavior for a moving actor. Treat it as optional routing vocabulary; Relay Crown's courier timings below come from an explicit distance model.

Read Godot's NavigationAgent2D reference

A small courier carries the glowing token along a marked lane toward the waiting roster pad.
Relay Crown gameplay concept: a courier carries a token along a marked lane.

Change courier speed on the same route

The fictional lane from center spawn to roster pad is eight tiles long. In a deterministic route model, a courier moving at two tiles per second delivers in four seconds. Recruitment stays unavailable during travel.

Change only courier speed to four tiles per second. On the same eight-tile route the token arrives in two seconds. The model isolates travel time; it does not simulate path blocking, unit balance or the automatic fight.

In the prototype, hold route length and battle timing fixed while comparing the two speeds. Verify that the token cannot be spent before delivery, that a unit joins the roster afterward, and that combat begins at the same lock point. Then test congestion and rerouting as a separate iteration.

The courier has delivered the token, and a new unit now stands with the roster beside the battle arena.
Relay Crown gameplay concept: the delivered token adds a unit to the locked roster.

Ask AI for a courier-to-roster combat loop

Describe a central token spawn, courier lanes, two roster pads and one auto-battle. Ask for visible token states and a rule that enables spending only on arrival. Keep the eight-tile lane and battle lock fixed while comparing speeds two and four.

Check the event log from spawn to delivery, recruitment and battle start. Play the prototype to confirm the route reads clearly and a late courier changes the roster at the intended time. The distance model cannot verify traffic or combat feel.

Create a small original auto-battler called Relay Crown. Spawn one resource token at the arena center. A courier carries it along a visible eight-tile lane to one of two roster pads. The token is unavailable until delivery. Let the player choose a pad and recruit one unit after arrival; lock the roster at the same battle start point in every run. Add a resettable courier speed setting with values 2 and 4 tiles per second. Show token state, route, estimated arrival, pad balance, roster and battle start. Log every transition. Do not add path blocking or extra resources until this loop is clear.

Tune travel time before adding lane traffic

When the token becomes spendable only after delivery, the route affects roster timing and the next automatic fight. Keep one token and one courier while tuning travel speed. Add congestion or alternate routes after the player can see why a recruit arrived late.

Start an auto-battler prototype with SEELE's AI game maker

Frequently asked questions

Should a token be spendable while the courier is moving?

Usually not if travel is meant to create a timing choice. Keep carried resources in a separate state from pad balance, and transfer them only on arrival. If the player can reserve or borrow a token in advance, show that as a distinct rule so the delivery route still has a visible consequence.

How can the route affect an automatic battle?

Let delivery determine when a recruit joins the roster, then lock the roster at a consistent battle start. Show the unit and token ledger before combat begins. That makes a delayed courier explain a composition change without secretly altering combat stats or resolving the fight differently.

Does the distance model prove the auto-battler is balanced?

No. It calculates arrival time for a fixed route at two speeds. It does not test blocked paths, competing couriers, unit strength, player comprehension or combat outcomes. Use it to check the timing rule, then test routing and automatic battles in an interactive prototype.

SEELE AI

Turn this guide into a playable build.

Start with a focused brief, then iterate in the Seele AI Workspace.

Start creating