How to Set Up and Use LW Spy Discord Bot for Last War

The LW Spy Discord bot gives your entire Last War: Survival alliance access to intelligence scanning directly in Discord. Instead of one person running scans on the web dashboard and relaying results, any authorized member can run commands and see results instantly. Here is how to set it up.

Step 1: Get a Discord Bot Plan

Visit lw-spy.com/pricing and select a plan that includes Discord bot access. Discord bot plans are designed for teams — one subscription covers your entire Discord server. All members with the right role can use the bot.

Step 2: Invite the Bot

After subscribing, you will receive an invite link. Click it to add the LW Spy bot to your Discord server. Grant it the required permissions: Send Messages, Embed Links, and Use Slash Commands. The bot does not need admin permissions.

Step 3: Configure Role Permissions

By default, all server members can use basic commands. To restrict advanced scans to officers, use the bot settings to map Discord roles to scan permissions. For example, allow @Member to use /scan search but restrict /scan alliance and /scan monitor to @Officer and above.

Essential Commands Reference

The most-used commands are: /scan search [player name] to find a player, /scan exposed [server] to find unshielded bases, /scan alliance [tag] to map an alliance, /scan shield [server] to check shield timers, and /scan troops [server] to find gathering armies. All commands return results as rich embeds with player details and coordinates.

Best Practices for War Rooms

Create a dedicated #war-intel channel and restrict it to officers. Use this channel exclusively for scan results during active wars. Pin important scan results (like pre-war enemy alliance maps) for reference. The bot posts results as embeds, making them easy to read and reference during fast-moving war situations.

When the Bot Returns "No Results" or Stale Data

Two failure modes look identical in Discord but have different causes. "No results" on a scan that should have results almost always means you queried the wrong server or alliance tag — the bot does not auto-correct typos, so a single wrong character returns an empty list. Re-check the server number against the in-game world map and the alliance tag against the actual displayed tag (capitalisation matters on some queries). The second failure mode is stale data: the same scan command returns identical results twice in 60 seconds because LW Spy briefly caches the latest result for that exact query. During fast-moving wars where shield states change minute-by-minute, this lag can mislead an officer into thinking a target is still exposed when they have re-shielded. The fix is to vary the query slightly (different filter, different sort) so the cache key changes, or simply wait 60-120 seconds for the cache to expire.

Discord Bot vs Web Dashboard: Which to Open When

The Discord bot wins on reaction time and team visibility — every officer sees the result the moment it lands, no need to relay screenshots. It loses on depth: you cannot apply five filters, scroll a 200-row result table, or save a scan to a personal archive from inside Discord. The web dashboard wins on planning workflows: pre-war enemy alliance audits, multi-day comparison of how a rival shifted positions, building a saved targets list before an event. The rule of thumb most established alliances settle on: bot for live war coordination, dashboard for prep and recap. Trying to do everything inside Discord clogs the channel with stale scan dumps; trying to do everything in the dashboard means your officers wait minutes for someone to copy-paste the result back into the war room. Use both.