Travian Guides

Travian alliance guide

Travian Chiefing And Conquering: Expansion Guide

Learn Travian chiefing and conquering strategy. This guide covers senator and chief usage, loyalty timing, target selection, and defending against enemy conquest.

The Core Difference Between Chiefing and Conquering

In Travian, the terms "chiefing" and "conquering" are often used interchangeably, but they represent two distinct phases of the same operation. Chiefing refers to the act of sending a Senator or Chief to a target village to reduce its loyalty to zero. Conquering is the follow-up strike that actually takes control of the village once the loyalty has been depleted. Understanding this distinction is critical because it dictates how you allocate troops, time, and coordination resources.

Many alliance leaders make the mistake of treating a chiefing operation as a single event. In reality, it is a multi-wave process that requires precise timing, backup plans, and a clear understanding of the defender's capabilities. A successful conquer is not the result of one lucky hit; it is the product of a well-rehearsed system that your entire alliance can execute under pressure. Your goal is to make this process so routine that your members can run it in their sleep.

Key Takeaways

  • Chiefing reduces loyalty; conquering captures the village. They require separate, coordinated waves.
  • Loyalty drops by 20-30 per successful Senator/Chief attack, and it regenerates over time. Timing is everything.
  • Target selection is 80% of the battle. Choose villages based on strategic value, not just proximity or resources.
  • Defending against conquest requires active scouting, fake-raid patterns, and rapid reinforcement protocols.
  • Coordination tools like Travian Bot streamline communication without automating any in-game actions.

Understanding Loyalty Mechanics and Regeneration

Every village in Travian has a loyalty score ranging from 0 to 100. A Senator or Chief attack that reaches the village successfully will reduce this score by a random amount, typically between 20 and 30 points. When loyalty hits zero, the village is considered "empty" and is vulnerable to a normal attack from any player, which will then claim it as their own. However, loyalty does not stay at zero indefinitely. It regenerates at a rate of roughly 1 point per hour, meaning you have a very narrow window to land the final conquer attack.

This regeneration mechanic is the single most important factor in your timing strategy. If you send your Chief too early, the loyalty may regenerate before your conquer wave arrives. If you send it too late, the defender may have time to reinforce or counter-attack. The standard approach is to send multiple Chief waves in rapid succession, each one reducing loyalty further, followed immediately by a conquer wave. For a village starting at 100 loyalty, you will typically need four to five successful Chief hits to bring it to zero.

Senator vs. Chief: Choosing Your Tool

The Senator is the Roman unit for conquest, while the Chief serves the same role for the Gauls and Teutons. While their function is identical, their practical use differs based on the civilization's overall military strategy. Roman Senators are slower but can be paired with the powerful Roman infantry for defense during the operation. Gaul Chiefs are faster and benefit from the Gaul's defensive bonuses, making them harder to intercept. Teuton Chiefs are the most aggressive, fitting the Teuton raiding playstyle.

Your choice of which unit to use is less important than how you deploy them. A single Chief is rarely enough. You should aim to have at least three to four Chiefs available for a single target, allowing for multiple waves and a margin of error if one wave is intercepted. Alliance leaders should maintain a shared roster of available Chiefs across members, so that no single player bears the full burden of a conquest operation. This also spreads the risk if one player comes under attack.

Action Checklist

  • Audit your alliance's available Senators and Chiefs. Create a shared spreadsheet or channel for this.
  • Ensure each Chief is accompanied by a sufficient escort. A Chief alone is a free kill for any defender.
  • Pre-position Chiefs at a forward base or rally point within striking distance of your target region.
  • Assign a dedicated "conquer coordinator" for each major operation to track wave timing.

Target Selection: The Art of Strategic Value

Too many alliances conquer villages simply because they are close to their own borders. This is a mistake. The best targets are those that provide a tactical advantage: a village that blocks an enemy's expansion route, a high-crop village that can sustain a large army, or a village that serves as a staging point for future operations. Before you commit resources to a conquest, ask yourself what this village does for your alliance's overall position on the map.

