Documentation
Start a game server from Discord
Add a Minecraft, Valheim or Steam server you already run, then start, stop and see who is on it from Discord — without giving anyone access to the machine.
The one thing to understand first
Your machine owns the servers. The bot is a remote control.
It starts them, stops them, reads the player count and creates a world — and that is the whole list. The files, the processes and the address belong to you. Nothing is ever hosted for you, and a server you add is one that already exists on hardware you run.
That is a deliberate boundary rather than a limitation: it means a member pressing Start cannot reach anything on your machine except the server you pointed at.
Add a server
Open /menu › Other › Admin › Game Servers. Five rows:
| row | what it does |
|---|---|
| Set up | Walks you through connecting a server from scratch |
| Detect | Scans for Steam and Minecraft servers already running in Docker, so you do not type names — on the hosted bot it asks your machine, which lists stopped ones too and reads each Steam server where it runs |
| Add | Adds one by hand when you know what you are adding |
| By address | Points at a server by its address — for one that is not on this machine |
| Remove | Takes one off the list |
⭐ Try Detect first. It is the difference between confirming a list and transcribing one.
See who is playing
/menu › Other › Admin › Game Servers › Power lists every server, one row each: up or down, how
long it has been up and how many are playing. Start or Stop sits beside each one.
What members get
Members open /menu › Gaming › Servers and see every server you added, each with one button: Start for a stopped one, View for a running one — how many are on it, the join address and the modpack. A server that cannot start yet is listed with Start greyed out and the reason beside it.
Members cannot stop a server. Stopping one other people may be playing on is yours to do, from Game Servers › Power. An empty server stops itself after a while unless you turned Idle shutdown off — and a game with no player count never stops itself.
⚠ Two limits worth knowing before you plan around them
One deployment points at one machine. The bot can be pointed at the machine of the server it is working for, but there is a single backend behind it — so this is built for your servers, not for running a hosting company out of a Discord bot.
Server names are unique across the whole deployment. If a name is taken you will be told so, without being told who has it. That is on purpose: a name collision is your problem to solve, and who else is running what is not your business.
Questions people actually ask
Does the bot need to be on the same machine as the server? No. The companion runs on your machine and holds the connection open; the bot can be anywhere.
Can I create a new world? Yes — world creation and its settings are part of what the bot can drive, because they are things your machine does on request.
What if the machine is off? The controls say so rather than failing silently. A server the bot cannot reach is reported as unreachable, not as stopped — those are different facts and confusing them is how someone ends up restarting a machine that was fine.