Admin Interface – Guide

A management window for server admins and a server help for every player. Everything runs in game, in German or English by game language. The server checks every action itself: what you may do follows from your connection – never from what another player sends.

Requirements#

• Stationeers 0.2.6428, BepInEx 5.4.23.5 and StationeersLaunchPad 1.0 (like all my code mods, see installation).
• The mod in the active mod pack – add new local mods in the LaunchPad menu (key M in the main menu).
• The server and all players need the mod in the same version. It adds no items – remove it and the save stays unchanged.

Quick start#

Clock and buttons on the HUD stay below all windows – they never cover an open window. With Skill & Level System 1.1.1 or later this also applies to its level bar.

In single player and as host you are the owner automatically – nothing to set up.

Setup on a dedicated server#

1. Install the mod on the server (the server's BepInEx folder) and start it.
2. Add your Steam ID (17 digits, e.g. from your Steam profile link) at the server console: admin add 7656119xxxxxxxxxx owner More admins: admin add <steamid> admin or … moderator. List: admin list, remove: admin remove <steamid>. Alternatively BesitzerSteamIds under [3 Server] in BepInEx\config\dominik1199.admininterface.cfg (comma separated).
3. Set a password (recommended on public servers): admin password <new password>, remove with admin password off. Admins then sign in with it in the window. The password never leaves your computer: the server sends a one-time challenge and your computer answers with a value derived from it. After 5 failed attempts you are locked out for 10 minutes (longer afterwards).
4. admin status shows the version, number of admins, password on/off, data folder and whether the restart watchdog is running.

Why a password? The game's dedicated server does not have Steam confirm the Steam ID of a connection. A modified client could pretend to be someone else – with a password it still gets no admin rights.

Roles and rights#

Only the owner changes the rights matrix (section Settings). Sections without the right appear grey with a note. Anyone who is neither admin nor moderator and has no abilities only sees the “Admins only” card after Ctrl+U, with a pointer to the server help.

Abilities are granted per player in the Abilities section: godmode, creative building, infinite tools, vanish, fly, teleport, heal, give, inventory, demolish, admin mode. Level “self only” works on the player only, “others too” on other players as well. With reason and expiry (e.g. 2h, 3d); revoking takes effect at once. Players see their abilities in the server help and switch them on and off there; active ones show as a symbol in the HUD.

The sections#

If a linked mod is missing (Banking System, Skill & Level System, Roleplay & Permissions, Exploration), the Mods & credits section shows a card with what it adds and where to get it.

Restarts with a start script#

A mod can stop the server but not start it again. The mod folder therefore contains two start scripts: Start-Admin-Interface.bat (Windows) and start_admin_interface.sh (Linux). Copy the matching one next to rocketstation_DedicatedServer, fill in SPIELSTAND (save), WELT (world) and your settings at the top and from now on start the server with it (Linux: chmod +x, e.g. in screen/tmux or as a systemd service). The script restarts it after every stop (after a crash after 10 seconds); “Shut down” in the interface creates the file admin_stop.flag, then it stops. The interface shows whether the watchdog is active.

Setting up the Discord bot#

Webhooks alone (messages into channels only) need no bot: in Discord channel → Edit → Integrations → Webhooks → New Webhook → copy the URL and paste it in the interface under Discord (default webhook or per category).

For slash commands, presence and chat bridge:

1. https://discord.com/developers/applications → New Application, name e.g. “My Server”.
2. Bot on the left → Reset Token → copy the token. It is shown only once. Paste it in the interface (Discord → Bot) – only the owner may do that. Afterwards the interface only shows “set · …1234”.
3. Under Bot → Privileged Gateway Intents switch on Message Content Intent only for the chat bridge. Without the bridge the bot needs no privileged intents.
4. General Information on the left → copy the Application ID → enter it in the interface.
5. OAuth2 → URL Generator on the left: scopes bot and applications.commands; bot permissions View Channels, Send Messages, Read Message History (for the bridge). Open the URL and invite the bot to your Discord server.
6. In Discord switch on Settings → Advanced → Developer Mode. Then right-click Copy ID for: your server (guild ID), the channels (status, chat bridge, tickets, announcements) and the roles allowed to use commands.
7. Enter in the interface: guild ID, channels, admin roles (all commands) and mod roles (/kick, /mute, /announce, /say, /save). Everyone may use /status and /players.
8. Press Test. The bot signs in, sets its presence (“3/10 players”) and registers the commands.

Commands: /status, /players, /announce text, /say text, /kick player reason, /ban player duration reason, /unban player, /mute player duration reason, /save. Give players by name or Steam ID, durations like 30m, 2h, 7d. The bot cannot kick or ban admins. Messages from the mod never ping anyone (@everyone is defused).

Token and webhook URLs are kept only in geheim.json on the server, never sent to players and never written to the log.

Anti-griefing and start lander#

Both are off by default. Anti-griefing blocks deconstructing, building onto, using and opening containers of other players' structures – optionally only while the owner is offline. Players keep their friend list in the server help (section Online). If Roleplay & Permissions is loaded, this protection stays off – its plots and rights take precedence.

The start lander gives each new player an own start point with a minimum distance (default 250 m) to everyone else, flat enough to land, with the contents of the start condition, an own crate or just the capsule.

Privacy (for server operators)#

Player logs store sessions, chat, deaths and build actions with location – no IP addresses. The data stays on your server in BepInEx\config\AdminInterface\; none of it is sent to me or to stationeers.de. Chat is deleted after 7 days, the rest after 30 (adjustable). Players see the notice in the server help; on request you delete all data of a player with one click. As the operator you are responsible for this data – mention it in your server rules. The same applies to a Discord connection: you decide what you send to Discord by webhook or bot.

Console#

Settings (dominik1199.admininterface.cfg)#

Multiplayer and data#

The server and all players need the mod. Admins, bans, tickets, polls, content and statistics apply server-wide (BepInEx\config\AdminInterface\), waypoints, game values, stack sizes and start points per save (welten\<name>.json). Bans also apply after switching worlds. More on all mods in multiplayer: Multiplayer and servers.

Limits#

• Fly, vanish and freeze take effect on the player's own computer, because in the game a character's movement belongs to its own computer. A modified client can get around them.
• Vanish hides the model, name tag and lights. Collision, atmosphere and the game's player list (Tab) remain.
• The dedicated server does not have Steam confirm the Steam ID of a connection – that is what the admin password is for.

FAQ#