Rally Reinforcements: Troops and Arrival Timing

When a guild sees a rally warning, the first reaction is often: “Everyone send troops!” Sometimes that saves the castle. Other times, it piles more troops into a defense that cannot hold. Good reinforcement means getting the right troops to the right castle before the first hit—not sending the largest possible number.

This guide is not about which formation the defender should select. It is about how the guild supports that formation. If three members can reinforce, discuss their troop types, march times, and how much strength the castle may have left after the hit—not just their combined troop count.

First decide: Is holding the castle worth it?

Before calling for reinforcements, an R4 or defense coordinator should answer three questions: Is the defender online? Where are their troops and leader? Is holding this castle actually the goal? Without those answers, sending reinforcements is a guess, not a plan.

For example, if the defender is online, can check their formation, and two nearby guildmates are ready, you can consider defending. If that player is offline, nobody knows which troops are inside, and most members are far away, stop the “everyone send troops” call. Try to reach the player, secure troops where possible, and check whether shielding is an option. Fury status and in-game restrictions may affect that option; do not treat a shield as a guaranteed fix.

For a closer look at the defender’s frontline choice, see the rally defense formation guide. You can find other war topics on the blog; here, we will focus on the reinforcement decision.

Don’t confuse the rally timer with arrival time

A rally’s assembly time and its attack march time are not the same. Each reinforcing member’s own march time is a third timer. Looking at the assembly countdown and saying “I can make it” does not tell you exactly when the attacker will leave or reach the target.

Here is a hypothetical calculation: The rally has 80 seconds left to assemble, and you estimate its attack march will take about 25 seconds. That gives you a rough 105-second window before the first hit. A member whose reinforcements take 120 seconds will miss that hit under this estimate. The attack march estimate can also change. Once the rally launches, check its displayed arrival time again and share the updated timing with the guild.

If two nearby members have 35- and 50-second marches while a third needs 120 seconds, do not call the third just to raise the troop count. Late troops cannot absorb the first hit and need a separate decision. If the rally speeds up or the defender relocates, recalculate everything.

LordsRally’s rally warning can bring the development into your WhatsApp or Telegram group so you can start that check. You should still use the current in-game arrival time for the decision. You can inspect the attacking castle’s visible gear with !equip, but a gear image alone does not prove which army was sent. See the supported commands and features.

Choose reinforcements for the frontline

In Lords Mobile, the basic counter cycle is: infantry counters ranged, ranged counters cavalry, and cavalry counters infantry. This is a starting point for reinforcement planning, not a win guarantee when you do not know the attacker’s actual composition. Confirm the defender’s formation and which troops remain in the castle, too.

Suppose you have reliable information that the attacker will use mostly cavalry. Calling for “infantry from everyone” ignores cavalry’s advantage over infantry. You can discuss a ranged counter and a suitable defender frontline. But cavalry gear alone does not confirm the incoming army: the opponent can change gear or send different troops.

If the attack type is unknown, do not ask five members to send 100,000 random troops each. First, ask the defender for the castle’s current troop distribution. A reinforcing member’s own march formation does not automatically change the defender’s castle formation. The call should therefore be “send this troop type according to the defender’s plan,” not simply “send troops.”

Look beyond the troops that can fight. The defender’s hospital capacity and willingness to absorb losses matter, too. Holding one hit at the cost of leaving three members unable to join later fights may be a poor trade for the guild. When you are unsure about the matchup, close the information gap before adding more troops.

Assign roles in hive defense

When everyone types at once in the hive, the most important message gets buried. Pick one coordinator and split four jobs: the defender reports the castle’s status, an observer tracks the rally timing, reinforcers report troop types and march times, and the coordinator announces the decision.

If six members are online, they do not all need to reinforce. Two nearby members prepare troops that can arrive in time; one watches the attack arrival; the defender reports their formation and remaining troops; the others check their own castles’ safety. That way, defending one rally does not leave the rest of the hive exposed.

Keep calls short and verifiable: “Members who can send infantry, post your march time. Do not launch yet.” Then: “The 35- and 50-second marches launch; the 120-second march waits.” Those two messages are more useful than a vague “urgent help” call. If the defender shields at the last moment or you decide not to hold, check the status of troops already marching. Do not send fresh reinforcements based on an outdated plan.

A practical R4/R5 rule: Put the target, requested troop type, latest acceptable arrival time, and decision-maker in one message. Handle player identities and coordinates only in the relevant guild channels, not in public posts.

What should you do after the first hit?

A successful defense does not mean the same setup will hold a second rally. After the first hit, check the defender’s remaining troops and hospital status, plus the losses taken by reinforcing members. Use the battle report to test your first estimate; do not treat it as certain information about the next attack.

For example, if you held the first rally but the defender’s frontline took heavy losses, do not automatically repeat the same formation and reinforcement call. The defender should reassess the formation, while reinforcers report their remaining troop types and new march times. If the opponent switches troop types, the first defense may give you false confidence.

Use this quick check between hits: read the report, confirm remaining troops, calculate the new rally’s arrival, then decide again whether to hold or pull back. Even if several minutes separate the attacks, do not act on an old screenshot. The second decision needs current information of its own.

If you want a clear process from rally warning to defense decision for your guild, get in touch with LordsRally.