/scout player:<name>
Scout the enemy line-up mid-battle
Name any player and get their team's vehicle line-up — tanks, AA, fighters, helis — pulled from the replay of their latest squadron battle. One command, answered in seconds.
Squadron battles · SQB & SRE · Discord
Scout the enemy line-up, auto-log every SQB battle your squadron plays, and replay the whole match as a timelapse — posted straight into your Discord.
A free alternative to BOTSRE · setup is one command · no game account access
Capabilities
War Thunder publishes a replay of every squadron battle — SQB and SRE alike. WT Scout reads those files directly, so nobody screenshots, nobody transcribes, nobody guesses.
/scout player:<name>
Name any player and get their team's vehicle line-up — tanks, AA, fighters, helis — pulled from the replay of their latest squadron battle. One command, answered in seconds.
/setlog
Every finished battle posts its own both-teams scoreboard to your channel, and a 🏁 session summary wraps the night: win–loss, per-battle results, top players by score.
🎥 render video
Every logged battle carries a render button — one click produces a top-down timelapse of the entire match: every spawn, push, and cap, in motion.
/scout player:<name> full:true
Both teams rendered as an image — vehicle art, MVP and first-blood badges, map background, and a definitive win/loss line read from the replay itself.
The battle log
Never wrong, never late. What the bot posts after every SQB — who played what, who carried, and who drew first blood. (Illustrative names; the real thing uses your battles.)
| Falcon_LeadMVPM1A2 Abrams | 1240 |
| BravoSixChallenger 2 | 860 |
| DuckhunterItO 90M | 540 |
| Night_OwlF-16C | 420 |
| GreyAlphaFIRST BLOODT-80U | 980 |
| VolkTwoSu-27 | 610 |
| Sokol_9Ka-52 | 330 |
| ZhelezoPantsir-S1 | 180 |
SQB session summaries
An hour after the last battle (or on /endsession), the bot closes the session: the record, every battle and who it was against, squadron-rating movement measured start to finish, and your players ranked by score.
Setup
Add it to your squadron's Discord with the button below. It needs nothing but permission to post.
An admin runs /setsquad <your squadron> — the name as it appears on the War Thunder community page. That's the whole setup.
Anyone can /scout player:<name> during a battle. Turn on /setlog #battle-log and every match logs itself from then on.
Questions
Everything WT Scout knows, it read from a replay War Thunder published itself.
A Discord bot that follows a squadron's Squadron Battles — SQB, also called SRE (Squadron Realistic Events) — and posts what happened without anyone screenshotting or transcribing it. WT Scout reads the replay War Thunder publishes for every squadron battle, so it can name the enemy line-up, post both teams' scoreboards, and close out the night's record straight into your channel.
No. WT Scout never asks for your War Thunder credentials, never touches the game client, and installs no files or mods. It reads only what War Thunder itself publishes on the official replay portal — the same pages anyone can open in a browser.
Nothing. Adding WT Scout to your Discord and using every one of its commands is free.
Three steps, about a minute. Add the bot to your Discord, have an admin run /setsquad <your squadron> — the name as it appears on the War Thunder community page — then /setlog #battle-log. From then on every squadron battle posts its own scoreboard about 10–15 minutes after it ends, and the session summary follows roughly an hour after the last battle, or immediately on /endsession.
Guides
Setup guide
Add the bot, set your squadron, turn on the log, and what happens after each battle.
Command reference
/scout, /setsquad, /setlog, /logstatus, /endsession, /help and the render button.
Squadron battles explained
Seasons, squadron rating, the weekly max BR schedule, and the public replay of every battle.
Classified
In the works right now. This card fills in when it ships.
Ready when you are