Travian Farm List Automation

What it does

Farm List Automation presses Travian’s native Gold Club start controls. It never creates a game list, adds targets, or changes its troop assignments. The first eligible run is immediate; later runs use a randomized interval. It reads list state, may deactivate native-list targets after losses, and can send a Farm Actions notification after a successful start.

How it works

The bot skips when disabled or the shared daily limit is reached. It finds the first cached village with a Rally Point, opens the Farm List tab, waits up to 25 seconds, and makes up to three attempts with 10 to 15 second pauses. A table without a start button is treated as already active. With any per-list interval or extra delay, due active lists are clicked individually with 0.8 to 1.5 second gaps; otherwise Start All is attempted first. Loss pause runs before sending: red pauses all-troops-died reports; any also pauses yellow loss reports, up to 10 targets. The UTC daily counter counts started lists rather than individual native-list targets. A due native Farm List can mini-login during logout pause; Custom Farm List cannot.

Pilotrav works in cycles, so an interval is a minimum rather than an exact alarm. A normal cycle waits 60 to 180 seconds after account work. Saved settings are loaded on the next cycle, but page loading, earlier work, game queues, resources, troops, merchants, and Travian rules can defer an action. A log records the observed game flow, not a permanent result. Review the relevant Travian page after important sends. No tool is risk-free and no configuration removes account risk.

Military settings share several practical timing rules. The bot normally checks an account’s settings at the beginning of a cycle. It then handles time-sensitive dodge and folder work before incoming attack detection, farm lists, hero work, and the per-village work that includes raid protection, research, training, and Hospital. Consequently, a later action can be delayed by an earlier eligible action or by a slow game page. A configured feature with no available troop, resource, merchant, building, button, or valid target is skipped and reconsidered later according to its own timing rules.

Use the Logs page to separate a configured intention from a completed game action. A message that says not due, unavailable, skipped, or waiting normally leaves configuration in place; it does not mean Pilotrav will reserve troops, resources, or merchants for that feature. Conversely, a confirmed send consumes the game resources that Travian accepted, which can affect later work in that same or the next cycle. Avoid conflicting plans, verify the first real action for a new setting, and keep enough time between a planned action and a game deadline. Telegram notices require a connected chat and the matching notification type. The bot acts through the account’s own browser session, but that does not override Travian’s server checks or its game rules.

Settings

Setup in 5 steps

1. Buy Gold Club and create lists with targets and troops in Travian.

2. Enable Farm List Automation.

3. Set a broad MIN/MAX interval and optional extra delay.

4. Optionally choose loss pause and a daily limit.

5. Save, start the bot, and review the first Farm Actions logs.

Requirements

Limits and what it does not do

Common problems

“Farm list: rally point not found yet, will retry” means wait for cached state. “Could not open farm-list page (attempt n/3)” or “Farm-list button did not load” ends that cycle. “Farm lists are already active; scheduled for the next interval” is expected when a table has no start button. “All farm lists started” or “Started N farm lists” confirms a start attempt.

Related features

Custom Farm List · Hero oasis raids · Attack alerts and raid protection

Last updated: October 26, 2026