Pilotrav and Travian Bot Glossary
Requirements
- Read Account as game login
- Use Logs for Bot status
- Check UTC+3 before schedules
Limits
- Folder does not share accounts
- Dual is not simultaneous bot
- Credit consumed on completion
- Plan counts stored accounts
What it does
Action Delay, Post-Build Delay, and Cycle Delay are separate waits. Proxy is required outbound connection. Live View pauses automation for manual control. Folder groups accounts. Registration credit is consumed after successful registration. UTC+3 is schedule and plan time zone.
How it works
Action Delay, Post-Build Delay, and Cycle Delay are separate waits. Proxy is required outbound connection. Live View pauses automation for manual control. Folder groups accounts. Registration credit is consumed after successful registration. UTC+3 is schedule and plan time zone.
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 |
|---|---|---|---|
| Bot | Account automation | Stopped after add | Statuses |
| Cycle Delay | Wait after pass | 60–180 s API | Range |
| Proxy | Browser connection | Required | Compatible host:port |
| Live View | Manual control | Off | Running bot |
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
“Hand control back to bot” ends Live View. “Problems” means warning/error levels. “Stagger seconds” is randomized folder gap.
Related features
getting started · proxies · anti detection and human behavior
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 ProxiesTravian Bot Human Behavior SettingsLast updated:
Ready to try Pilotrav?