Second Strike: Read the Battle Report First

The battle report from your first strike is not an order to attack again. Sending the same formation is easy; the hard part is separating what you learned from what may no longer be true. The defender may have healed troops, received reinforcements, changed gear, or prepared to activate a shield. In Lords Mobile, a good second strike depends on more than how many troops you lost. You need to know what evidence supports the risk you’re taking.

Define the First Strike’s Purpose

Before planning another attack, ask what the first one was meant to do. Were you trying to finish the target, test its defenses, or evaluate the result of a coordinated rally? The same report can lead to a different decision in each case.

Say your first march lost 30,000 troops and inflicted 45,000 losses. That alone does not mean “hit again.” If the attack was a test, your next job is to check whether the defender became active or changed its defenses. If you intended to finish the target, your remaining troops, available march capacity, and exposure to a counterattack also matter.

Tell your guild the plan before the first strike: “If the report looks good, we’ll hold for a second-march decision. If the target gets reinforced, we stop.” That keeps everyone from charging in with a different assumption as soon as the report arrives. When several players are marching on one castle, the second attack needs its own decision; it is not an automatic continuation of the first.

Read Three Factors in the Battle Report Together

Don’t judge a report by enemy losses alone. Look at your losses, then the defender’s, then the conditions that could change before another hit. The defender may heal wounded troops; the reported losses do not, by themselves, tell you what the second attack will face.

Suppose you lost 80,000 troops and the defender lost 10,000. What you can safely conclude is that this march was costly for you. A poor troop-type matchup, a strong frontline, or another defensive factor could explain it. Those two numbers alone cannot prove which one. Examine the report’s details and identify what you still need to know instead of repeating the march.

Conversely, you might lose 20,000 while the defender loses 60,000. That looks like a better trade, but don’t expect the same result if reinforcements arrive. Ask three quick questions:

• Cost: Are my losses acceptable relative to the losses I inflicted?
• Evidence: Does the report actually show the enemy frontline or troop distribution, or only the outcome?
• Freshness: Has the target’s behavior changed since the report arrived?

Base Your Formation Decision on Evidence

The troop-type counters are straightforward: Infantry counters Ranged, Ranged counters Cavalry, and Cavalry counters Infantry. But using that relationship requires reliable information about which troops are at the front. Seeing an overall troop distribution is not the same as confirming the frontline.

For example, if sufficient report detail or a current scout report confirms Ranged troops at the front, you can consider an Infantry-heavy counter. Against a Cavalry frontline, consider Ranged; against Infantry, consider Cavalry. Your troop numbers, research, gear, and the chance of reinforcements still affect the outcome. Finding a counter type does not guarantee a win.

If the first report shows 50,000 losses on your side and 15,000 on theirs but lacks useful defensive detail, switching your entire march to another troop type is a guess. Get fresher intel before deciding, or stop if the uncertainty is too high. Pretending the report contains information it does not show can cost more than the first attack with the wrong formation.

Record the formation you used for the first strike alongside its report. If another guildmate prepares a different march against the same target, they need to know which troop type led the first attempt. Otherwise, when comparing reports, you cannot tell whether the target changed or your attacking formation did.

Recheck the Target Before the Second Wave

The first report describes the castle when you hit it, not necessarily a few minutes later. Imagine the report arrives at 14:00 and you prepare the next march at 14:03. In those three minutes, the defender could become active, request guild reinforcements, or change gear. Those times are examples; the point is to run a fresh check before deciding.

First, confirm that the target is still viable. Then compare any new scout intel and your guild’s observations with the first report. If the troop distribution changed, don’t carry the first strike’s loss ratio straight into the second. If reinforcements arrived, the guide to rallies after reinforcements covers that decision in more detail. You can find other formation topics in the blog.

Set a simple stop condition: “If our frontline intel is no longer current, the second march does not launch.” This matters most when the first attack went well. A favorable report can make you overconfident at exactly the wrong moment. The defender may be able to activate a shield and close the window, but don’t burn troops on an unverified formation just to beat the clock.

Give the Guild One Go-or-No-Go Call

The costliest second-strike mistake is three players reading the same report and following three different plans. One may interpret 20,000 losses as a reason to continue while another has spotted fresh reinforcements. Before anyone marches, an R4/R5 or attack coordinator should issue one clear call: Continue, reassess, or stop.

• Continue: The first report is clear, the target’s defenses have been rechecked, and the planned counter type is confirmed.
• Reassess: The report looks favorable, but frontline intel is missing or the target’s situation has changed.
• Stop: The first march suffered heavy losses, or new reinforcements have undermined the current plan.

For instance, two players are preparing to hit the same target. The first report shows 25,000 losses on your side against 55,000 on theirs. If the target becomes active before the second player launches, “the first report was good” is not a go order. Share the latest status and change the formation or target if needed.

Guilds using LordsRally for enemy castle tracking can watch shield changes and target activity through group alerts. The !track command, listed under commands, tracks changes in might, gear, and shield status. Neither alerts nor tracking replace the battle report or your in-game judgment: an alert is a cue to check again.

In your next fight, treat the first report as evidence for a decision, not an order to hit again. To see how your guild can share alerts, visit features and contact our team.