grid0plus-discord

The Discord bot for a GRID0+ server. It is the only way to create a GRID0+ account: a person runs /register in the community's Discord and gets a login and password to type into their Switch's "Link Nintendo Account" screen.

Why a bot

A GRID0+ account used to come from a public web form, and every console also left behind a throwaway account when it linked. Discord is where the group already is. It knows who each person is, so a GRID0+ account belongs to the Discord account that made it, a password nobody has to invent, and a place for the rest of the account chores (friends, avatar, "who's on").

Commands

Command	What it does	Who sees the answer
/register	Creates your account and shows your login (your Discord username) and a generated 8-character password. Copies your Discord avatar to your Switch profile.	only you
/register username:alice.psn	An extra account, with a login you choose, beside the first one. Repeat it for as many as you want.	only you
/link	For an account made before the bot: enter its login and password in a private form to connect it to your Discord. Works for a second account too.	only you
/reset-password	A new password. The old one stops working. disconnect_all_accounts defaults to true; set it to false to keep linked consoles signed in.	only you
/reset-password username:…	A new password for that one of your accounts instead of your first (autocompletes from your own logins).	only you
/set-password	Choose your own password (8 to 64 characters, typed twice in a private form). Only for an account you already have; consoles stay signed in. Takes username:… like /reset-password.	only you
/splatoon-save-wipe	Asks to confirm, then deletes your Splatoon 3 cloud save on GRID0+ (archived on the server first). For after you put a different save on your Switch: the game plays from the console's save and uploads only changes, so the old cloud copy would otherwise mix with the new one. username: picks another of your accounts.	only you
/splatoon-save-upload file:	Asks to confirm, then replaces your Splatoon 3 cloud save on GRID0+ with the one inside a save.dat you attach (archived on the server first). The game takes the cloud save over the one on the console, so this is how a save made elsewhere counts on GRID0+. Close Splatoon 3 first. Off unless the server has the save key table set up. username: picks another of your accounts.	only you
/whoami	Login, friend code, linked consoles, friends, status	only you
/fc	Your friend code	only you
/fc-add user:@someone or code:SW-…	Sends a friend request. If they already asked you, you become friends.	only you
/fc-pending	Requests waiting for you (Accept / Decline buttons) and the ones you sent (Cancel)	only you
/fc-remove friend:	Removes a friend (autocompletes from your list)	only you
/friends	Your friends and what they're doing	only you
/avatar	Re-copies your Discord avatar to your Switch profile picture	only you
/online	Everyone on GRID0+ right now, except people whose Switch presence setting is "only me"	the channel
/status	Whether each GRID0+ service is up, and how many people are on	the channel

Splatfests

On when fest.mod_role_ids and fest.review_channel_id are set. GRID0+ keeps every fest, vote and game; the bot is the front end. Players on a console without CFW, reaching GRID0 over its ZeroTier relay and playing over LAN, count in the same fests as GRID0+'s online players.

Command	What	Who sees it
/fest-mod create	Mods. Posts a fest vote: a title, the announcement text (asked for in a form), and the three teams Alpha, Bravo and Charlie, each with a name, emoji and role. Tie it to an in-game fest with game_fest: (teams in the BCAT pack's order), or give start:/end: for a LAN-only fest. channel: overrides fest.channel_id.	the channel
reacting on the vote post	Joins that team and gives its role. The first pick is final, as in game: a reaction for another team is taken back with a DM. Needs a GRID0+ account. Picking a team in Splatoon 3 gives the role too, the moment it happens.
/fest submit	Reports a LAN game you played: its type (Open, Pro, or Tricolor, which only opens in the second half with the halftime leader defending, so up to six losers), winners, losers, optionally each player's paint (winners first, - if unknown) and a screenshot. Every player needs an account and a team. The other players are pinged and can Dispute it. Mods get it in the review channel with Accept / Refuse; the submitter is DMed the result (and a refusal's reason). An accepted game counts exactly like an online win; missing paint is the fest's online average.	only you, plus a notice in the channel
/fest me	Your team, games, wins, contribution and submissions in the current fest. Never team totals.	only you
/fest standings	What the game would show right now: nothing during the first half, the halftime ranking from the second half (places only, no percentages, as in game), the results once out.	only you
/fest help, /fest-mod help	What each command does.	only you
/fest-mod cancel	Mods. Removes the current fest's vote post. A LAN-only fest is deleted with its votes and games.	only you

