Travian Auto Celebration

What it does

Auto Celebration is the Town Hall culture-point action. When enabled, it opens Town Hall gid 24, waits if a celebration is running, then starts the preferred available celebration. Prefer large celebration tries large first and falls back to the other available type. It is the only culture-point automation here.

How it works

The first eligible pass checks Town Hall, then waits two hours before another village check. It needs a Town Hall and a startable game action. On resource error, enabled help reads cost, stock, and capacity. It first uses exact missing hero-bag resources. With NPC help, it verifies combined total can cover cost before spending 3 gold, then distributes for the cost. If capacity cannot hold cost, or total cannot cover it, it waits without an NPC trade.

The bot works in cycles, not finish-time alarms. A normal cycle sleeps for a random 60 to 180 seconds after all villages; the baseline uses 240 to 600 seconds. Between villages it waits 2 to 8 seconds, or 5 to 15 seconds in the baseline. Account settings reach a running bot immediately. Village settings have a five-minute cache, cleared when the Village Settings card is saved. Task edits are loaded after a complete village pass, so a change made while sleeping can take about two cycles to take effect. Refresh starts the next cycle sooner but does not itself reload tasks.

Each village pass reads current state first. Its economy order is Auto NPC, Auto Add Cropland, Auto Celebration, trade routes, settler training and sending, then build tasks. Earlier work can therefore delay later work. Displayed resources and queues are the last state read, not a promise of the next game state. Game automation carries risk; no setting guarantees a game result or eliminates account risk.

When reading results, separate a completed game action from a configured intention. A success log means the bot reached the relevant page and the action entered the expected game flow; it does not make later state permanent or exempt from game rules. A wait message usually preserves configuration for a later cycle. A temporary skip lets other eligible work be considered where queue logic allows it. A failed click can stop lower-priority building work for that pass because strict priority protects resources intended for earlier work. Review the game page as well as logs after important actions.

The bot does not wake exactly when construction finishes. It discovers a finished action during the next cycle, so a gap can be roughly a cycle plus per-village delay. The village list refreshes on periodic re-login, normally every 60 to 120 minutes and 120 to 240 minutes in the baseline, or after restart. A village founded while the bot runs is therefore not immediately processed. Configure clear priorities, avoid conflicting automation, and give one change time to appear before adding another.

Settings

Setup in 5 steps

1. Build a Town Hall.

2. Enable Auto Celebration.

3. Choose large preference.

4. Choose hero inventory and NPC help.

5. Save and review the next eligible log.

Requirements

Limits and what it does not do

Common problems

“Celebration: celebration started in village v” confirms start. “village v — ongoing: ...” means wait. “village v — insufficient resources: ...” means add resources or review help. “warehouse/granary capacity cannot hold the cost (...)” means raise storage. “celebration could not start” means inspect Town Hall requirements.

Related features

Second village and settlers · NPC trading · Village settings

Last updated: October 26, 2026