How to Read a !scout Scout Report in Lords Mobile: Data That Changes Your Attack Decision

The most expensive mistake before attacking a castle is treating high might as a threat by itself, or assuming low might automatically means an easy target. In Lords Mobile, the real decision comes from reading the troop composition inside the castle, leader status, trap and defensive preparation, and the target’s current activity together. !scout is the command you use to scout a castle, but simply seeing the report is not enough. You need to know which data in that report changes your attack plan.

Reading scout reports correctly breaks the question “can we hit it?” into four clearer questions: Does the target actually have troops worth defending? Which troop type stands out? Is the leader inside? Is this castle suitable for a solo attack, a rally, or a trap that should not be touched at all? In this article, let’s turn !scout data into a decision system from the perspective of a rally leader, R4/R5, or active fighter.

Why You Should Read the !scout Report Before Looking at Might

Might shows the size of a target, but it does not explain the battle outcome on its own. A high-might castle may carry a long history of research, construction, heroes, and troops. On the other hand, among two castles with the same might, one may be empty or lightly defended while the other is ready to receive rallies with millions of troops and a strong wall defense.

That is why your first rule should be: Might builds the target list; the scout report makes the attack decision.

Example scenario: An unshielded, medium-to-high-might castle appears near your guild. Instead of sending a solo attack based on might alone, you first get the report with !scout. If the report shows heavy defensive troop density and a mixed troop composition, you remove that target from the “solo hit” list. If its leader is inside and the report points to rally-scale defense, the target now requires coordination. A rushed solo attack at this stage can create both troop losses and leader risk.

The reverse scenario matters too: if a high-might castle has very few troops to defend with, a major part of that accumulated might may come from research or past development. That kind of report can shift your plan from a rally to a more controlled solo attack. The decision-changing factor is not “how many million might?” but how much of that might is actually converted into defense on the field.

5 Scout Report Details That Change Your Attack Decision

Do not give every line of a !scout result equal importance. The following five data points directly affect the type of attack you choose.

Troop type distribution: Infantry, ranged, and cavalry concentration are the first things to check. Heavy concentration in one type creates a clearer picture for a counter-formation plan. A mixed and crowded troop composition, however, increases the risk of solo attacks in particular.
Total defensive volume: The troop amount shown in the report is the foundation of the “solo or rally?” decision. As the number rises, you should consider not only your own attack power, but also rally participation, leader gear, and the chance that the target will come online during the attack.
Leader status: Whether the leader is inside the castle changes both the reward and risk side of the battle. If the leader is inside, a successful attack can create a prisoner opportunity; but it may also mean the target is more likely to take defense seriously. If your own leader is exposed, check your own shield and rage status as well as the target report.
Wall and trap visibility: If wall durability and defensive tools appear in the report, do not treat them as minor details. Especially against targets that look low on troops, the defensive layer can raise the attack cost more than expected. “Few troops means it will definitely burn” is one of the most common mistakes here.
Resource and reward balance: Visible resources are not a reason to attack by themselves. Burning a castle and gaining profitable resources may not be the same objective. If the value of the resources is weak compared with the risk of rally-level troop losses, the attack is not strategically sensible.

If you can summarize the report with this short sentence, you are reading it correctly: “This target has this type of defense, this leader status, so we attack with this formation at this scale—or we do not attack.”

Solo Attack, Rally, or Skip: A Practical Decision Matrix

After the scout report arrives, use a three-way decision instead of starting a long guild-chat discussion: solo attack, rally, or skip.

For a solo attack, you generally look for this situation: manageable defensive volume, a clear troop composition, low target activity, and limited counterattack risk. Even then, do not choose your formation blindly. Check your own troop composition and leader gear against the dominant troop type in the report.

For a rally, the situation is different: the target’s defense is too heavy for a solo attack, its leader may be inside, or its strategic location may be valuable. Before launching the rally, send the report to the rally leader; saying only “target is open” is not enough. Troop type, estimated defensive scale, activity signs, and the target’s hive support should be included in the same message.

The decision to skip or monitor is not weakness; it is loss control. If there is dense mixed defense, signs of an active target, nearby strong guild support, or insufficient rally participation, delaying the attack produces a better outcome. You can add the target to your watch list and wait for a more suitable shield drop or activity window.

Use this 30-second mini-check before making the call:

Is the dominant defensive troop type clear in the report?
Does the defensive volume exceed the limit for a solo attack?
Is the leader inside, and is that risk worth it?
Could the target be active?
Is the target’s hive, camp, or guild support nearby?
Are your own leader, shield, and rally capacity secure?

