Travian Bot Human Behavior Settings
Requirements
- Running account and proxy
- Min no greater than max
Limits
- Risk labels are not guarantees
- Logout wait is fixed
- No setting removes account risk
What it does
API defaults are action 2–8 seconds, post-build 3–8 seconds, and cycle 60–180 seconds. Work Schedule uses UTC+3 and a daily random offset up to 15 minutes. Logout occurs after random 60–120 minutes and waits about 15–25 minutes. Random activity occurs after random three-to-seven cycles and is skipped in Idle mode.
How it works
API defaults are action 2–8 seconds, post-build 3–8 seconds, and cycle 60–180 seconds. Work Schedule uses UTC+3 and a daily random offset up to 15 minutes. Logout occurs after random 60–120 minutes and waits about 15–25 minutes. Random activity occurs after random three-to-seven cycles and is skipped in Idle mode.
Pilotrav works only while an account runs. Each cycle reads game state, does eligible work, then waits a randomized delay. A proxy, credentials, plan, game queue, page, or Travian rule can prevent an action. Check Logs and the game page after important changes. Times for schedules and plans use UTC+3. Automation carries account risk; no setting removes that risk.
Settings
| UI label | What it does | Default | Range |
|---|---|---|---|
| Action Delay | Action wait | 2 / 8 s | 0.5–120 s UI |
| Post-Build Delay | Build wait | 3 / 8 s | 0.5–60 s UI |
| Cycle Delay | Pass wait | 60 / 180 s | 10 s–60 min UI |
| Work Schedule | UTC+3 hours | Off | Slots 0–23 |
| Periodic Logout/Login | Logout interval | 60 / 120 min | 30–480 min |
Setup in 4 steps
1. Open the relevant Pilotrav page.
2. Check the requirements below.
3. Save the listed settings.
4. Confirm the next result in Logs.
Requirements
Limits and what it does not do
Common problems
“Outside working hours - ... Waiting N min...” means check UTC+3 slots. “Working hours started - restarting browser...” is expected.
Related features
getting started · proxies · live view
Frequently asked questions
When does this take effect?
It takes effect after its prerequisites are met and the running bot reaches the relevant account during normal processing. Network conditions, game pages, existing work, plan access, and configured delays can postpone it. Check the exact log and Travian page rather than assuming an immediate result.
Will this remove automation risk?
No. Pilotrav documents configured behavior and operational limits, not a safety or game-result guarantee. Travian rules, account status, server responses, proxy quality, and timing remain outside the feature. Use the service only where you accept the associated account risk.
What should I do after an error?
Read the exact customer-visible message first, then check the prerequisite it names: running bot, proxy, credentials, plan, verification, or game building. Correct one issue at a time and retry only where instructed. Include recent logs in a Support ticket if the cause remains unclear.
Related docs
Pilotrav Getting Started GuideTravian Bot ProxiesPilotrav Live View Manual ControlLast updated:
Ready to try Pilotrav?