City tasks

Troop Training

Queue any mix of troop types and tiers; it walks to each training building and trains them.

Troop Training trains the troop types and tiers you queue — any mix of Ground, Mounted, Ranged and Siege in one run. For each building it walks there on your city map, opens its training window, and trains each queued tier up to its count, finishing every batch with speedups so the next one can start.

NeedsCity map — Barracks, Stable, Archer Camp, Workshop (the ones you train at)A city map for this instance Troop tiers in Resources ▸ Troops

It runs from two places, and each keeps its own settings. As a plan task: Duties ▸ Tasks ▸ Add to plan, then Instances ▸ Open an instance ▸ Task setup ▸ Troop Training. As a daily activity: Duties ▸ Daily activities ▸ Troop training ▸ ⚙.

The Troop Training board: type crests, the tier rail, the batch list and the plan cost, with Track progress across runs at the top.

Set it up as a plan task

In City Mapper, map and calibrate the training building of every type you will train, and give this instance its city map (link the map to its emulator, or pick it as City map in Settings).
On Duties, click the Troop Training chip under Add to plan.
Open Task setup ▸ Troop Training. Click a type crest, then tap the tiers you want on the rail below — each tap adds a batch.
Set each batch's count, and drag the batches into the order you want.
Tick Track progress across runs if the counts are a long-term goal, then press Save changes.

Set it up as a daily activity

On Duties ▸ Daily activities, switch Troop training on. It ships with 500 Ground T1 a turn.
Click ⚙, open the Task setup tab to change the batches, and press Done.

The settings form

Summary line

Train troops — the types and tiers you pick.

Track progress across runs

On: the bot remembers how many of each batch it has trained and resumes until every target is met; finished batches are skipped, and a building with nothing left is not visited. Off: every run trains the full counts again. Default: Off.

Type crests

Mounted, Ranged, Ground, Siege — whichever types your troops library holds. Click one to show its tiers on the rail. Every type you add lands in the same batch list.

Tier rail

The picked type's tiers, highest first. Tap a tier to add a batch; tap it again to remove it. Queued tiers fill in and show their place in the list. Hover a tier to see its cost per troop.

Batch rows

One per queued batch: the type's crest, the tier, a count, what the batch costs, a grip, and ✕ to remove it. A new batch lands after the other batches of its type.

Count

How many to train in that batch. Drag the number sideways, click it to type, or click it and scroll. Range 1 to 99,999,999. A new batch starts at 10,000.

Progress (tracking on)

Reads, for example, 2.5K / 10K trained, with a thin bar under the row. It climbs while a run is going, even with the form open. Only troops that were really trained count: a tier the run could not train adds nothing to its row.

Drag to reorder

Drag a row by anywhere that is not a control. The order decides which building is visited first, and the order of tiers inside each building.

Empty list hint

Pick a type above, then tap its tiers — every type lands here.

PLAN COST

The whole plan's bill: a bar showing each resource's share, the amounts, and N troops queued. Hidden while the plan is empty. Costs come from Resources ▸ Troops.

Footer notice

The bot walks to each building via your city map — map your training buildings (Barracks/Stable/Archer Camp/Workshop) in City Mapper. A type it can't reach is skipped, the rest still run.

Reset progress

Shown beside the notice while tracking is on and some batch has progress. It sets every trained-so-far count back to zero; press Save changes to keep it.

Empty library message

No troop tiers in the library yet — add them under Resources → Troops.

Save changes / All tasks

Save changes appears only while you have unsaved edits; All tasks goes back to the card grid.

An empty batch list shows under Needs setup: “Troop Training” needs “train plan” set before it can run. A building you queued but have not mapped shows as a chip on the plan row before the run starts.

The Troop training duty

Schedule tab

Default: Once a day. The Schedule tab is the same on every Daily activities row — How often (Once a day or Every few hours), Run before plan tasks, Come back every, Run cap, Retry when it fails and Reset schedule. Each is explained on Daily activities.

Task setup tab

The same board, headed this duty's own copy — the Task plan keeps its own. Default: one batch of Ground T1 × 500, Track progress across runs off — the whole batch every turn.

Reset task settings

Asks first, then restores the duty's shipped batch; the schedule is kept.

Record line and Reset records

What the duty remembers about its turns, and a button that forgets it (it asks first).

Done

Saves both tabs. ✕ or Esc discards.

How it runs

Building by building, in the order each building first appears in your list. With tracking on, a building whose batches are all done is skipped without walking to it.
Opens the training window. It walks to the building on your city map and checks the right window opened. An unreachable building is skipped and the rest still run.
Checks the building is free. If troops are already training there, or the building is upgrading, it skips that building's batches.
Trains each queued tier of that building: it swipes to the tier, skips a tier that is not unlocked, reads how many the city can afford from the number in the training box, and trains the smaller of that and what is still needed. If it cannot read the number, it stops that tier instead of guessing.
Finishes the batch: Train, then Training Speedup, then Finish All — so the building is free for the next batch. It repeats until the count is met or resources run out.
Closes the window at the end.

What it spends: the troops' resource cost, and training speedups on every batch. It presses the plain Train button, never the gem one.
When speedups run out: the log says Couldn't find Finish All — likely out of speedups. That tier stops, and the batch it had started keeps training on the game's own clock.
What it reports: a row per building — Opening the Stable → Opened the Stable — then a row per tier, Mounted — T10 ×10000 → Trained 10k Mounted T10.
When the plan task runs: once a day, whenever the screen is free. Its Rhythm sheet offers no How often — only When it may run.
Plan and duty together: the first to train that game day holds the other (already done today by the Task plan / already done today by Task duties).

Every batch spends training speedups to clear the queue. A large count with tracking off repeats that spend every day.

Examples

Daily top-up: switch the Troop training duty on — Ground T1 × 500, tracking off.
A long-term goal: plan task, Mounted T12 × 200,000, Track progress across runs on. It trains what it can each day until the target is met.
Two buildings in one run: Ranged T11 × 5,000, then Siege T11 × 2,000. It trains at the Archer Camp first, then walks to the Workshop.

Troubleshooting

A row says “Couldn't reach the Stable — is it mapped in City Mapper?”.

Map and calibrate that building in City Mapper. The plan row's chip uses short names: “barracks”, “stables” (Stable), “range” (Archer Camp), “workshop” (Workshop).

The log says “Tier N isn't unlocked yet — skipping it”.

The account cannot train that tier yet. Remove the batch or pick a lower tier.

A building row says “Troops are already training at the Barracks”.

The building was busy when the bot arrived — each building trains one batch at a time. It tries again on the next run.

The log says “Out of resources — stopping tier N”.

The city could not afford more of that tier. The next tier or building still runs.

The log says “Couldn't read the training capacity for tier N — skipping it”.

The number in the training box could not be read, or the two ways of reading it disagreed, so the tier is skipped and its row shows a ✕. Something may have covered the training window, or the emulator display is not 540 × 960 at 120 dpi. See Emulator setup.

It trained the whole count again, although it trained yesterday.

Track progress across runs is off, so every run starts over. Tick it if the count is a goal rather than a daily batch.

It says “Nothing to train at the Barracks — already done”.

Tracking is on and every batch at that building reached its target. Press Reset progress and save to start again.