The squadron bot

A second bot answers questions about the game: your account, your squadron, the rankings, the market. It works in the official server, and any squadron can also invite it to its own Discord.

It is read only. It cannot change anything in the game, it does not read what you write, and it joins a server with no permissions at all.

What it can answer

Some commands work for anyone, some need your account linked, and some are about your squadron.

Open to everyone, no link needed:

About your account, linked required:

About your squadron, linked and a member required:

/help lists all of it inside Discord, so nobody has to come back here for the names.

Who sees the answer

This is the part worth understanding, because it is what keeps squadron data from leaking.

In a channel your squadron has claimed, the squadron answers are posted publicly, for everyone in the channel to read. Only members get them: someone from another squadron asking there receives nothing at all.

Anywhere else, a squadron answer is about your own squadron and only you can see it. Other people in the channel see nothing, not even that you ran the command.

Your own /status and /market are the exception: those are posted publicly on purpose. You already see your own queues in the game, so the reason to run the command is to show somebody else, and /market is free advertising for what you are selling.

Bringing the bot to your own Discord

Anyone with Manage Server on their Discord can invite it, using the link in /help. It asks for no permissions, so there is nothing to review and nothing to grant.

Then the squadron leader runs /setup in the channel that should belong to the squadron. That is the whole process. The command takes no squadron name: it looks up your account, checks you actually lead a squadron, and binds that one. Nobody can claim a squadron that is not theirs, because there is no way to even name one.

Remember

Only the leader can run /setup, not a rank with high permissions. Whoever owns the Discord keeps the last word anyway: /unlink removes the binding, and it needs Manage Server rather than being the leader, so a server whose leader quit the game is never stuck.

A squadron has one home. Binding it somewhere new releases wherever it was before, so it cannot be public in two servers at once.

Playing in both realms

If you play the web version and the Steam one, your squadron in each is a different squadron. The bot sorts this out by channel, not by asking you: each channel is bound to one squadron in one realm, and the same command in each channel answers about that one. You never pick a realm.

Every answer carries the realm at the bottom, so two similar looking rosters are never confused for each other.

If a channel is bound to both realms, and only then, the commands ask which one you meant.

Automatic notifications

A leader can have the game post events straight into a channel. In a channel that already has /setup, run /subscribe and pick the event. /unsubscribe stops it.

Today there is one: Zone lost, sent when somebody takes a battlefield zone your squadron was holding. The message says which zone, which group was holding it, who took it and what the zone was producing.

Different channels can take different events, so a server can keep battlefield notices apart from everything else. A channel bound to both realms can receive the same event for each of them, and each message says which realm it came from.

/subscribe also takes an optional mention, which posts an @here alongside the notice so the channel is actually woken up rather than left to be read later. Leave it out and the message arrives quietly.

Pinging needs one permission the bot does not otherwise have. In a squadron channel of the official server it is already set up and there is nothing to do. In your own server, open the channel settings, go to Permissions, and allow the bot Mention @everyone, @here and All Roles there. /subscribe checks it and says so if it is missing, because without it Discord delivers the @here as plain text and notifies nobody.

Remember

In a private channel the bot cannot see, notifications never arrive. /subscribe checks this and refuses instead of accepting quietly, but if a channel is made private later, add the bot to it.

What the bot cannot do

Worth saying plainly, since it lives in servers that are not ours:

• It cannot write anything to the game. There is no command that spends, sends, joins or changes anything.
• It does not read messages. It only receives the commands typed at it.
• It joins with no permissions, so it cannot create channels, hand out roles or moderate.
• It only shows squadron data to members of that squadron, checked at the moment you ask and never remembered from before.

Removing it from a server erases the bindings and the subscriptions of that server on the spot.

TL;DR:

• Read only, no permissions, does not read what you write.
• /squadron, /player, /leaderboard and /timers work for anyone; the rest needs your account linked.
• In a claimed channel, squadron answers are public but only for members. Anywhere else, they are about your squadron and only you see them.
• The leader runs /setup and cannot name any squadron but their own. Manage Server undoes it with /unlink.
• The channel decides the realm, so playing both never means picking one.
• /subscribe posts game events into a channel, with an optional @here. Zone lost is the first one.