Best Target Selection in Lords Mobile: A Scoring Guide with !activity + !equip

The most expensive target-selection mistake in Lords Mobile is launching a rally based only on “no shield” information. A castle whose shield has dropped could belong to an online rally leader, a trap changing gear for a counterattack, or a player who will teleport away within minutes. On the other hand, a mid-might castle with low activity for a long period and no switch toward defensive gear can create a much cleaner opportunity.

The goal here is not to make a final decision with one command; it is to combine activity, equipment, and current war status into one target score. With LordsRally, you can review behavior history through `!activity` and inspect current and historical equipment images with `!equip`, then compare targets using the same criteria. This moves R4/R5 decisions beyond “I think they are open” and turns them into a fast but measured priority list.

Why is target scoring safer than checking shields alone?

A shield-drop notification shows that an attack window has opened; it does not mean the castle is easy. Especially during KvK, Baron, Chalice, or heavy migration days, the number of open targets increases—but active war players are among them as well. That is why the best choice is a target that can answer three questions at the same time:

How active is the player?
Does their equipment indicate preparation for defense or offense?
Is the timing window genuinely open for an attack right now?

In practice, scoring targets out of 100 points is enough:

Activity risk: 35 points
Equipment risk: 35 points
Current war status: 20 points
Location and guild context: 10 points

A high total score does not mean “guaranteed zero.” It means the target is a more favorable candidate that your guild should inspect first. For example, a 78-point target is usually a better starting point than an unshielded 42-point target that changes equipment frequently.

The important part of this system is simple: LordsRally does not automatically decide “attack this target.” The bot provides war intelligence; the final rally, scout, and troop decision belongs to the guild’s war team. You can view all available commands on the commands page.

Layer 1: Score return-risk with !activity

Start the first score with `!activity`. What you are looking for is not simply whether the player has been inactive for a while. The goal is to understand their repeating activity pattern. If a player consistently shows movement, might changes, shield renewals, or equipment changes at specific hours, they are likely to react quickly even if they appear open during that window.

You can structure the activity score like this:

0-10 points: Recently active, showing frequent changes, or has an unclear activity pattern.
11-22 points: Some intermittent activity; short quiet periods exist, but regular checking is still likely.
23-35 points: Long and repeating quiet periods; the target’s behavior appears more predictable.

Example scenario: The same guild finds two unshielded targets. The first castle has frequent movement and status changes in recent hours. The second castle has shown lower activity signals for a longer period. Even if the second target has lower might, it may be the more controlled candidate for rally organization.

The key distinction is this: Low activity is not zero risk. The player may return, a guildmate may call for defense, or their leader may come back. Use activity not as a final verdict, but as the heaviest layer of the total score.

If you want to interpret the activity graph in greater detail, see the !info activity graph reading guide.

Layer 2: Check defensive preparation and intent with !equip

`!equip` helps you view the target’s current and historical equipment images. The strength of this data is not one gear set alone, but the trend in gear changes. Does the target regularly switch into war gear? Do they remain focused on defense? Did they change equipment after their shield dropped? These details provide important context before a rally.

You can score equipment risk like this:

0-10 points: Recent equipment changes are visible; the chance of war preparation or active monitoring is high.
11-22 points: Equipment appears stable, but regular changes exist in the history.
23-35 points: No clear preparation change has appeared for a long time; if other signals also fit, reaction risk may be lower.

The most common mistake here is drawing a definite formation or troop comp conclusion from equipment. Gear can provide clues about intent and preparation; it is not a final report by itself. Instead of quick assumptions such as “I saw attack gear, so it must be infantry frontline,” read equipment together with activity history.

For example, if the target’s equipment appearance changes when their shield drops and activity rises in the same time window, reduce their target score significantly. In contrast, if activity is quiet and there is no sudden defensive preparation in equipment history, the target can remain near the top of the list.

To understand the limits of turning equipment data into a war decision, review the guide to reading enemy castle composition through equipment.

Layer 3: Use shield drops and rally alerts as a timing filter

Activity and equipment tell you about target quality; real-time notifications determine when you should act. With its event-driven structure, LordsRally delivers events such as shield drops, burning/smoking castles, rage, and rallies to your WhatsApp or Telegram group within 1-3 seconds. You do not wait for a scan that refreshes at fixed intervals; the notification arrives when the event occurs.