Another critical factor is the defender's activity level. A village owned by an inactive player is a gift, but it is also a trap if you assume the owner will remain inactive. Always scout the village multiple times over a 24-hour period to gauge activity. Look for signs of life: resource production changes, troop movements, or recent building upgrades. If the defender is active, you must assume they will call for reinforcements from their alliance, and your operation must account for that.

Example

Your alliance is planning to push into a contested valley. You have two potential targets: Village A is 3 tiles from your border, has low crop, and belongs to a solo player who logs in daily. Village B is 15 tiles away, has 50% higher crop, and sits on a crossroads that would cut off enemy reinforcement routes. The correct choice is Village B, despite the longer march time. The strategic value of cutting off enemy movement far outweighs the convenience of a nearby target.

Building the Chiefing Wave: Composition and Escort

A Chief or Senator should never travel alone. The escort's primary job is to ensure the Chief reaches the target village. This means the escort must be strong enough to defeat any defending troops or, at minimum, survive long enough for the Chief to complete its mission. A common mistake is sending a massive army with the Chief, which is wasteful and slows down the operation. Instead, send a balanced escort that can handle typical defense forces, and rely on speed to avoid larger enemy stacks.

The composition of your escort depends on the defender's known troop types. If the target is a Teuton player, expect heavy infantry and send a mix of swordsmen and cavalry. If the target is a Roman player, expect a strong defensive wall and consider sending catapults to soften the defenses in a prior wave. The key is to scout thoroughly before you commit. A failed Chief wave is not just a loss of troops; it is a warning to the defender that they are being targeted, giving them time to prepare.

Timing the Loyalty Drop and Conquer Wave

Once your Chief waves are in motion, the timing of the conquer wave is everything. The standard formula is to send your Chief waves so that they arrive at the target village in quick succession, ideally within minutes of each other. The final Chief wave should arrive just before your conquer wave, ensuring that loyalty is at zero when the conquer attack lands. This requires precise coordination and a shared clock among all participating players.

To execute this, you need to calculate travel times for each wave and stagger their departure times accordingly. This is where a dedicated coordinator is essential. They must track each wave's arrival time and adjust the conquer wave's departure to match. A common error is sending the conquer wave too early, resulting in a failed capture because loyalty had not yet reached zero. Another error is sending it too late, allowing loyalty to regenerate by a few points and again failing the capture.

Action Checklist

  • Use a shared timer or countdown tool that all participants can see in real-time.
  • Send Chief waves at 2-3 minute intervals to ensure loyalty drops sequentially.
  • Calculate the conquer wave's travel time and send it so it lands 1-2 minutes after the final Chief wave.
  • Have a backup conquer wave ready from a different player in case the primary one is intercepted.

Defending Against Enemy Conquest

Defending against a chiefing operation is a reactive game, but it can be won with the right protocols. The first line of defense is intelligence. If you know an enemy is targeting a village, you can reinforce it with troops and, more importantly, with your own Chiefs. A defending Chief can counter the attacker's loyalty reduction by increasing the village's loyalty back up, effectively resetting the attacker's progress. This is a powerful defensive tool that many alliances underutilize.

The second line of defense is disruption. If you cannot stop the Chief waves, you can disrupt the conquer wave. This means intercepting the conquer attack with your own troops, either by attacking it en route or by having a strong defense in the target village. Even if the loyalty reaches zero, a well-defended village will repel the conquer attack, and the loyalty will begin to regenerate. The key is to never let the enemy have a clean window to land their final blow.

Example

Your alliance detects that an enemy is sending three Chief waves to one of your border villages. Instead of panicking, your coordinator dispatches a single Chief from a nearby village to arrive just before the enemy's first wave. This defensive Chief raises the village's loyalty by 20 points, meaning the enemy's three waves will only reduce it to 40 instead of zero. Their conquer wave arrives, finds the loyalty at 40, and fails. You have successfully defended the village with minimal resources.

