Last War Alliance Verification & Discord Role Sync Guide

1. The Problem: Spies & Manual Role Chaos

In Last War: Survival, operational security is everything. When enemy alliances prepare for Saturday Kill Events or Capitol Conquests, having unauthorized players lurking in your alliance Discord voice channels or strategy rooms can cost millions in lost resources and broken shields.

Traditionally, R4 officers spent hours cross-referencing in-game usernames with Discord tags, manually assigning roles, and purging players who left the alliance. The moment someone promotes an officer or kicks an inactive player in-game, the Discord permissions immediately fall out of sync.

2. How Last War Companion Verification Works

Last War Companion bridges the gap between your game server and Discord. When a player enters /verify in your server:

• The bot queries public game server telemetry to confirm the player belongs to your bound alliance tag and server.
• It inspects their real-time rank: Leader (R5), War Officer (R4), or Member (R1–R3).
• It grants the corresponding Discord roles automatically and syncs their Discord server nickname to match their exact in-game handle.
• If a verified user leaves or is kicked from your alliance, running /audit flags them immediately for one-click removal.

3. Step-by-Step Setup Guide

Step 1: Invite Last War Companion

Add the bot to your server using the official authorization link. Granting administrator permissions ensures the bot can manage channel permissions and nicknames seamlessly.

Step 2: Bind Your Alliance Server

In your admin or officer channel, run the /setup command. Provide your exact alliance tag (3 to 4 characters) and your home warzone number:

The bot automatically provisions three secure roles in your server if they don't already exist:

• [TOP] Leader (R5)
• [TOP] Officer (R4)
• [TOP] Member

Step 3: Direct Members to Verify

Create a #welcome-verification channel where newly joined members can run:

Within 2 seconds, the bot validates their credentials, updates their nickname, and grants full alliance access.

4. The Critical Role Hierarchy Rule

To prevent the dreaded Missing Permissions error:

1. Open your Discord server Server Settings ➔ Roles.
2. Locate the Last War Companion role in the list.
3. Click and drag it to the top, above the R5, R4, and Member roles.
4. Save changes.

5. Running Live Roster Audits

Alliances are fluid. Players migrate, transfer warzones, or quit. Last War Companion includes an automated auditing engine:

The bot cross-references every Discord member holding an alliance role against your live 100-member in-game roster. It produces a clean breakdown:

• Verified Members Present: Active players in both game and Discord.
• Unlinked Discord Users: Server members who haven't run /verify yet.
• Former Members Detected: Discord users who still have member roles but are no longer in the alliance roster (potential security leaks).

6. Frequently Asked Questions

What if a player changes their in-game name?

The commander can simply re-run /verify player_name:NewName. The bot updates their record and syncs their Discord nickname instantly.

Can an enemy spy verify as our alliance leader?

Each in-game UID can only be linked to a single Discord account at a time. Furthermore, R5 and R4 role verification requires officer confirmation in high-security warzones.