You can distribute the 20 points in this layer as follows:

0 points: The target is shielded or currently in an active rally/heavy attack context.
5-10 points: No shield, but recent war movement, burning, or rage signals are present.
11-20 points: The shield has dropped, additional attack risk appears low, and there is enough time for the guild’s rally setup.

Especially when a rally alert arrives, recalculate the target score. An enemy launching a rally on a castle can mean two different things: either the target is already in the middle of a fight and your rally is too late, or the enemy has identified the attacker or target and changed their own defensive plan. In both cases, do not continue with the old score—re-rank the target.

For nighttime operations, a practical R4 flow is:

Check candidates with dropped shields or no shield.
Compare reaction risk among the first candidates with `!activity`.
Confirm recent preparation changes with `!equip` for the candidates that remain at the top.
Update the score if a rally, rage, or burning notification arrives.
Move the top 1-2 targets forward for scouting and the guild war plan.

Layer 4: Give the final 10 points through location, guild, and leader status

A good target is not only an open castle; it is an attackable target. If two castles have the same score but one is in the center of an enemy hive while the other is more isolated, rally travel time, counter-rally probability, and reinforcement speed will differ. These final 10 points add battlefield reality to your score.

Signals you can check:

Use `!find` to review the target’s guild, coordinates, might, and status card.
Use kingdom data to assess the war strength and surroundings of the target’s guild.
If there is a leader returning/returned alert, reassess the target; a leader coming back can change the defense decision.
If dense hives, camps, or tiles are near the target, the probability of fast support increases.

Example score: If a target receives 28 from activity, 24 from equipment stability, 16 from the current timing window, and 7 from location, the total is 75 points. Another target may receive 30 activity points, but only 8 due to equipment changes and 4 because of rally risk, leaving it at 49 points. Rather than prioritizing the second target just because it initially looks more inactive, you prioritize the first target with lower total risk.

5. Turn the score into a guild operation: shared decision, not one person’s call

Target scoring works best when R4/R5 and the rally leader speak the same language. Set a simple standard in your group: use the order “Activity / Equipment / Current Status / Location / Total” for every candidate. This creates short, comparable decision notes instead of long chains of screenshots.

LordsRally’s multi-kingdom support is especially useful here. While preparing for war in the main kingdom, you can also monitor other kingdoms where migration is possible and build different operation flows in kingdom-specific groups. One bot account can host multiple kingdoms, and the system brings search, war, migration, wonder, and map intelligence into the same workflow through 78 commands.

If WhatsApp native buttons are enabled, you can move from a player card to Info, Equipment, and Track with one tap; when they are disabled, the system safely returns to a numbered list. Guilds using Telegram also benefit from the same real-time notification logic. Without installation, an app, or keeping a computer on, the bot monitors the relevant kingdom 24/7.

The summary of this approach is simple: A shield drop opens your target list; !activity measures the target’s return-risk; !equip checks preparation changes; and a rally alert tells you whether the decision is still valid. For more tactics, browse the blog archive, and review the complete workflow on the features page.

Frequently Asked Questions

Does !equip output show the target’s formation with certainty?

No. `!equip` provides signals about preparation trends through current and historical equipment images; it is not definitive proof of formation or troop comp by itself. Evaluate equipment data together with `!activity`, real-time notifications, and your guild’s scouting decisions.

Does LordsRally create this score automatically?

No. The 100-point model in this article is a recommended operational framework for your guild to compare targets consistently. LordsRally provides the necessary intelligence and real-time alerts; the R4/R5 team assigns the score according to its own war plan.

Why should I check again after receiving a shield-drop notification?

Because the shield-drop notification that arrives within 1-3 seconds shows that the window has opened—it does not guarantee the target will remain defenseless. The player may shield again, change equipment, teleport, or their guild may start a reinforcement plan. That is why checking activity and equipment again before launching a rally is valuable.

If you want to manage target selection through a shared war workflow instead of guesswork, integrate LordsRally’s notification and command structure into your guild’s daily operations; do not chase every open castle—chase the most meaningful target at the right time.