Travian Dual Accounts and Handover

What it does

Dual Accounts is a handover feature, not several bots on one account. You add dual credentials supplied by Travian’s own dual-invite system, assign each a proxy, and choose working hours. Tasks, villages, and account settings remain the same; only the active login identity changes.

How it works

A dual stores label, login, required proxy, and UTC+3 start/end hours. Equal start and end means all day. On every cycle, Dual 1 then Dual 2 are selected if their hours cover now. Otherwise the main identity runs uncovered hours when Work Schedule is off, or only main schedule slots when it is on. If no identity covers the hour, the browser closes and checks again every 10 minutes. Switching logs out, closes the browser, waits a random handover delay, applies the next identity, and logs in. Changes appear on later cycles but changed credentials or proxy apply at next handover. Without duals, Work Schedule has up to 10 slots, default 8–14 and 16–22 when enabled, with randomized daily boundary offsets. Overlapping dual hours resolve by slot order.

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. Create the dual relation through Travian dual invite.

2. Add Dual 1 with login, proxy, and UTC+3 hours.

3. Add Dual 2 only if needed and check overlap.

4. Set handover delay and main Work Schedule.

5. Save and verify the first handover in Logs.

Requirements

Limits and what it does not do

Common problems

“Identity switch: main -> dual1 (taking over in N min)” starts a handover. “dual1 took over; login successful” confirms it. “Outside working hours - no identity is scheduled. Waiting 10 min...” means all schedules are uncovered. “Working hours started - restarting browser...” is an expected transition. Repeated switch failure requires checking dual credentials, proxy, and hours.

Related features

Farm lists · Farm lists · Farm lists

Last updated: October 26, 2026