Vetting LastWar Players: How to Read Their History Before You Trust Them

Look up any LastWar player's full history — alliance hops, name changes, level and rank changes — before you accept an applicant or trust a DM.

Someone applies to your alliance, or a stranger DMs you a deal that sounds too good. Before you commit, you want to know: who is this player, really? LastWar Atlas tracks a per-player audit log — every alliance they've left, every name they've worn, every rank they've held. Look them up before you say yes.

What you can see

Open the player search, type the name, and click View History. You'll get a timestamped feed of:

  • Alliance changes — every tag they've flown, in order. A player who's burned through five alliances in a month is telling you something.
  • Name changes — old name → new name. Useful for spotting players who rename to escape a reputation.
  • Level and rank changes — how fast they're growing, and what rank they held in past alliances (R5 → R1 → gone is a different story than R1 → R4 → R5).
  • King-of-warzone changes — which servers they've ruled, if any.
  • Career changes — switches between War Leader and Engineer.

The header also shows their current alliance, coordinates, level, total power, and non-army power, plus a copy button for their UID.

Vetting an applicant

You're an R4 reviewing a join request. Pull up their history and ask:

  1. How many alliances in the last 30 days? One or two is normal. Five-plus is a drifter or a scout.
  2. Did they leave an enemy alliance recently? Spies are a thing. Cross-reference the tag against your kill list.
  3. Rank pattern in past alliances. R5 → R1 → gone reads very differently than R1 → R4 → R5. The rank history tells you whether other leaders trusted them.
  4. Career flips. A player who toggles between War Leader and Engineer right before applying may be re-spec'ing for whatever they think you want to hear.
  5. Name changes that line up with alliance exits. Renaming on the way out the door is a tell.

None of these are automatic disqualifiers — context matters. But "joined and left six alliances this week" is a conversation worth having before you hand them an R3 slot.

Reading an unsolicited DM

A stranger pings you about a trade, a coordinated attack, or a "great deal on credits." Before you reply, look them up. Is their current alliance hostile to yours? Are they newly renamed from someone you've blocked? Have they been bouncing between alliances all week? Thirty seconds of due diligence saves a lot of regret.

Where to start

→ Look up a player

You can also click any base on the interactive map and hit View History in the popup — same data, different entry point.