Lords Mobile LM Events Tracking: Don’t Miss Official Event Cards Before Guild Fest and KvK

When Guild Fest begins or Kingdom vs Kingdom (KvK) approaches, task planning, shield discipline, migration activity, and war roster discussions all start at once. The problem is that having R4/R5 constantly monitor chat, collect screenshots, and repeat the same information to everyone is not sustainable. Especially in an active guild, even a few hours of communication gaps can lead to shields being activated at the wrong time, teleports to the wrong target, or war calls being seen too late.

LordsRally’s LM Events (🎯) notification is designed to send official Lords Mobile event cards to your selected WhatsApp or Telegram group. This alert is disabled by default, so you do not have to fill every group with unnecessary cards. By enabling it before Guild Fest and KvK, you bring official event announcements into the channel where war communication happens. Equipment, rallies, shields, and target discussions then remain in the same place as the event context.

What is the LM Events notification, and why is it disabled by default?

LM Events is one of LordsRally’s 12 smart notification types. Marked with the 🎯 icon, it sends official in-game event cards to the group. The goal is not to make players constantly refresh the event screen; it is to ensure that when an official event card appears, the guild sees it in its central communication channel.

Having this option disabled by default is a practical advantage. Every kingdom has its own pace, every guild has a different war intensity, and every group has a different message tolerance. For example, LM Events can create noise in a small attack group used only for target hunting. In contrast, event cards directly support decision-making in a main guild group coordinating Guild Fest or in a KvK preparation channel.

Separate notification preferences according to each group’s purpose:

• Main guild group: LM Events can be enabled for Guild Fest, KvK, and overall kingdom coordination.
• Rally operations group: If rally alerts, shield drops, and burning castle notifications are the priority, LM Events can be enabled only during critical preparation periods.
• Farm or target-hunting group: It can remain disabled to keep the message flow clean.

Check the settings screen used to enable or disable LM Events from the notification list. In LordsRally, !notifications lets you manage the numbered list of 12 alerts with an on/off system. You can also review the 12 notification types guide to learn when to use each war notification.

Turning the event card into an operation plan before Guild Fest

The most common Guild Fest mistake is letting everyone choose tasks individually. Some members chase short tasks, while others leave time-consuming tasks for the final day; as a result, the guild’s total target is put at risk. An LM Events card does not choose tasks or calculate points on its own. However, by placing the official event card in front of the group, it gives R4/R5 a way to share the plan without delay.

A healthy flow can look like this:

• A 🎯 event card arrives in the group.
• R4/R5 clearly defines the target score, task-taking order, and final-day rule in the same chat.
• Members confirm their task status through that same channel.
• War-focused members separately monitor shield and rage management during Guild Fest.

Consider a concrete example: the guild is starting Guild Fest while also facing tension with a neighboring kingdom. When the card reaches the group, leadership can write one operational message instead of two separate announcements: remind everyone about task discipline, identify members who need to shield during night hours, and separate the target-hunting team into its own channel. This way, Guild Fest preparation does not disrupt the war setup.

At this point, the !kingdom command is also useful. Confirming that the actively scanned kingdom is correct is a basic check, especially for guilds using multiple kingdoms or operating after migration. !find, one of LordsRally’s most-used commands, is the fastest starting point when you need a player’s current card, status, and coordinates. You can see all commands on the commands page.

Matching the official card with a war checklist before KvK

Seeing an event announcement as KvK approaches does not mean the war has already started; it means the preparation window is getting shorter. A strong R4/R5 team uses this moment as a checklist trigger rather than a panic call. When the LM Events card arrives, the group should clarify these four areas:

• Shield discipline: During which time window will farm accounts, leader-holding accounts, and members going offline check their shields?
• Rally structure: Which group will include rally leaders, fillers, and players coordinating defensive calls?
• Migration and positioning: Will newly arriving or departing castles be monitored, and is the hive layout changing?
• Target intelligence: Which might range, activity level, and shield status should be prioritized?

The key distinction is this: LM Events brings you the official event context; shield drops, rallies, and castle movement notifications identify the actual war opportunity. Because LordsRally is event-driven, it does not wait for fixed-interval scanning; once the relevant event occurs, the notification usually reaches the group within 1–3 seconds. On a KvK night, that can be the difference between “we will check later” and reacting on time.

