Pilotrav Troubleshooting Guide
Requirements
- Open Logs/error page
- Copy message
- Correct prerequisite
- Start once and wait
- Send logs to Support if needed
Limits
- Cannot override game bans/rules
- Repeated start cannot repair proxy/credentials
- Support tickets have rate limits
What it does
Normal start needs verified e-mail, plan, proxy, and credentials. Network proxy faults retry after five minutes; wrong credentials stop without retry. Non-network crashes stop restart after three. Live View needs running page, Telegram needs Start and switches, and registration checks plan, slots, credits, e-mails, daily limit, and availability.
How it works
Normal start needs verified e-mail, plan, proxy, and credentials. Network proxy faults retry after five minutes; wrong credentials stop without retry. Non-network crashes stop restart after three. Live View needs running page, Telegram needs Start and switches, and registration checks plan, slots, credits, e-mails, daily limit, and availability.
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 |
|---|---|---|---|
| Start | Starts eligible bot | Manual | Eligible account |
| Stop | Stops bot | Manual | Running account |
| Reconnect | Retries Live View | Manual | Connection loss |
| Enable Notifications | Telegram master | Off | On/off |
| Retry | Registration retry | Conditional | Up to 3 |
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
“Proxy is required...” add one. “You must verify your email...” verify. PLAN_EXPIRED renew. “The game rejected the login...” correct credentials. “Connection lost - tap Reconnect” retry while running. “Not enough ready e-mails.” reduce batch or wait.
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?