Core concepts
Routines, actions and task order
Build routines that reflect farm purpose, preserve active queues and avoid conflicting or wasteful action order.
What a routine contains#
A routine is an ordered list of supported actions plus their customer-facing preferences and limits. It is reusable across compatible farms, but assignment does not guarantee that every action will be available on every account.
The game decides prerequisites: unlocked features, active queues, owned resources, event timing and march availability. A well-configured action may legitimately do nothing when its prerequisites are absent.
A practical order#
- 1
Collect completed output
Clear known rewards and completed queues before asking whether development or troop facilities are idle.
- 2
Maintain the city
Handle configured research, buildings, workers, troop queues, healing and wall care.
- 3
Use selected owned items
Apply inventory, buff or shield preferences only after understanding current need and existing effects.
- 4
Run dailies and special buildings
Process eligible errands, gifts, shops and exploration within configured limits.
- 5
Dispatch outward work last
Gathering changes squad availability; put it after city tasks that may need those squads.
Limits are part of safety#
- Prefer resource-priced or free operations when that is the configured intent.
- Use quantity and refresh limits for shops, donations and repeatable tasks.
- Do not enable premium-currency spending unless a released action explicitly exposes and explains it.
- Do not combine uncertain side effects with aggressive retries.
When tuning a routine, change one action or limit, run one known farm, then inspect the result. Changing one setting at a time makes its effect easier to understand.
Still stuck?
Complete the evidence checklist before contacting support. Never send passwords, recovery codes, payment details or private licence material.