For example, if the guild enters defense mode after the official KvK card arrives, leadership can keep 🛡 shield drop and 🚨 rally notifications enabled. If a member’s shield drops or an enemy starts a rally, the operations group sees the event immediately. These notifications do not guarantee an attack outcome; they provide the visibility the right team needs to make a decision at the right moment.

Using event cards, war signals, and target searches in the same flow

Good intelligence in Lords Mobile is not about watching one screen. The official event card provides the strategic framework, while real-time castle signals reveal the opportunity on the field. LordsRally combines these two layers in the same WhatsApp or Telegram group.

A sample KvK preparation flow can look like this:

• An 🎯 LM Events card arrives, and leadership pins the preparation message.
• A 🛬 migration-in notification reveals a strong castle entering the kingdom.
• !find is used to review the player’s current card; guild, activity, might, and status are evaluated in one view.
• !activity is used to check recent movement.
• If the shield drops or the castle starts burning, the attack team regroups to decide whether to rally.

A general player card presents information in this format: guild tag and player name, activity status, coordinates, might, attack power, shield duration, and recent activity details. For example, a search result appears in the following structure:

!find → 🧧 [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 ] buttons.

This example is fictional; the important point is that target research can continue without leaving the conversation after an event announcement. When available in WhatsApp, native interactive buttons open actions such as Info, Equipment, or Track with one tap; when buttons cannot be used, the system safely falls back to a numbered list.

Managing Guild Fest and KvK communication across multiple kingdoms without splitting the team

For teams playing in more than one kingdom or maintaining allied groups across different kingdoms, information clutter grows faster. A KvK preparation message for one kingdom should not land in another kingdom’s farm group; likewise, Guild Fest coordination should not overwhelm the target-hunting chat.

LordsRally supports multiple kingdoms and operates with a separate group structure for each kingdom. This setup makes it easier to route LM Events notifications to the correct operations channel. Each group can use different notification preferences: one kingdom can have event cards and rally alerts enabled, while another can monitor only shield drops and migration movements.

You can also use multi-target tracking for up to 4 targets at the same time to monitor critical enemies separately. A castle that teleports and changes its name is automatically found again through its unique identity, so the team does not need to search for it manually. During KvK, not only the enemy’s name but also its location and behavior changes matter, making this especially valuable.

LordsRally’s 78 commands bring kingdom maps, might and kills leaderboards, migration records, smoking castles, captured leaders, wonder intelligence, and more into one system. Use !heatmap for a kingdom heatmap, !shield_drops for recent shield drops, and !unshielded to filter unshielded targets. You can compare all use cases on the features page and explore guides for different war scenarios in the blog archive.

Keeping message quality high when enabling LM Events

A notification is not useful only because it arrives quickly; the team must also know what to do when they see it. For this reason, it is effective to establish a simple response standard in the group when LM Events is enabled. After an event card arrives, the leadership message should stay under three lines and include: the responsible person, the first check time, and the war-group rule.

For Guild Fest, a clear structure such as “R4 is responsible for tasks, first check is tonight, shield/rally emergencies go to the separate war group” is enough. For KvK, a framework such as “Shield checks must be completed, rally calls will only be followed in the operations group, and migration notifications will be tagged to R4” reduces unnecessary chat.

LordsRally’s value is not in making decisions for your team. It makes official event cards, shield drop notifications, rally alerts, and target data visible without delay; the final decision remains with the guild’s war structure. This 24/7 flow on WhatsApp or Telegram helps maintain preparation discipline, even while leadership is offline.

Frequently Asked Questions

Is the LM Events notification automatically enabled in every group?

No. LM Events is disabled by default and works as an opt-in feature. You can enable it in groups coordinating Guild Fest or KvK and keep it disabled in groups used only for target hunting.

Does LM Events replace shield drop and rally alerts?

No. 🎯 LM Events sends official event cards. For opportunities and risks during war, separate notification types are used, including 🛡 shield drops, 🚨 rallies, 😡 rage, migration, and burning castles. The most efficient setup is to enable these signals together during events according to the group’s role.

Can I use different settings for Guild Fest and KvK in separate kingdoms?

Yes. LordsRally supports multiple kingdoms and can use a separate group structure for each kingdom. This allows you to manage LM Events, shield, and rally alerts according to each kingdom’s own war tempo.

If you do not want official event cards to become disconnected from your war communication before Guild Fest or KvK, configure your LordsRally setup around your plan. Use the commands and features pages to define your flow and create the right notification combination for your guild.