Lords Mobile: !find or !i? A Guide to Using the Two Search Commands in the Right Scenario

In Lords Mobile, finding a target and confirming the right target are not the same thing. You saw a name near a hive, caught an enemy name in a rally report, or a guildmate said, “find that castle”: which command should be your first move? In LordsRally, the short answer is: !i is for speed; !find is for decisions.

Both commands help you search for players, but their roles during war are different. !i quickly queries a name fragment and gets you closer to the castle you are looking for by the shortest route. !find brings together data that matters in war, such as the target’s guild, activity status, coordinates, might, attack power, shield information, and recent activity.

Once you establish this distinction, you will not waste time checking screens during night hunting, prepare for the wrong target before a rally, or send unclear calls as an R4/R5. LordsRally’s event-driven architecture delivers events such as shield drops and rallies to your WhatsApp or Telegram group within 1–3 seconds; however, processing that signal with the right query determines the quality of your move.

!i: When Should You Use a Quick Castle Query from a Name Fragment?

!i is LordsRally’s quick search command. If you do not have the player’s full name, the name is long or written with decorative characters, or you only know a distinctive part of it, this should be your first choice. The goal is to quickly get closer to answering “is the player I am looking for still in this kingdom?” without entering a long search process.

For example, a player in the war group says, “The enemy had Night in their name and left the hive.” If the full name is unknown, you use !i instead of guessing with !find immediately. You scan the name fragment, see possible results, and decide the next step needed to identify the correct player.

!i is especially useful in these moments:

• You only remember part of a name from a rally card or chat message.
• The enemy teleported and the group urgently needs to confirm, “who was that?”
• You want to collect possible candidates in the first pass among several players using the same abbreviation.
• You want to start a query from your WhatsApp or Telegram group within seconds instead of searching manually on the map.
• During hive fights, when you need to check many names quickly and then inspect only critical targets in depth.

The key point is this: !i is a pre-filtering tool. It is not meant to select a rally target on its own; it is meant to get you to the right player quickly. Name similarities can be misleading, especially in large kingdoms. Two different castles with the same name root may belong to different guilds and have completely different war value.

After catching a candidate with !i, your second command should be !find if that target has war value. This turns a quick search into verified intelligence. If you want a closer look at quick-search usage, see the !i quick search guide.

!find: What Does It Confirm Before You Rally a Target?

!find does not only answer the question, “where is this player?” It helps you see the target’s war context: guild tag, activity, coordinates, might, attack power, shield duration, and activity history are reviewed on the same card. This makes !find the command to use before an attack decision, tracking decision, or defense alert.

A typical !find output is read with this logic:

🧧 [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 ]

Every data point on this card serves a separate decision question:

• Guild tag: Is the target alone, or close to an active war guild? You assess the surrounding risk instead of preparing a rally into the wrong guild’s area.
• Activity status: Attacking an active castle is not the same as evaluating a target that has not reacted for a long time.
• Coordinates: You estimate rally pathing, hive distance, and the likelihood of nearby defense.
• Might and attack power: You do not assume a defense profile based only on high might; you build the war decision more carefully.
• Shield and activity history: You see whether the target is genuinely open and whether they have recently become active.

For example, you believe that the candidate found through !i is truly the enemy rally leader. If the !find card shows the castle as active, shows equipment changes, or indicates a recent might increase, that may signal that the target is preparing for war. Instead of calling an immediate attack, you share the card with the guild leader and account for possible defense and counter-rally pressure.

On the other hand, if the target is unshielded, smoking, or in rage, the !find card can become the starting point of a larger operation. Following it with !smoke, !unshielded, !rage, or guild-based queries makes more sense. To see all commands by category, use the commands page.

Quick Decision Table: Which Command for Which Question?

At war pace, command selection can become a simple decision tree. Ask the right first question and you eliminate unnecessary queries.

• “What was the full name, and which castle could it be?” → !i
• “Where is this player now, and which guild are they in?” → !find
• “Is this target open, active, and meaningful for an attack?” → !find
• “I need to identify the attacker in a rally alert quickly.” → First !i, then !find for the confirmed candidate
• “A guildmate only gave me part of a name.” → !i
• “As R4, I will share coordinates and war context with the group.” → !find
• “I want to be sure I have the right player before I track them.” → !find, then !track if needed

