How Far Back Does the Lords Mobile !names Record Go? A Guide to Reading Tracking History Correctly

Seeing an enemy castle under one name yesterday and being unable to find it today is a common situation in Lords Mobile warfare. Especially during KvK, Baron preparation, or long-running guild wars within a kingdom, players change names, switch guild tags, teleport, or migrate. For a rally leader who relies only on the visible name, this means losing the target’s trail.

In LordsRally, the !names command helps you view the name-change history recorded in the system for a player. However, the critical point is this: you should not read the record history as a fixed period such as “it definitely goes back this many days.” The depth of the history depends on conditions such as how long the castle has been in the scanned kingdom, when events were detected, and when the relevant change entered the system records. The right approach is not to treat !names output as standalone proof of identity, but to cross-check it with other war intelligence.

What Exactly Does !names Do?

!names is used to examine the target player’s name-change history. Its most valuable use in war is helping you connect the name you see today with a name you tracked before.

For example, an enemy player may have activated rage, dropped their shield, or joined a rally under a different name during the previous war. Even if they later change their name to stay less visible inside a guild, name history gives you a starting point for questions like these:

• Could this castle be the player we tracked before?
• Which guild were they in under their old name?
• Did the name change happen around the same time as a migration or guild change?
• Does the target’s gear, activity, and might profile match older records?
• Is a newly visible name in the rally team actually a known fighter?

The important limitation is this: !names only shows name-change history; it is not a complete timeline of every movement. For a player’s full war profile, you should use !find, !info, !activity, !equip, guild, and migration data together.

To view every command by category, open the commands page. LordsRally runs 78 commands in Turkish, English, and Spanish, including search, tracking, war, migration, tiles, and wonder intelligence.

How Far Back Does the Record Go? Read the Recording Logic, Not a Fixed Duration

The most common player question is simple: “How many days of records does !names show?” It would not be accurate to give one fixed number of days that applies to every castle and every kingdom. This is because name history depends on when the system was able to observe and record that change.

In practice, the main factors affecting record depth include:

• How long the player has been in the scanned kingdom
• When the name change was detected by the system as an event
• Whether the castle migrated or left the kingdom
• Whether very old target activity happened before the current monitoring period
• The possibility that the same visible name was used by different players

For this reason, seeing a short history in !names does not mean the player changed their name only once. Likewise, seeing a long history does not mean every historical movement is fully available. The value of the command is not that it tells “the player’s entire life story,” but that it turns recorded name changes into usable context for a war decision.

As an R4, the right question is: “Does this name history support that the target is the same person when combined with my other data?” If the answer is yes, the target can be searched again, added to tracking, and included in the rally plan.

Match Name History with 4 Data Points to Verify Identity

A name-change record may not be enough on its own. In busy kingdoms, similar names, character symbols, and changing guild tags create confusion. That is why you should combine !names results with these four checks.

• Check the current castle card with !find: Current guild, location, might, attack power, activity, and shield status are the first step in confirming the same target.
• Compare activity patterns with !info and !activity: If the old target became active at certain hours, seeing a similar movement pattern under the new name can be a meaningful sign.
• Review the war profile with !equip: The same player’s gear preferences and gear history can strengthen target verification after a name change. However, do not treat gear data as conclusive proof on its own; for a detailed read, see the gear missing-data guide.
• Check guild and migration events: If the player changed guilds, entered the kingdom, or left the kingdom around the same time as the name change, the tracking chain becomes more meaningful.

Example scenario: A fighter from an enemy guild first drops their shield, then changes their name and joins another guild. If the R4 team tracks only the name, the target disappears. But the old-name connection appears through !names; the current castle card is checked with !find; and movement patterns are compared with !info. If might and war profile are also consistent, the castle is added to the tracking list under its new name.

This method is far safer than assuming, “If the name matches, it must be the same player.” Especially in large wars, marking the wrong castle for a rally costs both time and troops.

An Operation Plan to Avoid Losing a Castle That Changes Its Name

