Travian Bot Proxies
Requirements
- Proxy per running account
- HTTP/HTTPS for authenticated proxy
Limits
- SOCKS5 with username/password unsupported
- Bulk assign never replaces proxy
- Save does not test proxy
What it does
Accepted forms are host:port or IP:port, optionally HTTP, HTTPS, SOCKS4, or SOCKS5. Saving does not test connectivity. Network faults retry after five minutes; bulk assignment distributes in order to empty accounts and can start accounts three to six seconds apart.
How it works
Accepted forms are host:port or IP:port, optionally HTTP, HTTPS, SOCKS4, or SOCKS5. Saving does not test connectivity. Network faults retry after five minutes; bulk assignment distributes in order to empty accounts and can start accounts three to six seconds apart.
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 |
|---|---|---|---|
| PROXY SERVER | Endpoint | Empty | [scheme://]host:port |
| PROXY USERNAME | Login | Empty | Text |
| PROXY PASSWORD | Password | Empty | Blank edit keeps old value |
| Start the bots after assigning | Starts assigned accounts | Off | On/off |
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
“No port in the proxy address...” means add :port. “A SOCKS5 proxy with username/password is not supported...” means use HTTP/HTTPS. “Bot crashed 3 times in a row...” means fix cause and start manually.
Related features
getting started · anti detection and human behavior · 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 Human Behavior SettingsPilotrav Live View Manual ControlLast updated:
Ready to try Pilotrav?