Track 4 Targets at Once in Lords Mobile: Managing Multi-Target Monitoring with !track and !tracks

In Lords Mobile, the most expensive mistake in war is not hitting the wrong target; it is failing to see the right target at the right time. An enemy opens fury, their shield expires shortly after, they teleport away from the hive, or they try to disappear by changing their name. If a rally leader tries to follow all of this through group messages, in-game notifications, and manual searches, even a window of a few seconds can close.

With LordsRally, you can set up active tracking for up to 4 targets at once and place the critical castles in your war plan on a separate priority list. Instead of checking movement at fixed intervals, the bot processes events through event-driven infrastructure the moment they occur; the alert usually reaches your WhatsApp or Telegram group within 1–3 seconds. In this guide, you will learn how to manage multi-target enemy castle tracking with `!track`, `!tracks`, and the right tracking cycle.

An important clarification: there is no command called `!pauseTrack` in the LordsRally command set. To stop active tracking, use `!canceltrack`; to close all active tracks, use `!canceltracks`. If you want to move a target into the background temporarily, the safest method is to cancel active tracking and restart it when needed.

Set the difference between active tracking and passive watching correctly

The first step in using the multi-target system efficiently is not putting every enemy at the same monitoring level. In LordsRally, `!track` is for active tracking; use it for targets that directly affect your war plan. `!watch` is better suited to lower-priority, passive monitoring scenarios.

It usually makes sense to divide active tracking slots among these four target types:

• Enemy leader with rally threat: A rival who has opened fury, appears online, or is using war gear.
• High-value castle with a shield expiring soon: Especially during KvK, Baron, or intense kingdom war hours.
• Solo target likely to teleport away: A player whose might, kill count, or gear history requires preparation.
• Enemy guild coordinator or rally setter: Track them for hive movement and rally timing.

For example, do not fill all four slots and play with a simple “we hit whoever loses their shield” approach. Reserve one slot for defense. If you are tracking a castle with potential to launch rallies, an incoming rally alert may be more valuable than an attack opportunity. Shielding your own hive on time can prevent a much larger loss than the farm target you might find a few minutes later.

For the division of duties between passive watching and active tracking, also check the !watch guide. The core rule is simple: A castle you will make an immediate decision about belongs in active tracking; a castle whose behavior you only want to observe belongs in passive watching.

Build a four-target war list with !track

Do not select targets randomly before using `!track`. First, use the popular search commands `!find`, `!kingdom`, and `!info` to establish the basic picture of the castle, kingdom context, and activity history. This lets you reserve your slots for targets that will actually create value.

A practical pre-war flow works like this:

• Use `!find` to locate the target and check its current status.
• Use `!info` to review the activity graph and see when the target becomes active.
• If the target is critical because of rally risk, the chance of catching it open, or location intelligence, add it to active tracking with `!track`.
• When all four slots are full, remove the lowest-priority track with `!canceltrack` before adding a new target.

The goal is not merely to list four targets, but to assign each one a war role. For an R4/R5, an example setup could be:

• Slot 1: Enemy rally leader
• Slot 2: Strong defender inside the enemy hive
• Slot 3: Opportunity target with an expiring shield
• Slot 4: New castle that migrated into the kingdom and has not been assessed yet

This structure stops you from blindly chasing one player. For example, when a target changes its name and teleports to another location, you do not need to search for it manually again; LordsRally continues automatic location tracking through its unique identity. This matters especially during heavy war hours when enemies try to break the intelligence chain through name changes or teleports.

Active tracking is not an attack guarantee. The target’s comp, leader status, fury, position, and guild support still need to be assessed. LordsRally gives you timely intelligence for the decision; your guild’s war structure determines the march, scout, and rally decision.

Audit your slots during every war cycle with !tracks

The biggest risk of a four-target list is forgetting old targets and locking active slots unnecessarily. The solution is to use `!tracks` regularly. This command lets you view your current active tracks; you should check them quickly, especially at the start of KvK, before Baron, and when an enemy hive becomes active.

A solid R4 routine can be set up like this:

• At the start of the war, use `!tracks` to check who occupies the four slots.
• Set a one-sentence purpose for every target: “rally threat,” “shield window,” “post-migration scan,” or “defense leader.”
• Remove a target that no longer has a purpose with `!canceltrack`.
• Before adding a new target, confirm its current intelligence value with `!find` or `!info`.

