Pilotrav Telegram Notifications
Requirements
- Telegram account
- Tap Start after Connect
- Required switches enabled
Limits
- One chat per user
- No push, digest, quiet hours, groups
- Some messages Turkish
What it does
Connect and test are limited to five requests per ten minutes. A message needs connected Telegram, global switch, account switch, and trigger switch. System messages use panel language, but many farm and bot action messages are Turkish free text.
How it works
Connect and test are limited to five requests per ten minutes. A message needs connected Telegram, global switch, account switch, and trigger switch. System messages use panel language, but many farm and bot action messages are Turkish free text.
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 |
|---|---|---|---|
| Enable Notifications | Master switch | Off | On/off |
| Bot Started / Stopped / Crash | Lifecycle | On after master | On/off |
| Login Failed / Ban / Attack | Problem | On after master | On/off |
| Notifications for This Account | Account switch | On API default | 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
“Waiting for you to tap Start in Telegram...” means tap Start. “Önce Telegram bağlayın” means connect. “Çok fazla Telegram isteği...” means 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?