SwansonX Bot
A Discord bot running live in a real community. 16 commands and 12 features, talking to a game server over one outbound WebSocket, covered by 194 tests.
The architecture decision
The game server dials out to the bot. The bot listens and never starts the call. One WebSocket, checked on the upgrade, carrying a small typed envelope both ways.
The other way round, the game server accepts incoming connections. That means a port to open, an attack surface to defend and a firewall rule to get wrong.
Making the connection outbound removes all three at once. It also means a restart on either side heals itself, instead of needing someone to step in.
What it does
16 commands and 12 features spanning both sides. Things that happen in the game show up in Discord, and actions in Discord reach into the game.
It runs in a real community with real players. That is a different bar from a bot in a test server.
Tested, because it talks to production
194 tests.
Anything that can write to a live game server on behalf of a chat message needs to be wrong somewhere safe first. And a bot is unusually easy to test badly: the happy path is trivial, and every interesting case is a disconnect, a restart or a broken message.