Travian Hero Oasis Raids

What it does

Oasis List has hero mode and Oasis Farm Mode. Hero mode sends one hero raid per interval; Farm Mode sends configured troops without the hero to eligible oases in a round. Both use live garrison count, animal exclusions, and target troops. Nearby Oasis Scanner discovers candidates. Battle estimate is a cautious hero-mode filter, not a combat guarantee.

How it works

Hero targets are considered least-recently-sent first. The hero must be known, alive, and not away unless troops-only fallback is on. Garrison is read from the tile immediately before a send; min/max count and excluded animals can skip it. A success sends one target and starts the fixed hero interval. Farm Mode reads source troops, checks every target, and schedules a random round interval even if none send. Scanner needs the live browser: radius is 1–12, UI default 6, and up to 625 square tiles. It tries a quick hover scan first, otherwise reads tiles in 45-second partial batches. Battle estimate requires readable hero strength and health, skips predicted loss or health below threshold, and intentionally ignores items and some bonuses.

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. Place the hero in the source village and ensure a Rally Point exists.

2. Scan nearby oases or add coordinates and troops.

3. Choose hero or Farm Mode and set garrison filters.

4. Optionally enable Battle estimate with a health floor.

5. Save, start the bot, and inspect sends and skip logs.

Requirements

Limits and what it does not do

Common problems

“Bot is not running - start the bot first to scan” or “Bot is currently logged out/asleep - try again in a few minutes” blocks scans. “A scan is already running for this account - wait for it to finish” means wait. Raid skips include “garrison too strong”, “too weak”, and “contains excluded animal”. “hero strength/health unavailable; not sent because combat prediction is enabled” needs readable hero state. “Hero oasis raid: could not send to (x,y) - ” is retried later.

Related features

Farm lists · Custom Farm List · Hero adventures and attributes

Last updated: October 26, 2026