How to Put an Enemy Castle on Active Tracking with !track in Lords Mobile: Step-by-Step Setup Guide

The real challenge in enemy castle tracking is not finding a target once. The real challenge is being notified at the right moment after that target teleports, changes name, loses its shield, or begins rally preparations. Especially during KvK, Baron preparation, or clashes between powerful guilds inside a kingdom, even a few minutes of delay can close the rally window.

The !track command in LordsRally is used to place a selected enemy castle under active tracking. The system is event-driven; it does not wait on a fixed-interval polling cycle. When a tracked event occurs, the notification usually reaches your WhatsApp or Telegram group within 1–3 seconds. That means your guild does not lose decision time when the target’s shield drops, rage activates, the player migrates, or war activity begins.

In this guide, we will cover !track not only from the command side, but also as part of real war discipline. Adding every castle you see to the tracking list is not intelligence; tracking the right target, for the right purpose, with the right alert setup is.

1. Which targets are truly worth active tracking?

The best targets for the !track command are castles your guild can actually act against. Instead of tracking a very high-might account positioned outside your kingdom just out of curiosity, focus on battle scenarios where your guild can make a decision.

Use this priority framework:

• Rally leaders: Players who launch rallies for the enemy guild should be your first priority, especially during Wonder and Baron periods.
• Strong accounts that frequently lose shield: Castles with weak shield discipline are valuable if catching them can result in real damage.
• Opponents near a hive: Enemy castles close to your hive require active tracking because of fast teleports and sudden defense potential.
• Accounts preparing to migrate: Strong players entering a new kingdom or likely to leave your kingdom can change the power balance.
• Targets whose leader recently returned: A castle without shield whose imprisoned leader has just returned can create a short but critical opportunity window under the right conditions.

Active tracking is not a guaranteed attack. You still need to read the target’s might, equipment, activity status, nearby camps, and hive structure together. Think of tracking not as the decision itself, but as the intelligence layer that helps you decide faster.

2. Verify the target before !track: do not track the wrong castle

Before using an active tracking slot, you need to verify the target’s identity. Names can be similar, the player may have changed guilds, or the opponent may have changed their name in the past. For that reason, your first step should be !find.

After searching for the target in your group, check the guild tag, might, attack power, activity, and status on the castle card together. You can also see the target’s current location and recent events through the card. LordsRally has automatic location tracking that helps find castles again through their unique identity even if they teleport and change name; however, avoiding the wrong target during the first selection protects your guild’s time.

Standardize these three checks when evaluating a target:

• Guild and name history: If there is a suspicious name change, check the history with !names.
• Activity signal: If the target is constantly active, they may react quickly even when their shield drops. In that situation, launching a rally based on an unshielded notification alone is risky.
• Equipment and war role: Use !equip to inspect current and historical equipment visuals for additional context on whether the target is defense-focused or attack-focused.

If you want to examine identity verification in more depth, also review the single-target analysis routine that combines search commands. This step helps ensure that your !track notification is coming for the correct player.

3. How do you start active tracking with !track?

For setup, simply enter the WhatsApp or Telegram group where the LordsRally bot is connected for the relevant kingdom. You do not need to install an app, keep a computer running, or open an extra screen in-game. The bot runs on infrastructure that monitors the selected kingdom 24/7.

The basic step-by-step flow is:

• First, make sure the correct kingdom is selected. If necessary, use !kingdom to check or change the kingdom monitored by the bot.
• Verify the target with !find. The name, guild, and war signals on the castle card should be consistent.
• Then use !track to add the target to active tracking.
• Confirm that the target entered the list with !tracks.
• If the target no longer has strategic value or the war plan changes, remove that individual tracking entry with !canceltrack.

You can manage up to 4 targets at the same time with active tracking. This limit helps you focus on four targets that can produce real action instead of filling the list with random names. For example, you can track one enemy guild’s rally leader, two strong defenders, and one farm or alt account that frequently leaves itself exposed.

