Lords Mobile: Farm Account or Real Player? How to Identify Targets with !activity History

When you spot an unshielded castle, your first instinct may be to set a rally or solo it. But in Lords Mobile, having no shield does not mean the target is truly idle. Some players stay open while gathering resources, some briefly change equipment, and others deliberately enter rage and appear vulnerable to bait enemies. Farm accounts, meanwhile, often leave regular but low-volume activity traces.

Making this distinction correctly helps you avoid wasting troops, especially during KvK, Baron periods, or heavy kingdom wars. The !activity command in LordsRally shows the target’s activity history, while !info helps you view the activity graph. When you combine both with shield status, recent burns, guild position, and equipment, the difference between an “open castle” and a “player waiting to counter” becomes much clearer.

What does a farm account’s activity trace look like?

A farm account is not necessarily a completely inactive account. A farm tied to an active main account sends resources, goes to tiles, sometimes refreshes its shield, and teleports into the guild hive. That is why seeing one action does not mean you should label the target a real fighter. What you are looking for is a repeating, low-intensity behavior pattern.

A castle that is likely to be a farm usually shows these signs:

Activity repeats at specific times in short, similar intervals.
There are long periods without movement, followed by minor actions such as resources, tiles, or a short location change.
After its shield drops, there is no fast return, equipment swap, or aggressive movement.
Might growth is slow and limited rather than made up of major jumps.
The castle usually sits in, or close to, the main guild’s hive.
Routine logistics matter more than war activity.

Consider this example: a 300M might target has been briefly active at roughly the same time every night for the past few days, then remains quiet for long periods again. After its shield drops, it does not relocate and creates no equipment-change or new burn record. This profile leans toward a farm account—but it is still not a “guaranteed zero-response” target. If the main account owner is online, they may shield, reinforce, or rally to protect the farm.

For that reason, do not base your decision on the graph alone. First, open the target’s current castle card with !find and check its guild, activity status, location, and visible details. Then use !activity to read its historical movements. You can find every command on the commands page.

Why are !activity and !info stronger together?

Players often say “the !activity graph,” but in practice the most reliable read comes from using !activity history and the !info activity graph together. !activity gives you the events and movement history to inspect. !info makes the rhythm easier to see: when does the target become active, how long does it remain quiet, and is its pattern changing?

The goal is not to memorize individual events. It is to read the target’s behavioral rhythm. Let’s look at three different profiles:

Profile A: Regular farm: Short activity at similar times each day, long gaps, limited might changes. This player is usually opening the account for resources and account management.
Profile B: Active fighter: Irregular movement throughout the day, guild changes, teleports, equipment swaps, burns, or war-related signals such as rage. Even without a shield, this target is likely to react quickly.
Profile C: Trap or preparing castle: After a long quiet period, there is a sudden change in location, equipment, or attack power—especially if it is waiting close to an enemy hive. Rallying this target without reading historical data can become an expensive mistake.

For example, a target may have looked idle for two days. But if it has activity records, an equipment change, and a teleport near the hive in the last 20 minutes, those two quiet days are no longer enough to make a decision. If current behavior breaks the historical rhythm, prioritize the current signal.

For a deeper interpretation of activity data, also read How to Map an Enemy’s Weekly Activity Rhythm with !info in Lords Mobile.

A 90-second target check when the shield drops

The first minutes after a shield drop are the most valuable time to identify a farm account. A shield drop notification opens an opportunity window while also letting you measure the target’s reaction time. Because LordsRally is event-driven, the alert reaches your WhatsApp or Telegram group within 1–3 seconds when the event occurs, without waiting for fixed-interval polling.

When the alert arrives, an R4/R5 or rally leader can use this practical flow:

First 15 seconds: Open the castle card with !find. Check the current guild, location, might, attack power, activity status, and shield status.
15–40 seconds: Use !activity to inspect recent history. Do the latest movements look like war preparation or routine farm behavior?
40–60 seconds: Use !info to examine the rhythm. Has the target been inactive for a long time, or does it return regularly in cycles?
60–90 seconds: Evaluate the target’s location. Is it inside a hive, close to its main guild, or likely to receive support nearby? If needed, inspect nearby targets with !near.

