Rally Filling: Troop Types and Counter Formations

When a target’s shield drops, having everyone in the guild send troops at once can feel like the right response. But if the rally leader is preparing a cavalry attack while two players send infantry out of habit, a full rally is not necessarily a well-planned rally. In Lords Mobile, an offensive rally depends on more than the participants’ might: what you know about the target, how well the troops fit the plan, and the formation the leader chooses all matter.

This guide is about filling an offensive rally, not defending one. The goal is not to prescribe one ‘perfect setup’ for every target. It is to help you decide what information to check, give your guild clear instructions, and adjust after the first hit.

Choose the Attack’s Objective Before the Target

Instead of opening a rally with ‘everyone fill,’ state the objective in one sentence: What are we trying to accomplish with this attack? Trying to burn a castle in one hit is different from testing its defense before the next move. Is the target’s leader inside? Is the castle receiving reinforcements? Does the player appear active? An expired shield alone is not enough reason to attack when those questions remain unanswered.

Suppose you find two unshielded castles with similar might. For the first, a recent battle report and current scout report help you identify the dominant defensive troop type. For the second, you have only an equipment image. You can build a counter-troop plan for the first target; you should not infer the second target’s exact troop composition from its gear. Equipment hints at intent; it does not prove how many troops are inside.

Before calling the rally, the leader should give the guild three things: what is known about the target, the requested troop type, and the attack’s objective. Rather than just saying ‘send cavalry,’ say, ‘Based on what we know about the defense, we’re trying a cavalry-heavy attack; if reinforcements arrive, we’ll reassess.’ If your information is weak, review available in-game scouting and battle reports first. Don’t promise a win when the result is uncertain.

The Biggest Single-Troop Fill Mistake: Assuming

A single-troop-type fill is not mandatory for every offensive rally. It is a coordination method for an attack built around one troop type. If the leader plans a cavalry-heavy hit, participants who add infantry or ranged troops according to personal preference change that plan. A mixed-troop attack can also be deliberate; the problem is creating a mix by accident.

Picture a rally filled by five players: three send cavalry and two send infantry. The rally looks full, but its troop distribution is not what the leader expected. The fix is straightforward: name the troop type in the call, have each player check what they sent, and have the leader review the fill before the march launches. A quick ‘cavalry / sent’ confirmation in guild chat beats silently sending the wrong troops.

Quantity matters as much as type. If a member sends fewer troops than planned, don’t assume someone else will make up the difference. Check the actual fill and decide whether to attack based on that. Don’t add siege troops out of habit, either. If they are not part of the plan, say so in the fill instructions.

Plan Counter Troops and Formation Together

Keep the basic Lords Mobile troop counters in mind: infantry counters ranged, ranged counters cavalry, and cavalry counters infantry. That is a starting point, not a guarantee of the battle’s outcome. The target’s formation, troop mix, reinforcements, and battle buffs also matter. Before saying ‘I saw infantry, so I sent cavalry,’ ask: ‘How reliable was what I saw?’

For example, a current scout report or reliable battle report points to an infantry-heavy defense. A cavalry-heavy attack is a reasonable candidate. But if the opponent receives reinforcements or changes their defense, sending the same rally based on old information is risky. The rally leader should consider the offensive troop choice and formation together. Participants should not assume that changing the formation in their own castles substitutes for the leader’s attack plan.

If you also want to work on your defensive frontline, see the rally defense formation guide. Its goal is to hold your castle; here, the goal is to make a sound attack decision against an opponent’s defense. You can find more game-focused guides on the blog.

Match Fill Time to March Time

The right troops cannot help if they fail to reach the rally in time. Before starting it, the leader should consider members’ march times. Players should check whether their marches will arrive, not merely say ‘sent.’ If one member is 40 seconds away from the rally and another is 2 minutes away, you cannot rely on both under the same timing constraints. Those times are examples; check the actual times on your game screen.

Teleporting closer can shorten the distance, but it is not automatically the right move. A player filling beside an enemy hive may be exposed to a counterattack. The rally leader should decide in advance who moves closer and who fills from a safer position. If the target appears active, watch for reinforcements or a counter-rally while the rally is filling.

For short opportunities such as a shield drop, first confirm that the target is still suitable. Guilds using LordsRally can check a shield-drop notification and recent drops with !shield_drops; a notification does not make the battle decision for you. You can explore the relevant tools on the commands page. Immediately before giving the attack order, the leader’s final checks remain the same: target status, actual fill, and whether the marches will arrive.

Don’t Repeat the First Rally Blindly

After the first hit, someone in guild chat will often call for another. But the battle report is your best chance to improve the second attack. Check your troop losses, the opponent’s losses shown in the report, and any visible defensive details. Don’t claim to see a troop distribution the report does not reveal; the first attack does not necessarily expose every troop in the target castle.

Suppose you planned two attacks. The first inflicts heavier losses on your side than expected, and the target holds. Before immediately sending the second rally with the same troop type, check three possibilities: Was your counter-troop estimate wrong? Did the rally contain the planned troop types and quantities? Did the target receive reinforcements during the attack? If the only problem was an incomplete fill, correcting the call may be enough. If the counter matchup was wrong, stop and rethink the setup.

Even if the first hit succeeds, the target’s defense or activity may have changed. ‘The last hit worked’ is not a substitute for current information before the next one. Having an R4/R5 collect reports in one place and assign one person to announce continue / change the setup / stop is safer than letting five players send troops based on separate guesses.

If you want a more organized way for your guild to check targets, explore LordsRally’s features. Always base the attack decision itself on current game information.