Reassessing your tracking list every day is a good R4 habit. If the target guild migrated, the account has become inactive for a long time, or the opponent is no longer part of the war plan, free the slot. When you need to clear all active tracking entries, you can also use !canceltracks.

You can review every command and its use case on the commands page.

4. What should you do when a notification arrives? War flow for shields, rallies, and migration

The value of tracking starts with notification speed, but it is won through the guild’s response. LordsRally delivers shield drops, burning/smoking castles, rage activation, migration movement, rally alerts, leader returns, and other critical events through its notification system. These 12 smart alert types can be enabled or disabled individually, and might, shield, and activity filters can also be configured.

Set a clear guild procedure in advance for these three events in particular:

• Shield dropped: As soon as the notification arrives, first confirm whether the target is still unshielded, their activity state, and the area around them. If there is no rally leader available, sharing coordinates alone creates chaos. When R4 shares the target, they should state in one sentence whether the plan is to attack, observe, or prepare defenses only.
• Rally alert: Speed matters when the enemy makes a rally move. You can use the interactive options on the rally card to find the attacker or find the target. If WhatsApp native buttons are disabled, the bot safely switches to a numbered list. This prevents everyone in the war room from having to type the same command.
• Migration or rage activation: A powerful new castle can change the kingdom’s balance. A target in rage may be vulnerable to attacks, but may also be actively preparing for war. Do not treat the notification as an automatic attack order; perform a second check with !find, !equip, and if needed !activity.

The goal is not to turn 1–3 second detection into random ping traffic; it is to speed up the decision chain. The first R4 who sees the notification verifies the target, the rally leader makes the risk decision, and members move according to a clear command.

5. Tracking discipline and notification cleanup across multiple kingdoms

LordsRally supports multiple kingdoms. This matters for guilds researching migration targets, groups with allies in different kingdoms, or coordinators monitoring more than one war front. Setting up a separate group structure for each kingdom prevents notifications from mixing together.

A practical group structure could look like this:

• One group: Unshielded castle, rally, and defense notifications in the main kingdom.
• One group: Migration tracking and enemy guild movements.
• One group: Baron, Chalice, and title intelligence before Wonder events.

This separation prevents the main war group from filling with unnecessary messages. For example, LM Events notifications are disabled by default; only teams that truly want to track them should enable them as opt-in alerts. Leaving every alert enabled is not good intelligence. Keeping critical events visible while controlling secondary events produces better results.

Also, do not rely only on active tracking. To scan for opportunities across the kingdom at night, use !unshielded to filter open castles, !smoke to check unshielded castles currently under attack, and !rage to view targets in fury status. For a broader kingdom picture, you can also use !heatmap, leaderboards, and migration commands. LordsRally’s 78 commands turn a tracking decision into a much stronger war intelligence routine than a single alert.

To learn how to enable and disable notification types based on the war calendar, review the !bildirim guide, and see the full system structure on the features page.

Frequently Asked Questions

What is the difference between !track and !watch?

!track is used for active tracking, while !watch is a separate command for passive monitoring. Use an active tracking slot when a target has high war priority; set up passive monitoring for lower-priority or long-term observation targets. You can check your current lists with !tracks and !watches respectively.

Can I actively track multiple enemy castles at the same time?

Yes. LordsRally supports up to 4 active tracking targets at once. The best approach is to distribute those four slots deliberately among rally leaders, critical defenders, and genuine opportunity targets.

Do I need to keep my phone or computer on for tracking?

No. LordsRally does not require installation or an app; the bot runs in the relevant WhatsApp or Telegram group and monitors the kingdom 24/7. Thanks to its event-driven architecture, notifications are targeted as soon as an event occurs, with no fixed-interval scanning delay.

Building your active tracking list around your war plan turns shield drop notifications and rally alerts into a real advantage. For more Lords Mobile war bot tactics, explore the blog content or plan the notification structure your guild needs with LordsRally.