Travian Custom Farm List

What it does

Custom Farm List is Pilotrav’s own raid list. Each target stores a source village, coordinates, enabled state, and exact troops. It sends raids only and skips a target if every requested unit is not home. Inactive Village Finder searches map snapshots for villages whose population and owner population did not grow enough, then can add candidates to this custom list.

How it works

When due, enabled targets are loaded in order and grouped by source village. The Rally Point is opened, all home troops are read, then each target is filled, sent as Raid, confirmed, and followed by a new troop read after 0.8 to 1.5 seconds. Skip targets with troops in flight records busy time as twice one-way travel plus 60 seconds; unread travel uses a distance estimate. A sending round schedules its own random MIN/MAX delay plus optional extra delay. If nothing sends, the timer does not advance. Finder results use snapshot comparisons, circular distance, optional alliance filters, village-count filters, and optional Natars; results are nearest first in pages of 30. Troops must be entered in Add New Target before Add or Add All.

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. Enable Custom Farm List and choose an interval.

2. Enter exact troop numbers in Add New Target.

3. Add coordinates manually or use Inactive Village Finder.

4. Enable Skip targets with troops in flight if desired.

5. Save, start the bot, and review sends and troop skips.

Requirements

Limits and what it does not do

Common problems

“Custom farm list: sent N attacks” confirms sends. “Custom farm: skipped N targets - not enough troops in village (available: ...)” means troops were absent. “N targets skipped - raids still on the way or returning” comes from in-flight skipping. “Custom farm: could not send to (x,y) - ” is retried later. Finder can say “No inactive villages matched these criteria” or “First enter the troops to send in the Add New Target form”.

Related features

Farm lists · Hero oasis raids · Attack alerts and raid protection

Last updated: October 26, 2026