Clear product documentation for configuring Pilotrav and understanding what each feature does and does not do.
Looking for strategy instead? Read the blog, browse the FAQ, or see the Travian bot overview.
Pilotrav’s auto building queue works through active village tasks in priority order. It can upgrade a chosen field or building, construct a new building, or level a group of resource fields. It starts only actions that the game currently permits and waits when a queue or resources block progress.
Pilotrav templates insert prepared task lists into a selected village, while starter packs apply tasks and selected settings to new accounts. Quick Plan offers Smart, Classic, and Saved choices. Templates save time but do not guarantee prerequisites, avoid duplicate application, or choose a settlement target for you.
Auto NPC redistributes a village’s stored resources through its Marketplace when crop storage reaches a chosen granary threshold, or optionally when any resource nears full storage. You set a target ratio for lumber, clay, iron, and crop. It runs once per village pass before building tasks and requires Marketplace access and enough gold for the trade.
Pilotrav trade routes repeatedly send configured resources from one village Marketplace to coordinates. A route can trigger after an interval or when a selected storage fill percentage is reached. Routes are checked once per village pass, so they are schedules rather than exact timers, and they need available merchants.
Pilotrav has no single second-village switch. It can train settlers in a qualifying Residence or Palace, optionally cover a one-settler shortfall, and send ready settlers to configured coordinates. A build template, culture points, expansion slots, free tile, and game availability remain requirements you manage.
Auto Celebration checks a village Town Hall and starts a small or preferred large celebration when the game offers one. It checks a village no more than once every two hours, can use hero resources and calculated NPC help, but does not read culture points, expansion needs, or a stop target.
Village Settings are saved per village, not as a universal account switch. They control Auto NPC, celebrations, construction boosts, hero resource use, and settlers. Saving clears the five-minute settings cache for that village, while the bot applies settings during its next relevant village pass.
Pilotrav Tools provides browser calculators for distance and travel time, counter-attack timing, and troop power or upgrades. Elephant Finder is the exception: it scans through a running account session. Tools calculate planning information; they do not send attacks, upgrade buildings, trade NPC resources, or automate production.
Pilotrav loads active tasks in ascending priority order and evaluates recognized types for a village or account hero. Building types are upgrade_field, upgrade_building, new_building, and resource_build_plan. Each needs type-specific target data; an unknown type remains active but is permanently skipped until you fix or remove it.
Pilotrav Farm List Automation opens Travian’s Gold Club Farm List at the Rally Point and starts existing game lists at randomized intervals. It reads list status, can pause native-list targets after losses, and applies a shared daily raid budget. You create targets and troop assignments in Travian itself.
Pilotrav Custom Farm List stores your raid targets and exact troop counts, then sends raids from chosen villages without Gold Club. It checks troops currently at home before each target and can avoid targets while prior troops are travelling. The Inactive Village Finder supplies candidates from population snapshots, not live scouting.
Hero Oasis Raids sends a living, available hero from its selected village to one saved oasis at a time, optionally with fixed troops. Pilotrav checks the oasis garrison immediately before sending. Nearby Oasis Scanner finds candidates through the running account session, and Battle estimate can skip risky hero raids.
Pilotrav can send an eligible hero on the first available adventure and distribute newly unspent hero attribute points. Adventure sending requires an active Hero task and a readable health value above the configured threshold. Attribute automation uses the four numeric allocations you set; it does not heal, revive, equip, or reassign old points.
Pilotrav can periodically train selected troops, attempt Hospital healing, and start one Academy or Smithy research check per village. Training chooses a random configured amount constrained by live resources. Academy and Smithy priority selectors are checked every four hours. Smithy break-even is a calculator only, never an automatic upgrade rule.
Pilotrav checks the Travian village sidebar for incoming attack markers, records visible landing timers, and can notify Telegram. Raid Protection can spend resources shortly before a known landing. Troop evasion sends all home troops on a raid to your coordinates. Neither feature distinguishes fake attacks or guarantees timely protection.
Pilotrav folder plans coordinate multiple account villages toward one target. Defense plans schedule reinforcement sends to arrive before a user-entered UTC+3 arrival time. Resource plans send calculated surplus through Marketplaces inside a time window. Both preview from saved snapshots, then recheck essential live values before sending.
Dual Accounts lets one Pilotrav bot use the main account identity plus up to two Travian dual logins during configured UTC+3 working hours. Each dual needs its own proxy. At a changeover, the bot logs out, waits a randomized handover delay, and logs into the next identity; only one identity is active at once.
Pilotrav runs a cloud browser for each Travian: Legends account. Verify e-mail, add a public world URL and credentials, attach a proxy, and start the account. The bot processes configured work in cycles and records results in Logs.
Pilotrav requires a proxy for every running account, so the cloud machine is never used as a direct game connection. Add one per account or bulk assign only accounts that have none.
Pilotrav uses a persistent browser identity, randomized delays, optional working hours, periodic logout/login, and browsing actions. Explicit settings take priority, but cannot guarantee avoidance of detection or penalties.
Live View shows a running account browser and accepts click, typing, and scroll input. Automation pauses while open and resumes after Hand control back to bot. It closes after 15 minutes without input and is not a recording or audio stream.
Logs shows one account activity in UTC+3 and refreshes every ten seconds. All, Info, and Problems explain cycles, schedules, control, login failures, recovery, and bans. The panel shows 200 lines; Pilotrav retains the latest 500.
Pilotrav sends bot-status notifications to one connected Telegram chat. Connect using the one-time Start link, enable the master switch, and choose triggers plus account notification switch. No bot e-mail or push alerts are implemented.
Folders group your accounts for overview and bulk actions. Each account belongs to at most one folder. Bulk starts and stops use random stagger timing; folder plans use snapshots and recheck live data before sending.
The wizard creates Travian: Legends accounts individually or in batches when enabled. It uses a managed e-mail pool, reserves one credit per job, enforces a rolling daily limit, and shows progress. Finished accounts need your fixed proxy before bot use.
Plans limit stored and started accounts. Trial permits one account for seven days from e-mail verification, subject to one trial per IP and device fingerprint. Expiry stops bots while stored accounts and settings remain until renewal.
Pilotrav stores data needed to operate accounts, including encrypted game credentials, proxy details, settings, logs, and support data. Account deletion removes related bot data, but user deletion is requested through Support or e-mail and handled within 30 days, subject to legal retention.
Pilotrav is built for Travian: Legends. Add Account accepts public HTTP or HTTPS world URLs; registration requires HTTPS travian.com. Pilotrav does not verify speed, round, availability, or login when adding an account.
Account is one Travian login, Bot is its automation, and Cycle is one work pass followed by random waiting. Proxy, Live View, folder, registration credit, and UTC+3 have specific panel meanings and limits.
Troubleshoot by reading exact log or panel message and checking one prerequisite at a time. Most failed starts come from unverified e-mail, expired plan, missing/unreachable proxy, or invalid game credentials. Other pages report actionable limits.