Travian Village Settings

What it does

Village Settings apply only to the selected village. Economy controls include Auto NPC, Auto Celebration, Construction Boost, hero inventory for building, Settler Training, and Send Settlers. Account-level fallbacks exist for some construction options, but a saved village value takes precedence.

How it works

Save the card to persist values and clear its cache. During a pass settings are used in order: NPC, celebration, routes, settler training and sending, then construction. Construction Boost only checks a full queue. Complete instantly with Gold needs remaining queue time above its threshold; Complete immediately when queue is full ignores threshold. The engine clicks the first game finish button and has no gold budget or daily cap.

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. Select the village.

2. Open Village Settings.

3. Change only intended automation.

4. Set non-zero coordinates before settler sending.

5. Save and check logs after next pass.

Requirements

Limits and what it does not do

Common problems

If a setting appears ignored, confirm it was saved on the intended village and allow a pass. “Complete immediately: queue is not full” means no full queue. “insufficient gold (x < 2)” means finish action cannot run. “dialog button not found” means completion was not confirmed.

Related features

Auto building queue · NPC trading · Second village and settlers

Last updated: October 26, 2026