How to Find the Weakest Attack Window from !activity History in Lords Mobile

Finding a good target in Lords Mobile is not simply about spotting a castle without a shield at that moment. The real advantage comes from estimating when the target will become active again, when they may receive guild support, and during which hours their defensive reaction is weaker. For that, you need behavioral data rather than a one-time search.

In LordsRally, `!activity` helps you read that rhythm by showing a player's activity history. But the right approach is this: do not treat activity history as proof that “the target is definitely asleep.” Treat it as a signal for finding the lowest reaction-risk window. When combined with shield drop alerts, rage status, leader information, and guild movements, it creates a safer attack plan.

Read a Repeating Rhythm, Not a Single Moment, with !activity

Seeing a player idle at 03:00 one night means very little on its own. They may have stepped away briefly, may return to refresh their shield, or guildmates may still be online. But if you see consistent silence in the same time range across several days of activity history, that becomes a behavioral pattern.

The first step is choosing the right target. Search the player with `!find` and review their basic card, then open their history with `!activity`. Guild, might, activity status, and recent movement details from the `!find` result help you put the activity graph into context. For example, the history of a high-might target who frequently changes names or teleports should be interpreted differently from a farm account that stays in a stable hive.

Look for these three signals in activity history:

• Recurring low-activity hours: If activity is low during the same period for several consecutive days, it may reflect the target's daily routine.
• Short, regular logins: If the target appears for only a few minutes at specific times, they may be refreshing a shield or checking resource tiles. Starting a rushed rally during these windows is risky.
• Movement before extended silence: An equipment change, location movement, or guild change followed by a long idle period does not always mean the target is away from the game. Sometimes it indicates war preparation.

In practice, look for at least several repetitions instead of relying on a single 24-hour snapshot. For example, if a target is active daily around 00:30–01:00 and then remains quiet for a long time after 01:00, do not treat 01:05 as the attack moment. First confirm their shield status, then use 01:15 onward as a more sensible checkpoint. The goal is not to predict the exact second; it is to eliminate hours when the guild is unnecessarily waiting online.

If you want a more foundational explanation of how to read `!activity` data, see the guide to mapping an enemy's online-offline hours.

Weakest Window = Idle Pattern + Shield Risk + Low Guild Response

The most common mistake is deciding to attack simply because activity history looks low. In Lords Mobile, an attack window should be evaluated through three layers:

• Player layer: Is the target's activity rhythm low?
• Defense layer: Has the shield actually dropped, is rage active, and is the leader inside?
• Guild layer: Is the target's hive active, are guildmates nearby, and is fast support likely?

Consider a practical scenario: a target's `!activity` history shows they have stayed idle for long periods over the last few nights. That is a positive first signal. But if their shield is still active, there is no attack window yet. The moment the shield drops, LordsRally's event-driven system sends the alert to your WhatsApp or Telegram group within 1–3 seconds. Since you are not waiting for a fixed polling interval, you combine activity analysis with a real event.

At that point, the team's decision flow should stay simple:

• An R4 notes the target's low-reaction hours from activity history.
• When the shield drop alert arrives, they recheck the target's current status.
• If rage is active on the target, they act more carefully because it suggests recent war interaction.
• The rally leader considers the target's location and guild density around them.
• If conditions are not suitable, do not force the opportunity. The right window is not just an unshielded castle; it is an unshielded castle with a low chance of counterplay.

This approach is especially important during KvK. An enemy who appears idle may still respond to an attack coming from another kingdom. Activity history gives you priority, not certainty.

Enable Alerts Around Your Activity Plan: Reduce Noise, Speed Up Decisions

The value of a war bot is not sending every event to the group. Its value is making sure the right person can make a decision when the right event happens. In LordsRally, all 12 smart notification types can be enabled or disabled individually, and might, shield, or activity filters can be configured. This lets you carry the target profile identified through `!activity` directly into your alert flow.

For finding the weakest attack window, prioritize these alerts:

• Shield dropped: The main alert that turns an activity estimate into a real opportunity.
• Rally alert: Helps you reassess the plan if the target or nearby area is already involved in war movement.
• Rage activated: Provides critical context that the target has recently been involved in combat.
• Burning/smoking castle: If the target is already under attack, your rally may be too late or entering a risky situation.
• Guild changed and name changed: Indicates that the target profile has changed, so the old activity rhythm may no longer be reliable.
• Leader returning: A leader returning to an unshielded castle is a separate timing factor that must be evaluated carefully.

Example: You identify a target with a recurring idle profile between 02:00 and 06:00. Instead of tracking only shield drops during that period, keep rally and rage alerts enabled too. If the shield drops at 03:20 but rage activates in the same minute, the chance that the target or their surroundings are actively fighting increases. On the other hand, if the shield drop is followed by a calm event flow, the rally leader can make a faster decision.

You can review all alert settings and use cases on the features page, and check the full command list in commands.

Build a 5-Minute Pre-Rally Check Routine

Guilds that apply activity data instead of debating it move faster. For R4/R5 players, a short check routine reduces confusion, especially during night operations. Before opening a rally, use this order:

• 1. Confirm the target: Use `!find` to check the target's current guild, location, might, and current card.
• 2. Compare activity history: Use `!activity` to see how the target normally behaves during the time window you are currently in.
• 3. Confirm shield status: Even if an alert has arrived, reread the current card before committing.
• 4. Scan war signals: Evaluate rage, burning, rallies, and leader status.
• 5. Discuss nearby risk: If strong support is likely in the target's hive, do not rely only on the target being idle.

The advantage of this routine is that everyone evaluates the same information in the same order. One player does not say “the target is asleep” while another misses that rage is active. The rally leader makes the call based on current signals, not emotion.

Especially against high-might targets, you need a fast answer to the question: “Has the window closed?” If the target teleports or changes names, you do not want to get stuck in a manual search chain. LordsRally's automatic location tracking finds the target again through a unique identity, so your tracking flow does not break after a name or location change. You can track up to four targets at the same time, keeping alternative opportunities ready beside your main target.

How Does Activity Analysis Change Across Multiple Kingdoms?

For guilds monitoring more than one kingdom, the biggest mistake is applying the same time logic to every kingdom. One kingdom may be quiet at night while another has migration movement, Wonder preparation, or KvK pressure. Do not separate activity history from its kingdom context.

LordsRally supports multiple kingdoms and can monitor each kingdom 24/7 in a separate group. This allows you to manage low-activity hours for farm targets in one kingdom while tracking the movement rhythm of war guilds in another. For example, if incoming migrations are heavy in a target kingdom, older idle data may become less reliable because new players can change hive balance and support times.

At this stage, do not look only at the individual target. Use `!kingdominfo` for a broader view of the kingdom, leaderboards for power balance, and `!heatmap` for map distribution. The result of `!heatmap 1247` visually shows castle density and hot/war zones, helping you assess whether a target with quiet activity history is actually positioned inside an active hive.

LordsRally's 78 commands help you collect this intelligence without leaving your WhatsApp or Telegram team chat. Start with the most popular trio—`!find`, `!kingdom`, and `!info`—to quickly frame the target and kingdom, then use `!activity` to deepen your timing decision.

Frequently Asked Questions

Does !activity history prove that a target is definitely offline?

No. Activity history is not proof that the target is offline; it shows behavioral tendencies. The healthiest decision comes from reading historical rhythm together with shield drop alerts, rage status, and war movement around the guild.

Why should I check again after receiving a shield drop alert?

Because in Lords Mobile, even a few seconds can be enough for a target to refresh their shield, teleport, or for their guild to react. LordsRally reports the event within 1–3 seconds; your job is to use that speed with an up-to-date target check and clear rally communication.

Can I use activity analysis only for rallies?

No. You can also use it when choosing farm targets, evaluating unshielded castle risk, planning when your own guild members may be exposed, and analyzing the tempo of enemy guilds before KvK. In every scenario, however, you should separately verify current factors such as shield status, location, and guild support.

For more war tactics and real command scenarios, browse the blog archive. If you want to build a more disciplined shield drop, rally alert, and enemy castle tracking flow in your kingdom with LordsRally, start with commands and features.