For example, if a target left the hive 6 hours ago and no longer affects the guild’s war power, it makes little sense to keep the slot open. In contrast, a newly migrated castle may look ordinary at first; but if it has a notable wonder history, high kill potential, or fury activity, adding it to active tracking can be the smarter move.

Do not try to solve the need for “pausing” a track by assuming a command exists. Instead of `!pauseTrack`, use two clear actions:

• If a target becomes temporarily unimportant, free the slot with `!canceltrack`.
• If the entire war plan changes, reset the list with `!canceltracks` and rebuild it with new priorities.

This approach reduces confusion inside the group. Everyone knows which four castles are truly critical, and the R5 does not get lost among notifications from old targets.

Connect shield drops and rally alerts to your tracking list

Active tracking does not work alone; it becomes war intelligence when combined with notification settings. LordsRally has 12 smart notification types that can be enabled or disabled individually, with might, shield, and activity filters available. For actively tracked targets, these events are especially important:

• Shield dropped: An attack window opens; immediately reassess the target’s online status, fury, and hive support.
• Rally alert: A critical signal for defense, anti-rally, or counter-rally decisions.
• Fury opened: It may show that the target is becoming aggressive; check your own guild’s open castles.
• Burning/smoking castle: Shows the target is under active attack, which can indicate either an opportunity or a trap.
• Name change and guild change: Helps you read enemy organization movement.
• Leader returning/returned: Leader status can directly affect the attack decision.

Consider a realistic scenario: two of your four slots are assigned to attack opportunities, one to an enemy rally lead, and one to a defensive threat. A fury notification arrives for the enemy rally lead. In the same minute, the second target loses its shield. Your first reaction should not be to send a march at the open castle; first check the attacker/target information on the rally card and the security of your own hive. If WhatsApp native buttons are enabled, you can continue with one tap on the relevant option in the card; when buttons are unavailable, the system safely falls back to a numbered list.

For a deeper breakdown of shield drops, read the shield drop detection guide, and for the rally defense flow, see the rally alert article.

How should you change tracking priorities across multiple kingdoms?

LordsRally supports multiple kingdoms. This is important for guilds planning migrations, players farming in different kingdoms, or coordinators monitoring more than one war front. However, multi-kingdom support does not mean every kingdom deserves the same level of attention.

If one kingdom is quiet while another is preparing for KvK, direct your active tracking slots toward the busier war front. Switch the scanned kingdom with `!kingdom`, then manage searches and tracking on the correct front. After that, use commands such as `!kingdominfo`, `!top_players`, `!top_players_kills`, and `!heatmap` to read the kingdom’s overall structure and choose your four targets accordingly.

For example, if the heatmap shows a dense hive area, a better group of four may be two rally leads, one strong defender, and one target showing teleport movement rather than randomly tracking individual castles. When maps, leaderboards, migration movement, and active tracking are used together, your decision is based on kingdom intelligence rather than assumptions.

You do not need to memorize all 78 LordsRally commands. To begin, `!find`, `!info`, `!track`, `!tracks`, `!unshielded`, and `!kingdom` create a solid core flow. You can open other tools as needed from the commands page, and review notification and infrastructure details in features.

Frequently Asked Questions

How many targets can I actively track at the same time?

With LordsRally, you can manage up to 4 actively tracked targets at once. The most efficient approach is to reserve slots for different roles, such as a rally leader, shield opportunity, defensive threat, and newly migrated castle.

Does the `!pauseTrack` command exist?

No. There is no command called `!pauseTrack` in LordsRally. Use `!canceltrack` to remove one target from the active list, or `!canceltracks` to close all active tracks. You can add the target again later with `!track` when needed.

How fast do tracking alerts arrive, and which apps do they work in?

Thanks to event-driven architecture, events are usually delivered to your WhatsApp or Telegram group within 1–3 seconds. The system does not wait on fixed-interval polling; it generates the notification when the event occurs.

Building your four tracking slots around your war plan does more than prevent you from missing a shield window: it shows your guild which threat must be handled first. For more Lords Mobile war tactics, browse the blog archive; when you want to set up tracking and notifications for your own kingdom, contact the LordsRally team.