Travian Task Types Reference

What it does

Tasks power the building queue, templates, and Active Tasks. upgrade_field raises a slot to condition.maxLevel. upgrade_building raises an existing slot or building type. new_building constructs by type, or a wall at slot 40. resource_build_plan levels a chosen field group. Hero adventure is account-level rather than village construction.

How it works

Only active tasks load, ascending priority. upgrade_field needs slotId and maxLevel. upgrade_building needs slotId or gid and maxLevel; instance chooses Nth building type. new_building needs gid except wall uses slotId 40; Cranny can use instance. resource_build_plan accepts allResources, excludeCrop, onlyWood, onlyClay, onlyIron, or onlyCrop and defaults target level to 10. Completion updates status. Temporary skip permits lower work. Unknown type returns “Unknown type: {task.type}” internally and remains active without customer log, so replace it.

The bot works in cycles, not finish-time alarms. A normal cycle sleeps for a random 60 to 180 seconds after all villages; the baseline uses 240 to 600 seconds. Between villages it waits 2 to 8 seconds, or 5 to 15 seconds in the baseline. Account settings reach a running bot immediately. Village settings have a five-minute cache, cleared when the Village Settings card is saved. Task edits are loaded after a complete village pass, so a change made while sleeping can take about two cycles to take effect. Refresh starts the next cycle sooner but does not itself reload tasks.

Each village pass reads current state first. Its economy order is Auto NPC, Auto Add Cropland, Auto Celebration, trade routes, settler training and sending, then build tasks. Earlier work can therefore delay later work. Displayed resources and queues are the last state read, not a promise of the next game state. Game automation carries risk; no setting guarantees a game result or eliminates account risk.

When reading results, separate a completed game action from a configured intention. A success log means the bot reached the relevant page and the action entered the expected game flow; it does not make later state permanent or exempt from game rules. A wait message usually preserves configuration for a later cycle. A temporary skip lets other eligible work be considered where queue logic allows it. A failed click can stop lower-priority building work for that pass because strict priority protects resources intended for earlier work. Review the game page as well as logs after important actions.

The bot does not wake exactly when construction finishes. It discovers a finished action during the next cycle, so a gap can be roughly a cycle plus per-village delay. The village list refreshes on periodic re-login, normally every 60 to 120 minutes and 120 to 240 minutes in the baseline, or after restart. A village founded while the bot runs is therefore not immediately processed. Configure clear priorities, avoid conflicting automation, and give one change time to appear before adding another.

Settings

Setup in 5 steps

1. Choose village and task control.

2. Add recognized task with required target.

3. Place prerequisites above dependents.

4. Reorder so lower number is more important.

5. Review completion or waiting logs and remove invalid tasks.

Requirements

Limits and what it does not do

Common problems

“P{priority} [{taskType}] completed — {reason}” confirms completion. “...: {reason}, skipping” is temporary. “[{taskType}] slot={slotId} failed — will retry next cycle” blocks lower build tasks this pass. A task with no movement and no log can be unknown type or invalid target; inspect and replace it.

Related features

Auto building queue · Build templates and starter packs · Village settings

Last updated: October 26, 2026