Name history is for retrospective analysis; during active war, you need to keep the target under continuous tracking. LordsRally’s tracking infrastructure helps automatically find a castle again through its unique identity even if it teleports and changes its name. This means you do not need to manually search for the target every time.

A practical setup for a rally or hunting operation can look like this:

• First, confirm the target’s current card with !find.
• If there is a suspicious name change, review the historical connection with !names.
• If the target is truly strategic, add it to active tracking with !track.
• Track up to 4 targets at the same time, separately monitoring the enemy rally leader, a castle suspected of being a trap, a fighter activating rage, and a player preparing to migrate.
• Evaluate events such as the target changing guilds, their leader returning, activating rage, or dropping shield inside your group.

LordsRally is event-driven; it does not wait for fixed-interval polling. Detected events such as shield drops, incoming rallies, migrations, or name/guild changes are delivered to your WhatsApp or Telegram group within 1–3 seconds. This matters especially during night shifts: even if a target changes its name, you can continue the operation through tracking and the event chain instead of relying only on chat messages.

If you want to treat target selection after a shield drop as a separate discipline, also review the target selection guide.

In Which War Scenarios Is a Name Change Actually Critical?

Not every name change is an urgent attack signal. The real value appears when you place that change in its war context.

1. Identity concealment before a rally: An opponent may move a known rally leader or powerful fighter into their hive under a new name. !names is the first checkpoint for investigating that player’s former war identity.

2. Rebuilding after migration: If a castle changes its name and guild after entering a kingdom, it may be trying to leave fewer traces in the new kingdom. Reviewing migration alerts together with !names and !find builds a healthier profile.

3. Shield-drop opportunity: If a castle that dropped its shield does not look familiar, checking its history before rushing a rally is sensible. A high-might, active target wearing defensive gear may carry trap risk.

4. Internal war and diplomacy tracking: Noticing that the same player has moved across different guilds can help you understand enemy alliances or the movement of a guild that is breaking apart. Do not use this data to conclude that a diplomatic agreement definitely exists; treat it only as a field signal.

5. Wonder period: Known players around Baron, Chalice, or Paladin may sometimes try to keep their identity less visible. Reading name history together with wonder data, the live Baron board !k71, and !wow timers gives you a stronger framework.

You can use !heatmap for kingdom density, hot zones, and target clusters, and review all capabilities on the features page.

A Name-History Note System for R4/R5

Name history is not data to check once and forget. To improve the intelligence quality of an R4/R5 team, you need a short but standard note system. In LordsRally, you can save personal notes and guild notes; list personal notes with !notes and guild-based notes with !guildnotes.

A useful note template contains these four items:

• Old name and current name connection
• Last known guild and migration status, if applicable
• War role: rally leader, filler, suspected trap, or farm target
• Last verification date and the data used for verification

For example, it is enough to keep a note short: “Old-name connection confirmed; might and gear profile are similar; changed guild after last check.” Instead of unverified judgments such as “definite trap” or “definite rally leader,” writing the observation and verification date creates a more professional war intelligence system.

This structure becomes even more important for guilds playing across multiple kingdoms. With multi-kingdom support, LordsRally can monitor each kingdom in a separate group; rather than mixing old-name information from one kingdom with rumors from another, you manage every operational area in its own record context.

Frequently Asked Questions

Exactly how many days back does !names go?

It should not be interpreted as a fixed number of days guaranteed to be the same for every target. The command shows name-change history recorded in the system; the visible depth may vary depending on the player’s history in the scanned kingdom and when changes were detected.

If name history exists, is it certain that the target is the same player?

No. Name history is a strong trace, but it is not conclusive verification on its own. Evaluate the current castle card with !find, movement patterns with !info and !activity, the war profile with !equip when needed, and guild/migration events together.

Should I immediately rally a target that changed its name?

No. First check shield status, activity, might, gear, and possible rage status. LordsRally’s shield-drop and rally alerts provide data for fast decisions, but the final attack decision should be made through your guild’s scout, front test, and rally plan.

If you want to track opponents who change names and lose their trail more consistently, while collecting shield and rally alerts in one group, review LordsRally’s blog guides; then set up your workflow for your kingdom through WhatsApp or Telegram.