Planned by arrival time: say when it lands, the bot
works backwards to when it leaves. A standing order goes instead when its army is ready
and a scout says it wins.
Operations2
5 commands waiting
Next leaves1h 21m
Noble train on Grimwald
Timing—
not measured yet
TrainNoble train on Grimwaldscheduled
595|427 Grimwald · 2.8 fields · 1828 points
Clearing + nobleman 1
→ 595|427
4001501
leaves in 1h 21mlands 00:17:03
Nobleman 2
→ 595|427
150
leaves in 1h 21mlands 00:17:03
Nobleman 3
→ 595|427
150
leaves in 1h 21mlands 00:17:03
Nobleman 4
→ 595|427
150
leaves in 1h 21mlands 00:17:03
0/4 sent
Standing orderKeep Grimwald downactive
595|427 Grimwald · 2.8 fields · 1828 points
520 / 573 Axeman
292 / 292 Light cavalry
waiting for the army: 520/573 Axeman
again every 6h · at least 400 men
· sends 573 Axeman, 292 Light cavalry · last hit 7h 00m ago
Schedule an operation at a time, or when the army is ready
The same stack several times, landing at the time you set. The troops have to be at home when it leaves.Several stacks landing a few hundred milliseconds apart at the time you set. The troops have to be at home when it leaves.One small command to each target, leaving from the time you set.No clock. It waits until the village has trained this army - troops not built yet included - then keeps it at home, has the target scouted, and goes only when a fresh report says it wins two to one. It goes with nine tenths of the stack if a few are still out.
now 21:17:03
commandsms apart
hours, each time a new scout report says it still wins
A train lands a few hundred milliseconds apart - tight enough that nothing gets between the waves.
Each fake is one unit, so the defender has to treat it as real.
It shows above with what it is waiting for, and raiding carries on until the army is complete.