Travian Hero Adventures and Attributes

What it does

Hero adventures are task-driven; Auto Hero Attribute is a separate account setting. An active adventure task allows the bot to send a healthy, available hero to the first enabled adventure. Attribute automation assigns new points according to four numeric values. Neither action heals or revives a hero.

How it works

Hero state is read each cycle and cached for three minutes, or 30 seconds when no adventures are available and the hero is home. Adventure is skipped when data is missing, hero is dead or away, no row exists, or health is unknown or under the threshold. The account Min. Health Threshold overrides task minimum. The first enabled displayed row is clicked and confirmed; reward and distance are not compared. When points exist, attributes are opened. If requested values fit, those exact values are assigned; if they exceed points, all are scaled proportionally and rounding remainder goes to Resources; all-zero gives every point to Resources. Existing points are never reset. heroAttributeMode is stored but does not change the engine calculation.

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. Add an Adventure task and choose a health floor.

2. Let the bot read hero state.

3. Enable Auto Hero Attribute if desired.

4. Enter four desired allocations; use all zero for Resources only.

5. Verify first dispatch and save in Logs and Travian.

Requirements

Limits and what it does not do

Common problems

“Hero task skipped: health 35% < min 40%”, “hero is dead”, “hero already on adventure”, and “health unknown, skipping to be safe” explain skips. “Hero: adventure list is empty” means none is available. “Adventure: rows found but button missing” is retried. Attribute logs include “Hero attributes: no points available, skipping”, “save button not found”, and “Hero attributes saved - power:+x attack:+y defence:+z resources:+w”.

Related features

Hero oasis raids · Troop training and research · Custom Farm List

Last updated: October 26, 2026