How to Report the !info Activity Chart to Your Guild with Screenshots in Lords Mobile

Good intelligence in Lords Mobile is more than dropping a single “the target may be open” message into the group. Your rally leader, R4s, and online players need to see the same picture and reach the same decision. This is where the activity chart from LordsRally’s !info command becomes a strong reporting tool.

The activity chart shows a castle’s recent activity rhythm, but the real advantage comes from sharing that data with the right context through a screenshot. Especially during KvK, wonder battles, Baron preparation, or busy shield-drop hours, you can provide a fast, evidence-based answer to the question: “When is this player likely to be online?” Because LordsRally delivers events within 1–3 seconds, you can combine your chart report with live shield, rage, and rally alerts.

Why should the !info chart become a guild report?

A target’s activity chart is not a guaranteed attack order by itself. But when interpreted correctly, it is strong pre-screening data that prevents your guild from wasting time. For example, if a high-might opponent becomes active consistently during certain hours, setting a rally during that window can be an unnecessary risk even if you catch them unshielded. On the other hand, if there is a long low-activity window, the R4 team can add that target to the watchlist.

The benefit of a screenshot report is simple: everyone sees the same chart. Instead of sharing subjective messages such as “I think they are idle,” you share timestamped data. This lets the rally leader evaluate the chart, the current castle card, and the shield status together before committing to the target.

In practice, a good report should answer three questions:

• Which castle is being reviewed? The guild tag and player name should be clear.
• What does the chart show? Is there a noticeable activity window in recent hours or days?
• What is the guild’s action? Watch, wait for a shield drop, stay alert for a rally, or skip the target.

This approach turns a screenshot from a random image added to chat clutter into a short war intelligence record.

Step by step: preparing the !info output for a report

First, make sure you have verified the correct target. Similar names, guild changes, or name changes can cause you to share the wrong castle’s chart, which may lead to a bad rally decision during active war hours. After searching for the target with English commands, request the activity chart.

• Use !find to locate the target.
• Then open the target’s activity chart with !info.
• Take a screenshot of the chart you receive.
• Send the image to the guild war group with the query time and recommended action.

A sample workflow looks like this:

• An R4 verifies the enemy castle with !find.
• They review recurring activity hours in the !info chart.
• They share the image with a note such as: “Check time: 22:15. Recent activity looks weaker outside this window. If the shield drops, scouting/rally decisions should proceed with R4 approval first.”
• If shield-drop and rally alerts are enabled for the same castle, new events arrive in the WhatsApp or Telegram group within 1–3 seconds.

The important distinction is this: the chart explains historical trends, while the live situation must be confirmed through the bot’s real-time alerts and the castle card. So instead of saying “they are definitely sleeping” based only on an older chart, cross-check the chart with the live shield status and current movement.

You can share the commands page with your guild managers to see every command and its use case.

The 4-line war note to add to a screenshot

Long paragraphs usually work against you when reporting to the guild. During rally preparation, players have limited time to read their screen. The most efficient format is four short lines placed above or below the image.

• Target: Player name and current guild tag.
• Check time: When the chart was captured.
• Observation: A clear activity window or quiet period.
• Action: Watch, defense alert, target priority, or skip decision.

Example report text:

• Target: [NOVA] FictionalCommander
• Check: 21:40
• Observation: Recent activity increases during evening hours; do not assume the target is idle right now.
• Action: If the shield drops, confirm again with the live card; if a rally starts, keep the defense team ready.

This note structure reduces two critical mistakes. First, it prevents the group from forgetting when the screenshot was taken. Second, it separates the reporter’s personal interpretation from the guild’s official action. Especially when the R5 is unavailable, having R4s communicate using the same criteria protects coordination.

In LordsRally, alerts can be enabled or disabled individually. For a war group, prioritizing alerts such as shield drop, rally, rage, and leader back/returning reduces unnecessary notification noise while keeping critical events visible. You can also review the alert logic on the features page.

Reading the chart together with shield-drop and rally alerts

