Pilotrav Folders and Bulk Actions
Requirements
- At least one account
- For start: verified e-mail, plan, proxy
Limits
- No cross-user sharing
- One account in one folder
- One job per folder
- Overview not live polling
What it does
Folder names are unique and up to 100 characters. Assignment allows 200 accounts per request. One folder job runs at a time. Stagger defaults to 20 seconds and each gap is 70% to 130% of that value. Overview refreshes every 30 seconds and is last bot-visit data.
How it works
Folder names are unique and up to 100 characters. Assignment allows 200 accounts per request. One folder job runs at a time. Stagger defaults to 20 seconds and each gap is 70% to 130% of that value. Overview refreshes every 30 seconds and is last bot-visit data.
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 |
|---|---|---|---|
| Folder name | Name | Empty | Unique, max 100 chars |
| Colour | Folder colour | First | Five choices |
| Stagger seconds | Start/stop gap | 20 s | 0–600 s |
| Apply settings preset | Merges preset | Manual | Saved/baseline |
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
“Start {count} accounts?” needs confirmation. FOLDER_JOB_RUNNING means wait. EMAIL_NOT_VERIFIED, PLAN_EXPIRED, and PROXY_REQUIRED are per-account failures.
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?