Safety & Anti-Detection
The honest rundown: Travian's Terms of Service forbid automation, every bot carries ban risk, and no one can promise immunity. Here is exactly what Vangrd does to minimize detection — and what it cannot promise.
Using any bot violates Travian's Terms of Service. Most Vangrd users never see a sanction, but reports from other players, unrealistic activity, or Travian policy changes can always lead to one. If zero risk is a hard requirement, do not use automation — anyone's, not just Vangrd.
Defense in layers
Every agent runs an isolated Chromium session with its own viewport, timezone, language, and user-agent. Nothing is injected into the game and no memory is patched.
Each Agent uses one residential or mobile IP and stable fingerprint. Linked gameworlds share both while their cookies and runtime remain isolated.
Configurable weekly availability grids with presets like 24/7, work hours, night shift, or weekends. The account goes offline during sleep windows instead of acting round-the-clock.
Every farm run, build click, and page visit has a configurable minimum delay plus random jitter so timings never look mechanical or perfectly periodic.
Between tasks, Vangrd occasionally visits ordinary pages — reports, messages, statistics — instead of repeatedly hitting the same endpoint a player never would.
Cookies, local storage, and session state live inside each agent. No shared credentials, no shared cookies across accounts.
Agents & gameworld isolation
Travian tracks account activity at the network level. Gameworlds linked to one Agent intentionally share one network identity, fingerprint, and schedule.
Vangrd keeps each linked gameworld's cookies, browser storage, tasks, and runtime isolated. Use separate Agents when gameworlds must present different network identities.
Each Agent uses one dedicated residential or mobile IP and stable fingerprint. One gameworld is included; additional linked gameworlds cost €1.99 per 30 days before tax.