The best way to use an activity chart is not to make it your only decision system. In the Lords Mobile war meta, a castle can show low activity while gathering resources, recovering its leader, or taking part in an enemy guild’s rally plan. This is why the second stage of your report must be a live event check.

Example scenario: A target’s !info chart shows low movement during specific late-night hours over the last few days. That is enough information to put the target on a watchlist, but it is not enough to attack. If a shield-drop alert arrives, the R4 should first check the target’s current status. Then check whether the castle is under active attack, has rage active, has its leader inside, or is receiving a rally.

This is where LordsRally’s event-driven architecture makes a difference. Instead of waiting for fixed-interval scanning, the alert reaches the group within 1–3 seconds when the event occurs. The rally leader decides based on the chart plus the live event, not on a chart shared several minutes ago.

You can use a short decision matrix:

• Quiet chart + shield drop: Check the current card and move into a fast target assessment.
• Busy chart + shield drop: Treat the chance of an active player as high; coordinate instead of charging in alone.
• Quiet chart + rally alert: Do not send marches before assessing the possibility of a trap, counter-rally, or defense setup.
• Busy chart + rage active: The target may be in war mode; remind your guild about defense and position discipline.

This method matters for defense as much as offense. When one of your own members is exposed, the R4 should not report their activity rhythm to the group; they should report the current risk and the defense plan to apply.

Daily and KvK reporting routine for R4/R5

Sharing activity charts for every target creates group clutter. Setting up a standard routine is more effective. The goal is not to make everyone study every chart, but to improve decision speed for war-relevant accounts.

For a daily routine, try this system:

• At the start of the day, select 3–5 strategic targets: rally leaders, high-might defenders, or key members of the enemy hive.
• Check their !info charts and report only patterns that have changed or deserve attention.
• Match shield drops, migrations, and guild-change events received during the day with the same target list.
• Before the evening’s active war hours, publish one “target summary” message.

During KvK or wonder periods, the focus of the report changes. You are no longer looking only for open targets; enemy online density, possible defense windows, and rally coordination become important. When assessing movement around Baron, Chalice, or other wonder titles, live tables, timers, and kingdom visibility also contribute to the decision process.

LordsRally’s 78 commands bring castle search, war checks, kingdom intelligence, migration, tiles, and wonder data together in one bot. Guilds managing multiple kingdoms can also set up tracking in separate groups. This lets you maintain the same reporting structure in your main kingdom and in a second kingdom monitored as a migration option.

For more war routines and command-focused tactics, browse the blog archive.

Common mistakes in screenshot reports

The first mistake is posting the chart without context. When only an image is shared, players may not know which target, time, or decision it refers to. The second mistake is treating an old screenshot as current data. An activity chart shows a trend; shield and rally status can change within seconds.

The third mistake is making a definite judgment with an “idle” label. The chart is decision-support data, not a guarantee of safety. Especially against high-might accounts, calling for an attack without current gear, leader status, rage, and incoming rally information is risky.

Finally, allowing everyone to write reports can create repeated information. The best practice is to let R4/R5s or assigned intelligence officers share reports in a standard format. This prevents critical alerts from getting lost between discussions in the WhatsApp or Telegram group.

Frequently Asked Questions

Does the !info activity chart show whether a player is definitely online?

No. The chart helps you interpret activity history and rhythm; it does not guarantee real-time online status. For an attack or defense decision, you should check the current castle status, shield, rage, leader information, and rally alert together.

Can I share the chart screenshot in a Telegram group instead of WhatsApp?

Yes. LordsRally can be used in WhatsApp or Telegram groups. Whichever channel you use, adding the target, check time, short observation, and action note beside the image makes the report easy to read.

Can I create separate activity reports for multiple kingdoms?

Yes. LordsRally supports multiple kingdoms. By creating a separate group and reporting routine for each kingdom, you can monitor your main kingdom, migration options, or enemy war kingdoms independently.

If you want to turn the activity chart into a shared decision screen for your guild, start by applying a standard reporting format to a small target list. Then combine shield-drop and rally alerts with this routine, and build a tracking setup that fits your guild through commands and features.