The bot posts on its own, pinging the three team roles, when play opens, the halftime report, when play ends, and the results (no Conch Shells: GRID0+ scores none, since GRID0 LAN players can't earn any it sees), after which it takes the team roles back. These reply to the vote post, unless fest.announce_channel_id sends them to a channel of their own (then they link to it), so the vote channel holds only the vote. In-game votes arrive over a stream GRID0+ keeps open (it needs redis.url set on GRID0+); after a restart the bot catches up once on votes and reactions it missed.

Mod commands are a command of their own (/fest-mod, /salmon-mod), because Discord hides whole commands, not subcommands. They are hidden from everyone without Manage Server; to show them to mods, allow the mod role on them in Server Settings → Integrations → the bot. Whatever Discord shows, the bot only obeys fest.mod_role_ids.

Salmon Run over LAN

On with the Splatfest settings (it uses the same mods and review channel). GRID0+ keeps the rank, and it is the same rank the game shows online: a player who only ever plays over LAN opens Salmon Run online at the rank they earned.

Command	What	Who sees it
/salmon request teammate1: [teammate2:] [teammate3:] [modded:]	Sets up a job for you and 1–3 teammates (all need an account). Answers the current rotation's stage and the hazard level: each player's rank as a number (title × 100 + points, Eggsecutive VP 800 + points, at most 1665), averaged, × 0.2%, to the nearest 5%, at most 333%. Weapons stay on random. Above 200% without modded:True (the host has the IPS patches that allow going above 200%), the job is played at 200% and a clear is worth +10.	the channel
/salmon report job: result: [disconnect:]	A player reports a clear or the wave lost in. disconnect:True means a teammate disconnected, which halves a loss's cost (−10/−5/0) as in game. Goes to the review channel; nothing moves until a mod accepts. Everyone is DMed their new rank.	only you
/salmon rank [user:]	A rank and Eggsecutive VP stage badges (bronze 400, silver 600, gold 999).	only you
/salmon help, /salmon-mod help	What each command does.	only you

Points: clear +20, lost in wave 1 −20, wave 2 −10, wave 3 0. Each new rotation keeps the title and resets the points to 40 (200/300/400 at Eggsecutive VP with that stage's badge), online and over LAN alike. A job can't be reported or accepted after its rotation ends.

Help

/help lists what you can use, and /help category: explains one category. Mod categories show only to mods.

Downtime alerts

With alerts.channel_id set, the bot reads GRID0+'s health every minute and posts when a service has been down for three reads in a row (a deploy's restart is not an outage), pinging alerts.ping_role_id, and again when it is back, with how long it was gone.

Passwords are never logged or stored by the bot. GRID0+ keeps only a bcrypt hash, so nobody can read one back later, the admin included.

More than one account

One Discord account can own several GRID0+ accounts: /register username:… for each extra, /link for accounts that predate the bot. The first one you made is your first account — that is what /whoami, /fc, /friends and a bare /reset-password act on — and the rest are reachable by naming their login.

Naming a login on /reset-password can only ever reach your own: GRID0+ resolves it through the accounts your Discord account owns, and answers the same way for a login that is somebody else's as for one that does not exist, so no login's existence is readable by asking.

How it works

The bot is a thin client. It never touches GRID0+'s database; every action is a call to GRID0+'s bot API (internal/baas/botapi.go in the GRID0+ repo), a loopback-only listener inside baas that shares its rules with the console's own endpoints. Each call carries:

• Authorization: Bearer <baas.bot_api.token>, which proves it's the bot;
• X-Discord-User-ID, the person, taken from Discord's interaction payload and never from anything they typed.

An unregistered Discord id gets "not registered", never someone else's account.

Setup

1. In the Discord developer portal, create an application and a bot, and copy the bot token. No privileged intents are needed.

2. Invite it with the bot and applications.commands scopes: https://discord.com/oauth2/authorize?client_id=<application id>&scope=bot+applications.commands&permissions=268561472 (View Channels, Send Messages, Embed Links, Attach Files, Read Message History, Add Reactions, Manage Messages, Manage Roles -- the last three only matter for Splatfests; permissions=0 is enough without them).

3. On the GRID0+ host, set baas.bot_api in GRID0+'s config.yaml (listen: "127.0.0.1:8096", token: from openssl rand -hex 32) and restart switchnet-baas.

4. Build and install the bot:

   go build -o switchnet-discord .
   sudo mkdir -p /opt/switchnet-discord
   sudo cp switchnet-discord config.example.yaml /opt/switchnet-discord/
   sudo cp /opt/switchnet-discord/config.example.yaml /opt/switchnet-discord/config.yaml
   # edit guild_ids (and api_url if you changed the port)
   printf 'SWITCHNET_DISCORD_TOKEN=%s\nSWITCHNET_BOT_API_TOKEN=%s\n' '<bot token>' '<bot_api token>' \
     | sudo tee /etc/switchnet-discord.env >/dev/null
   sudo chmod 600 /etc/switchnet-discord.env
   sudo cp deploy/switchnet-discord.service /etc/systemd/system/
   sudo systemctl daemon-reload && sudo systemctl enable --now switchnet-discord
   

   The commands appear in the configured servers as soon as the bot connects.

5. For Splatfests: give the bot Manage Roles with its role above every team role, and Add Reactions, Manage Messages (to take back a second reaction), Send Messages, Embed Links and Attach Files in the fest and review channels (Send Messages and Embed Links in the announce and alerts channels too). Set fest.* (and alerts.*) in config.yaml. Still no privileged intents.

Updating

deploy/deploy.sh [ssh-host] builds for the host's architecture, replaces the binary and restarts the service.

Development

go test ./...
go vet ./...

SWITCHNET_DISCORD_TOKEN and SWITCHNET_BOT_API_TOKEN override the file, so a local config.yaml never needs to hold a secret.

Network activity

The bot watches N on GRID0+ · M playing. N includes idle ONLINE and PLAYING accounts, counted once each under the server's existing presence expiry rules. SELF/private presences remain excluded, as in /online. It polls the protected /bot/v1/presence-count endpoint every 15 seconds with a five-second deadline; one loop handles reconnects, and unchanged counts cause no Discord update. An API outage displays status unavailable instead of retaining a stale number. This counts accounts, not physical consoles or distinct Discord owners.

Tournaments

The optional tournament manager provides account-checked slash registration, accepted teammate invitations, 1v1/2v2 single-elimination brackets, organizer-covered timezone scheduling and best-of-three result reporting. It persists state across restarts and exposes failed notifications instead of silently losing invitations. Enable it with tournaments.store_file; see the tournament guide for configuration, command examples, scheduling rules and recovery procedures.