Travian Attack Alerts and Raid Protection

What it does

Sidebar attack detection supports Telegram alerts, Raid Protection, dodge, and Idle mode. Raid Protection can force NPC, troop training, Smithy research, or a full Marketplace send. Dodge sends all home troops as a raid to a user-selected coordinate. Idle mode stops ordinary automation but retains attack checks and dodge wake-ups.

How it works

The bot checks attacks once per cycle and sends a Telegram alert no more than once per village per 20 minutes. Known attacks are rechecked every 30 seconds and every five seconds in the final 60 seconds before a dodge. The Incoming Attack Alert toggle is stored, but detection is forced by the normal and idle loops. Raid Protection runs inside its trigger window in order: NPC, forced training, forced Smithy research, then market send of all resources. Dodge sends immediately or N minutes before landing, reads all home t1–t10, optionally the hero, and sends a Raid. It wakes about 15 seconds before due dodge sends, including from normal sleep or logout pauses. Idle checks every four to eight minutes and runs no farming, building, training, or hero actions.

Pilotrav works in cycles, so an interval is a minimum rather than an exact alarm. A normal cycle waits 60 to 180 seconds after account work. Saved settings are loaded on the next cycle, but page loading, earlier work, game queues, resources, troops, merchants, and Travian rules can defer an action. A log records the observed game flow, not a permanent result. Review the relevant Travian page after important sends. No tool is risk-free and no configuration removes account risk.

Military settings share several practical timing rules. The bot normally checks an account’s settings at the beginning of a cycle. It then handles time-sensitive dodge and folder work before incoming attack detection, farm lists, hero work, and the per-village work that includes raid protection, research, training, and Hospital. Consequently, a later action can be delayed by an earlier eligible action or by a slow game page. A configured feature with no available troop, resource, merchant, building, button, or valid target is skipped and reconsidered later according to its own timing rules.

Use the Logs page to separate a configured intention from a completed game action. A message that says not due, unavailable, skipped, or waiting normally leaves configuration in place; it does not mean Pilotrav will reserve troops, resources, or merchants for that feature. Conversely, a confirmed send consumes the game resources that Travian accepted, which can affect later work in that same or the next cycle. Avoid conflicting plans, verify the first real action for a new setting, and keep enough time between a planned action and a game deadline. Telegram notices require a connected chat and the matching notification type. The bot acts through the account’s own browser session, but that does not override Travian’s server checks or its game rules.

Settings

Setup in 5 steps

1. Connect Telegram and enable Incoming Attack notifications.

2. Choose a cycle delay suitable for the desired response.

3. Enable only feasible Raid Protection actions.

4. Choose a safe dodge coordinate and hero choice.

5. Keep bot running and confirm detection in Logs.

Requirements

Limits and what it does not do

Common problems

“Incoming attack: ” confirms detection. “Raid protection triggered - village N, attack in M min” starts configured actions; “Raid market: no merchants available, skipping” and “target coordinates not set, skipping” explain failures. Dodge logs include “Troop evasion scheduled”, “Troop evasion sent”, “no troops at home”, and “target coordinates are missing or invalid”. “bot is inactive ... timely dispatch may not be possible” means no reliable response was possible.

Related features

Folder defense and resource send · Farm lists · Troop training and research

Last updated: October 26, 2026