Pilotrav Live View Manual Control
Requirements
- Running bot and open browser
- Available session capacity
Limits
- Unavailable for stopped, sleeping, starting bot
- Pauses automation
- No recording or audio
What it does
Live View needs a running bot with an open page. Frames can reach 1024×768 at about ten per second. Lost connections retry five times after 1, 2, 4, 8, and 15 seconds, then offer Reconnect. One manual session controls a bot.
How it works
Live View needs a running bot with an open page. Frames can reach 1024×768 at about ten per second. Lost connections retry five times after 1, 2, 4, 8, and 15 seconds, then offer Reconnect. One manual session controls a bot.
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 |
|---|---|---|---|
| Live View | Opens control | Off | Running account only |
| Hand control back to bot | Resumes bot | Manual | In session |
| Reconnect | Retries session | Hidden | On loss |
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
“Bot must be running for Live View” means start first. “Connection lost - tap Reconnect” follows automatic retries.
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?