If two of these six questions are uncertain, gather more intelligence before giving an attack order.

Cross-Check !scout Results With Other Commands

The best war decision does not come from one screen. !scout gives you a snapshot of the castle’s internal defense; other commands help you understand what happened before and what may happen after that snapshot.

First, use !find to check the target’s guild, position, might, attack power, shield status, and visible activity details. For example, the bot’s castle card arrives in this format:

!find → 🧧 [XYZ][R3] Player (35) · 🟢 ACTIVE · 📍(X:512 Y:340) · 💪 1.10B ⚔️ 160M · 🏆 2 days, 00:49 · ━━ Details ━━ 🔎 Shield Dropped / Might Increased / Equipment Changed · [ Info | Equipment | Track ] buttons.

If the target appears active in this example, the chance of a gear or formation switch during rally preparation increases even if the !scout report looks favorable. Then, use !activity to review the target’s recent movement and !equip to inspect current and historical gear visuals. Sending a blind attack based on an old report against a target that has equipped defensive gear, increased activity, or suddenly changed might is not the right move.

For a deeper read of troop distribution before a rally, also see the guide to solving enemy formations with !comp. The commands page is a practical starting point for using every command by role, while the features page helps you evaluate the bot’s tracking and alert infrastructure.

The Value of 1–3 Seconds During Shield Drops and Rally Alerts

A scout report is valuable when it is accurate; when it arrives at the right time, it can win battles. There is a major difference between reading a report several minutes after a target’s shield drops and preparing your scout in the first seconds. With its event-driven architecture, LordsRally delivers shield drop, active attack, rage, migration, and rally alerts to your group within 1–3 seconds when the event occurs; it does not wait on fixed-interval polling.

This speed makes !scout usage more disciplined. For example, when a shield drop notification arrives, the team can follow this sequence:

Check the target’s guild, location, and status from the notification card.
One player gets the defense report with !scout.
The rally leader evaluates the troop distribution in the report.
Another player checks !activity or !equip for the target’s immediate response potential.
The decision to solo attack, rally, or retreat is finalized in one clear message.

With LordsRally, you can turn each of the 12 smart alerts on or off individually and protect your group from unnecessary messages through might, shield, and activity filters. The system works in WhatsApp and Telegram groups, allowing you to monitor your kingdom 24/7 without keeping a computer on. This is especially valuable for guilds monitoring multiple kingdoms: you can manage a newly migrated castle, a war opportunity in another kingdom, or rally pressure through the same operational setup.

Scout Discipline for R4/R5: How Should You Share the Report With Your Guild?

An R4/R5’s job is not only to run !scout; it is to communicate the report clearly enough that everyone reaches the same decision. Instead of a vague message such as “target is strong,” use a decision-focused summary.

Example reporting template:

Status: No shield; target shows activity signs/does not show activity signs.
Defense: Dominant troop type and defensive density.
Leader: Inside/outside status.
Risk: Nearby hive, possible reinforcements, gear changes, or counter-rally potential.
Decision: Try solo / launch rally / monitor / skip.

This discipline reduces misunderstandings, especially in guilds playing across different time zones. Among LordsRally’s 78 commands are tools for war, kingdom intelligence, migration, tiles, and tracking; however, you do not need to use all of them at once. Combining the right three data points quickly during war is more valuable than trying twenty commands randomly. You can also use the guides in the blog for different war routines.

Frequently Asked Questions

Is !scout alone enough to make an attack decision?

No. !scout provides critical data about castle defense, but target activity, gear changes, shield status, guild support, and location also affect the outcome. For the healthiest decision, cross-check with !find, !activity, and when needed, !equip.

If the scout report shows few troops, is a solo attack definitely safe?

It is not guaranteed. The leader, wall, traps, whether the target is online, and nearby guild support can change the risk. The target may also hide troops, receive reinforcements, or change gear after the report. The longer the time between scouting and attacking, the more important it becomes to check again.

When should !scout be used after a LordsRally rally alert arrives?

Use it immediately when a fast decision is needed for the target or attacking castle. Since the rally alert reaches the group within the first 1–3 seconds, getting the scout report early gives more time for rally participation, counter-formation, or defense decisions.

Use the scout report not as an information screen, but as the foundation of your war order. To manage shield drop notifications, rally alerts, and kingdom intelligence in one group more efficiently, review LordsRally’s features and commands pages.