In this workflow, !i improves query speed and operational practicality. !find reduces decision errors. Rather than trying to replace one with the other, using them in sequence is the most efficient method.

The time between the first signal and confirmation matters especially against enemies who change names or disrupt hive formation by teleporting. LordsRally can automatically locate a castle again through unique-identity location tracking even if it teleports and changes its name. However, you should still make the current war decision using the information on the !find card.

The !i and !find Workflow During Rally and Shield-Drop Scenarios

Think of a realistic KvK or high-intensity kingdom war scenario: a rally alert arrives in the group. The attacker’s name is long, decorative, and one group member could only read the word in the middle. Having everyone search on the map is a waste of time.

The first player queries the name fragment with !i. Once the attacker is identified among possible candidates, the R4 or rally coordinator opens the detailed card with !find. The guild tag, activity status, coordinates, and context of recent movements are read from the card. Then two practical decisions emerge:

• If the attacker is near an enemy hive, the defense call and counter-move can be planned at the same time.
• If the attacker is in another area or far from guild support, the target opportunity after the rally ends can be evaluated separately.

The same principle applies to a shield-drop notification. A shield drop, one of LordsRally’s 12 smart notifications, reaches the group as soon as the event occurs; there is no fixed polling interval to wait for. If you already know the target when the notification arrives, checking the current card with !find is enough. If only a name fragment is visible or there is uncertainty in the group, return to the !i then !find chain.

The goal here is not “the shield dropped, hit immediately.” A call made without reading an open target’s activity, guild, location, and recent movement can lead to trap defense, unnecessary speed-up use, or moving toward the wrong target. Speed matters in Lords Mobile, but verified speed matters more.

Standard Search Discipline for R4/R5 and Multi-Kingdom Management

In an R4/R5 role, the biggest problem is not finding information; it is having everyone in the group act on different assumptions about the same target. The solution is to establish simple search discipline: use !i when a name fragment arrives, !find when a decision card is needed, and !track if the operation will continue.

A sample guild procedure can look like this:

• If a member only knows part of the name, they share the !i result in the group.
• An R4 confirms that the candidate is the right player with !find.
• If the target is critical, active tracking begins through the Track option on the card or with !track.
• The call is updated as events such as shield drops, rage, guild changes, or leader returns arrive.
• After the war, private notes about the target can be saved with note commands if needed.

LordsRally supports tracking up to 4 targets at the same time and supports multiple kingdoms. This is useful especially when war continues in your main kingdom while you are planning migration into a second kingdom and do not want to lose visibility. Monitoring each kingdom in a separate group also prevents war chat from being flooded with unnecessary notifications.

On cards that support WhatsApp native buttons, actions such as Info, Equipment, and Track can continue with one tap. If buttons are unavailable, the system safely falls back to a numbered list. In other words, the card you receive through !find is not only a data screen; it is the transition point to your next intelligence step. Explore broader war and kingdom tools on the features page.

Get Faster with !i, Prevent Wrong Decisions with !find

The summary rule is clear: !i is for quickly picking up a player’s trail; !find is for understanding whether that trail belongs to the right target and the right war situation. Start with !i when you have a short name fragment, need urgent confirmation, or are in a crowded war chat. Move to !find when you will share coordinates, evaluate a rally, read a shield window, or place a target under tracking.

LordsRally’s strength is not only in its 78 commands; it is in using those commands in the right order for the pace of war. Matching these two commands correctly during shield-drop notifications, rally alerts, migration movements, and opportunity targets makes kingdom intelligence more actionable. For more tactics, check the guides on the blog page.

Frequently Asked Questions

Is !i a simpler version of !find?

Not exactly. They serve different needs. !i is used for quick searches with a name fragment. !find lets you evaluate a target with broader war data such as guild, activity, coordinates, might, attack power, shield status, and historical movements.

Which command should I use first when a rally alert arrives?

If the attacker’s name is clear, using !find directly is the fastest confirmation method. If the name is incomplete, unreadable, or only partly known, first find the candidate with !i and then open the target card with !find.

Can I automatically track a target I found with !i?

It is healthier to first confirm that it is the right player with !find. Then you can use the Track option on the card or start active tracking with !track. This reduces the risk of tracking the wrong castle because of name similarity.

To build the search workflow around your guild’s war structure and use LordsRally commands more efficiently, run a short test round in your group with !find, !i, and !info; whenever needed, you can quickly reach the right category from the commands page.