Travian Trade Routes Automation

What it does

Trade Routes are per-village Marketplace sends in the Trade Routes tab. Each enabled route has destination coordinates, fixed amounts or Send all resources, and an interval or threshold trigger. Any valid coordinates can be used; the engine does not verify that the target is your own village.

How it works

Every village pass loads enabled routes. An interval route is due after interval_minutes since last_sent_at, but can never be shorter than a cycle. A threshold route is due when its selected resource, or any resource, reaches threshold. last_sent_at is saved before clicking to reduce duplicate sends after a crash. The bot checks Marketplace, form, and merchants, enters amounts and coordinates, then confirms. No merchants gives about a three-minute cooldown; a missing form or button gives about five minutes. Threshold routes have no separate cooldown and can send on each pass while full.

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. Build a Marketplace.

2. Open Trade Routes and add a route.

3. Enter destination, trigger, and fixed amounts or Send all resources.

4. Enable and save.

5. Watch Last sent and logs through a normal cycle.

Requirements

Limits and what it does not do

Common problems

“Trade route "name": sending from village v to (x|y)...” starts an attempt. “no merchants available — 3 min cooldown” means wait for merchants. “send form not found” means nothing was sent. “send button not found (target x|y)” means validate coordinates and confirmation flow.

Related features

NPC trading · Village settings · Auto building queue

Last updated: October 26, 2026