The advantage of this flow is that it reduces the pressure to “hit immediately.” Especially for rallies with high troop costs, a 60–90 second check is far cheaper than sending a rally into the wrong target. If the target genuinely looks like a farm, make the attack decision in line with your guild’s current war plan and the in-game rules.

In LordsRally, all 12 notification types—including shield drops, rally alerts, rage, migrations, leader returns, and other events—can be enabled or disabled individually. So if you are farming targets at night, you can build a cleaner group feed with filters that fit your operation instead of keeping every alert enabled. Review the notification system on the features page.

5 red flags that reveal a real player

A farm-like account is not automatically safe. If two or more of the signals below appear together, it is more sensible to classify the target as “able to react instantly.”

Fast movement after the shield drops: If activity, a teleport, or a location change appears shortly after the shield drops, someone is likely at the account.
Equipment change: A switch to attack-focused equipment can indicate that the account owner is preparing for war. You can check current and historical equipment with !equip.
Rage signal: A castle in rage may already be operating at war tempo. Use !rage to filter current rage targets separately.
Burns and rally surroundings: Seeing that the target burned recently is not proof of weakness on its own; an enemy guild may be gathering for defense or a counterattack.
Connection to a strong, active guild: If the target is at the center of a hive, it can receive reinforcements quickly even if its own might appears low.

Remember: an activity graph does not read intent; it shows a behavior pattern. Instead of saying “the graph is empty, so it is definitely a farm,” ask: “Is the data limited, and is the risk low?” If the graph is empty or there are not enough signals, do an additional check rather than treating the target as certainly idle. Use the checklist in What to Do If the !activity Graph Is Empty.

A guild target list: Farm, suspicious, active fighter

Target selection becomes inconsistent when it relies on one player’s memory. As an R4/R5, build a simple three-tier classification so rally leaders speak the same language:

Farm candidate: Regular low-intensity activity, long inactive blocks, no war signals, limited hive support.
Suspicious target: Looks idle, but its location is critical, its guild is active, or recent equipment and teleport movements exist.
Active fighter: Irregular, intense activity; war signals; fast reactions; and a strong link to an active guild.

In LordsRally, you can use !addnote for private notes and !addguildnote for guild-based records. This lets your team retain field notes such as “farm candidate, becomes active in the evening” or “returned quickly after shield drop.” Recording past decisions means your rally leader can act on data rather than guesswork when approaching the same castle again.

For guilds playing across multiple kingdoms, this system becomes even more valuable. LordsRally supports multiple kingdoms, letting you set up separate tracking flows for each kingdom group. Through WhatsApp or Telegram, you bring kingdom intelligence into the team channel without installation or keeping a computer on. With 78 commands covering search, war, maps, migration, and wonder intelligence, target selection moves beyond the simple question of “is it unshielded?” and becomes a more disciplined operational process.

Frequently Asked Questions

Can !activity tell me with certainty that an account is a farm?

No. !activity shows past behavior; it does not define certain intent or account type. For a farm profile, long-term low intensity, regular routine, and the absence of war signals should be evaluated together. Add a !find check for current shield, guild location, and activity details.

Why should I not attack immediately after receiving a shield drop notification?

A shield drop is an opportunity window, not an automatic safe-target marker. The target may be online, its main guild may provide support, or it may be preparing a counter rally. The notification arriving in 1–3 seconds gives you time—use it for a quick verification with !find, !activity, and !info.

Which commands are practical when looking for targets at night?

Start by listing open castles with !unshielded, then open individual target cards with !find. Review behavior rhythm with !activity and !info. !smoke for smoking castles and !rage for targets in rage also add useful context. For more tactics, explore war and kingdom intelligence guides in the blog archive.

When distinguishing a farm from a real player, read the rhythm instead of making assumptions: check history when the shield drops, verify the current signal, and build your guild’s attack plan accordingly. To adapt LordsRally’s notifications and command structure to your kingdom setup, review the features and commands pages.