Handling Multi-Village Conquest Operations

Advanced alliances often run simultaneous conquest operations on multiple villages to overwhelm an enemy. This is a high-risk, high-reward strategy that requires exceptional coordination. The primary benefit is that the defender cannot reinforce all villages at once. The primary risk is that if one operation fails, it can compromise the others by alerting the enemy to your broader strategy. Therefore, multi-village operations should only be attempted when you have a significant numerical advantage.

When running multiple operations, stagger your timings so that the first conquest completes before the second begins. This allows you to use the newly conquered village as a staging point for the next operation, reducing travel times and creating a snowball effect. It also prevents the enemy from focusing all their defensive efforts on a single moment in time. A well-executed multi-village operation can break an enemy alliance's morale and force them to retreat.

Post-Conquest: Securing and Developing Your New Village

Capturing a village is only the beginning. In the immediate aftermath, the village is vulnerable. Its loyalty is at zero, and it has no defenses to speak of. You must immediately send a defensive force to the village to protect it from counter-attacks. You should also begin rebuilding its infrastructure, starting with the rally point, warehouse, and resource fields. A conquered village is a liability until it is fully integrated into your alliance's network.

Long-term development is equally important. A village that is not developed is a drain on your alliance's resources. Assign a dedicated player to manage the new village, or integrate it into an existing player's portfolio. Prioritize building up the crop production to sustain a defensive garrison, and construct a wall if the civilization allows it. The goal is to turn the conquered village from a strategic asset into a fortified stronghold that can support future operations.

Action Checklist

  • Send a defensive garrison to the new village within 10 minutes of the successful conquer.
  • Assign a responsible player to manage the village's development and report progress to the alliance.
  • Prioritize rebuilding the rally point and resource fields before any other structures.
  • Add the village to your alliance's map and defense planning tools immediately.

Where Travian Bot Fits

Executing a chiefing operation requires flawless timing, constant communication, and a shared situational awareness across your entire alliance. This is where a coordination tool like Travian Bot becomes invaluable. Travian Bot is a Discord bot designed to support alliance leaders and coordinators by centralizing information and automating communication workflows. It does not control game accounts, does not send troops, and does not take any in-game actions. Its purpose is purely organizational.

With Travian Bot, you can create dedicated channels for each conquest operation, where coordinators can post wave timings, travel times, and target details. The bot can be configured to send automated reminders for upcoming waves, ensuring that no one misses a critical departure time. It can also maintain a shared database of available Chiefs and Senators across the alliance, making it easier to allocate resources. By reducing the administrative burden, Travian Bot allows your leaders to focus on strategy rather than logistics.

Common Mistakes and How to Avoid Them

The most common mistake in chiefing operations is underestimating the defender. Even a seemingly inactive player can have a well-defended village with hidden troops. Always scout multiple times and assume the worst. Another frequent error is poor communication. If your Chief wave arrives but your conquer wave is delayed by even five minutes, the entire operation can fail. This is why a dedicated coordinator and a reliable communication tool are non-negotiable.

Finally, many alliances fail to plan for the aftermath. They celebrate the conquest and then leave the new village undefended, only to lose it to a counter-attack within hours. A conquest is not complete until the village is secure and integrated. Always have a post-conquest plan ready before you even send the first Chief wave. This includes identifying the defender, assigning a new owner, and pre-positioning defensive troops.

Example

An alliance spent three days planning a conquest of a key enemy village. They executed the Chief waves perfectly, and the conquer wave landed successfully. However, they had not arranged for a defensive garrison to arrive immediately after. Within two hours, the enemy alliance launched a counter-conquest, and the village was lost. The entire operation was wasted because the post-conquest phase was ignored. This is a classic failure that can be avoided with simple foresight.