Lords Mobile KvK Preparation: Read the Enemy Kingdom in 72 Hours and Build a War Plan

In KvK, most guilds limit preparation to training troops, gathering resources, and stocking shields. These are necessary, but what often determines the advantage in the first hour of war is understanding how the enemy kingdom is organized in advance. Which guild is war-ready, which hive is empty, which players are migrating in, and which areas are constantly burning? If you start looking for these answers on war day, the opponent may have already zeroed their first targets.

The goal of this guide is to build a simple but effective intelligence file on the enemy kingdom around 72 hours before KvK opens. Whether you are R4/R5, a rally leader, or an active player on the attack team does not matter: if you have a shared plan, everyone evaluates the same targets and risks.

1. First 24 Hours: Measure the Kingdom’s Overall Pulse

Your first task should not be searching for individual players, but seeing the kingdom’s structure. Total castle density, activity, the number of shielded players, and the strongest guilds in the enemy kingdom tell you the scale on which the war will be fought. In a kingdom where many strong guilds are gathered in the same area, teleporting randomly carries more risk than looking alone for easy prey.

Start by answering these four questions:

How many different power blocks are represented among the top 25 guilds by might?
Are guilds with high kill scores also near the top of the might rankings?
Are large guilds concentrated in one hive, or spread across the map?
Is there battle activity around the kingdom center and Wonder area?

Within LordsRally, the `!kingdominfo`, `!top_guilds`, and `!top_guilds_kills` commands help create this initial picture. A power ranking alone is not enough. For example, a guild with 20 billion total might may not appear on the field on day one if its members are shielded and inactive. In contrast, a compact guild with lower total might but high kill scores can be an active rally threat.

Practical example: If you see three guilds consistently near the top in both might and kill tables, mark them as the main defensive block. In your war plan, view those guilds’ hives not as solo-hunting zones, but as areas with rally pressure and counterattack risk.

For a broader event-preparation setup, you can also add the KvK and event calendar plan to your war room routine.

2. 48 Hours Before: Map Hives and Approach Zones

In KvK, finding a target and approaching it safely are not the same thing. An unshielded castle visible on the outer edge of a hive may be bait for rally leaders waiting inside. Therefore, look not only at castle count, but also at the distance between castles and nearby camp/tile activity.

Use `!hives` to identify the kingdom’s notable hives, then use `!heatmap` to see high-density areas. A dense area on the heatmap is not always the place to attack; sometimes it is the area that will cost you the most time and speed-ups in battle. Especially in crowded zones near the center, a player who teleports in can trigger many counter-movements within seconds.

Divide hives into three categories:

Red zone: Areas where strong guilds are concentrated, with constant support and rally risk.
Yellow zone: Areas with active but scattered guilds; potentially suitable for fast hit-and-run actions.
Green zone: Low-density, inactive, or farm-heavy areas; safer starting points for points and resource targets.

Concrete scenario: If more than 50 castles from the same guild form a tight block on the map, do not teleport into that hive alone to scout. First, check the activity of players on the outer ring. If there are many nearby camps and tiles, the chance that players are online increases. In this situation, it is safer to set two teleport points for the attack team: one close to the target and another on the outer line for retreating and regrouping.

3. 48–24 Hours Before: Read Migration Activity as a Threat Signal

Migration is one of the most overlooked signals before KvK. Powerful players entering a kingdom are not merely new targets or new enemies; they are often part of an approaching war plan. If several accounts from the same guild enter the kingdom in a short period, it may indicate that guild is gathering for Wonder, rallies, or defense.

The goal here is not to hunt every migrant, but to record the change. Use `!migrations`, `!migrationsin`, and `!migrationsout` to separate these three situations:

Individual migration: It may be account movement, a guild change, or a personal decision.
Consecutive migrations from the same guild: The likelihood of an organized team setup rises.
Powerful players leaving the kingdom: Defensive strength may be declining; however, the empty space may be filled by new migrants.

Use a simple record system: categorize players who arrived in the last 24 hours as high might, same guild, accounts with Wonder history, and unknown location. Three strong accounts from the same guild arriving is not an attack order by itself. But if those three accounts settle in the same hive area and the guild also has high kill scores, move that region into the red-risk category.

For players evaluating migration cost or alternative target kingdoms, the kingdom and migration tools on the commands page help prevent rushed decisions on war day.

4. Final 24 Hours: Create Target Roles, Not Just a Target List

The biggest mistake when creating a KvK target list is giving everyone the same label: “unshielded, hit.” An unshielded castle can be an empty farm, an online trap, rally bait, or a newly teleported fighter. Therefore, classify targets not by name order but by their role.

Four effective target roles are:

Point target: A low-risk castle with confirmed inactivity or one positioned outside a hive.
Scout target: A castle being watched to gather information; no attack decision has been made yet.
Rally target: A target whose troop setup and support situation appear suitable for a team attack.
Avoid target: A castle showing activity signs, located in a strong hive, or likely to be defensive bait.

Write down three pieces of data for every target: last known location, associated guild, and latest activity sign. Even this simple list significantly reduces confusion in the war room. For example, if a player has high might but belongs to a scattered guild, is located in an outer area, and has remained in the same spot for a long time, they are first a scout target. In contrast, a lower-might castle sitting in the middle of the main hive is not a point target; it is a possible trap.

The same logic applies on the rally-defense side. Your guild should know in advance who is online, who will refresh shields, and who is ready for a counter-rally. To avoid leaving formation and frontline decisions until the final seconds, see the correct formation guide for rally defense.

5. 60 Minutes Before War Starts: Establish Notification and Communication Discipline

In the first hour of war, an abundance of information becomes noise if it is not managed correctly. If every shield drop or migration is posted to the whole guild, rally calls become impossible to see. R4/R5 teams should therefore divide notifications into three channels: urgent threats, targets to monitor, and developments for record-keeping only.

The rule at this stage should be simple: When a notification arrives, the assigned player makes the decision; not everyone teleports randomly to the same target. For example, when a target’s shield drops, the first player checks activity, the second player reviews the nearby area, and the rally leader decides whether to attack or wait. This three-person mini role assignment is better than having 20 people waste teleports at the same time.

Because LordsRally can deliver events such as shield drops and rally alerts to a WhatsApp or Telegram group within 1–3 seconds, it provides a natural early-warning layer for this task distribution. Guilds monitoring multiple kingdoms should decide in advance which alerts will be enabled; disable unnecessary alerts and prioritize notifications that affect war decisions. You can review notification types and kingdom intelligence options on the features page.

Final checklist: Are the attack group, defense group, teleport point, backup shield plan, and target-record owner all assigned? If one of these five points is missing, close that gap before the war begins. In KvK, preparation is not about finding the strongest account; it is about ensuring the right player uses the right information at the right time.

Frequently Asked Questions

Which data should I check first in the enemy kingdom before KvK?

First examine the strongest guilds and guilds with the highest kill scores, then hive density and recent migration activity. Start searching for individual targets only after you understand the kingdom’s main war blocks.

Is every unshielded castle in the enemy kingdom a KvK target?

No. A dropped shield only opens an attack window. Do not make an attack decision before checking the target’s hive position, activity status, guild, and possible nearby support.

How many hours before KvK should I start collecting intelligence?

The ideal starting point is around 72 hours. In the first 24 hours, map the kingdom structure; in the next 24 hours, monitor migration and hive changes; in the final 24 hours, clarify target roles and guild task assignments.

To organize your KvK war room more effectively, review other war and intelligence guides on the blog and rehearse the command flow based on your guild’s needs in advance.