Home/Docs/Military & Hero/Travian Folder Defense and Resource Send

Travian Folder Defense and Resource Send

Pilotrav folder plans coordinate multiple account villages toward one target. Defense plans schedule reinforcement sends to arrive before a user-entered UTC+3 arrival time. Resource plans send calculated surplus through Marketplaces inside a time window. Both preview from saved snapshots, then recheck essential live values before sending.

Requirements

  • Folder accounts with usable bot sessions.
  • Defense: Rally Point, recent troop snapshot, target time.
  • Resources: Marketplace, merchants, and current stock.

Limits

  • Does not discover attacks or choose targets.
  • Snapshots can be stale; live shortfalls are skipped.
  • Defense-value selection is capped at 500.
  • Resource plans do not preserve later construction needs.
  • Resources are sent to coordinates, not a village ID.

What it does

Folders coordinate accounts. Defense plans send reinforcement from folder villages to a target coordinate before a user-entered arrival time. Resource plans send surplus resources through Marketplace at random moments in a window. You choose targets and timing; neither reads an enemy attack or selects a target.

How it works

Defense preview uses last troop snapshots, map wrap distance, unit speed, server speed, and a 10% buffer. It excludes hero, settlers, and chiefs, can keep a percentage at home, and supports all, random, or defense-value selection. Arrival must be at least five minutes away and only one active plan exists. Execution wakes about 15 seconds before due, re-reads troops, verifies the reinforcement radio, reads actual travel on confirmation, and skips late sends. Resource preview reserves the larger of absolute reserve and floor(storage capacity times keep percent), flags snapshots older than 30 minutes, and randomizes each send after minimum delay inside the window. Execution re-reads resources, clamps by current stock and merchant capacity, verifies coordinates on form and confirmation, then sends. Resource plans can cancel while scheduled or running; running defense plans cannot be cancelled through the API.

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

UI labelWhat it doesDefaultRange
Attack arrival timeDefense arrival in UTC+3RequiredAt least 5 minutes future
Who sendsAll, Random N, or defense valueAll eligibleValue 1–500
Send timing / Safety marginDefense timing and bufferAs soon as possible / 180 sMargin 0–3600
Keep at home (%)Troop or resource reserve00–100
Window / Minimum delay (minutes)Resource send timingRequired / 1Window 1–1440; delay 0 to window
Keep at home per resourceAbsolute resource reserveEmptyOptional amounts

Setup in 5 steps

1. Group accounts in a folder and ensure their bots can run.

2. Enter target and timing in Defense or Resources.

3. Preview and inspect stale, late, and unavailable rows.

4. Set margin or reserve and create one plan.

5. Monitor sent, skipped, and failed statuses.

Requirements

▸Folder accounts with usable bot sessions.
▸Defense: Rally Point, recent troop snapshot, target time.
▸Resources: Marketplace, merchants, and current stock.

Limits and what it does not do

▸Does not discover attacks or choose targets.
▸Snapshots can be stale; live shortfalls are skipped.
▸Defense-value selection is capped at 500.
▸Resource plans do not preserve later construction needs.
▸Resources are sent to coordinates, not a village ID.

Common problems

Defense logs include “Defense support skipped: village N, reason missed_window”, “insufficient_troops”, or “too_late”; failures include “event_type_missing”, “event_type_unverified”, and “confirm_button_missing”. “Restarting browser for defense dispatch” is an expected wake-up. Resource logs include “Resources sent: village N, wood .., clay .., iron .., crop ..” and “Resource dispatch skipped” with reasons such as no_market, no_merchants, target_mismatch, or confirmation_missing.

Related features

Attack alerts and raid protection · Farm lists · Farm lists

Frequently asked questions

When does travian folder defense and resource send act?

It acts only while the account bot is running and reaches its check in the normal cycle. The chosen interval is a minimum, not a precise deadline. Other village work, page loading, resource availability, troop availability, and game-side requirements can make an eligible action later or skip it.

Does a successful log line guarantee the result?

No. A success line means Pilotrav reached the expected page flow or submitted the requested action. Troops, resources, merchants, queues, timing, and server rules can still change the resulting game state. Check Travian and Logs after important military actions rather than treating a configuration as a guarantee.

Does this remove Travian account risk?

No tool is risk-free. This documentation describes product behaviour, not a promise of safety, availability, or game results. Choose targets and intervals you accept responsibility for, review logs regularly, and stop or adjust automation when the game state needs your attention.

Related docs

Travian Attack Alerts and Raid ProtectionTravian Farm List AutomationTravian Farm List Automation

Last updated:

Ready to try Pilotrav?