Steam Group Whitelist on Space Engineers Server

This guide walks you through setting up a Steam group whitelist on a Space Engineers dedicated server. This restricts joining to only players who are members of a specific Steam group, which is useful for private servers with friends or a community. You’ll need admin access to the server’s config files and a Steam group with a custom URL.

What You’ll Need

• Access to the server’s SpaceEngineers-Dedicated.cfg file (usually in the server’s root folder or DedicatedServer64 folder).
• A Steam group you own or have admin rights to. The group must have a custom URL (e.g., https://steamcommunity.com/groups/MyGroupName).
• Steam Web API key (optional but recommended for verification). Get one from Steam Community Dev.
• A text editor like Notepad++ or VS Code.

Step-by-Step

1. Stop the server – If the server is running, shut it down gracefully to avoid config file conflicts.
2. Locate the config file – Navigate to your dedicated server folder. The file is typically named SpaceEngineers-Dedicated.cfg. If you use a hosting panel, use its file manager.
3. Open the config file – Open it with a text editor. It’s an XML file with many settings.
4. Find the whitelist settings – Search for <Administrators> or <Whitelist>. If there is no <Whitelist> element, you may need to add it. The relevant section is usually near the top.
5. Set the whitelist mode – Look for <EnableWhitelist>. Set it to true. If the element doesn’t exist, add it inside the <Settings> block (or the root element depending on version).
6. Add the Steam group ID – In the <Whitelist> element, add a new line: <SteamGroupId>YOUR_GROUP_ID</SteamGroupId>. Replace YOUR_GROUP_ID with your group’s numeric ID (see Tips).
7. Optional: Add Steam Web API key – If you have an API key, add it in <SteamApiKey> element. This helps the server verify group membership reliably.
8. Save and close – Save the file and close the editor.
9. Restart the server – Start the server again. The whitelist should now be active.
10. Test – Try joining with a Steam account that is NOT in the group. It should be rejected. Then try with an account that is in the group – it should connect.

Common Mistakes

• Using the group’s custom URL instead of the numeric ID – The config requires the numeric Steam Group ID (a 64-bit number), not the URL text.
• Forgetting to set EnableWhitelist to true – Just adding the group ID does nothing unless the whitelist is enabled.
• Editing the wrong config file – Some installations have a sample config or multiple copies. Make sure you edit the one the server actually uses.
• Not stopping the server before editing – The server may overwrite your changes on shutdown if it’s still running.
• Using a group that is not public – If the group is private or restricted, the server may not be able to verify membership. Make the group public or at least allow the API to see members.

Tips

• How to get the numeric Group ID – Go to your group’s page on Steam. The URL is like steamcommunity.com/groups/YourGroupName. Open the page source (Ctrl+U) and search for "gid" or "groupID64". You’ll find a number like 103582791429521412. That’s your ID.
• Use the Steam Web API to verify – Without an API key, the server might rely on cached data. Adding a key ensures real-time verification. Get one free from Steam.
• Backup your config – Copy the original config file before editing. If something goes wrong, you can restore it.
• Whitelist overrides admin – Even if you are an admin, if you are not in the whitelisted group, you won’t be able to join. Make sure your admin accounts are also in the group.
• Test with a second Steam account – Use a different account to test the whitelist, so you don’t lock yourself out.

Troubleshooting

• Server won’t start after editing – Likely a syntax error in the XML. Check for missing closing tags or extra characters. Revert to the backup and try again.
• Players can still join even if not in the group – Ensure EnableWhitelist is indeed true and that the config file is the one being read. Also, check if the server is using a different config path (e.g., via command line arguments).
• Players in the group are kicked – The server might not be able to fetch group membership. Check if the group is public and that the API key is correct. Also, ensure the server has internet access to Steam.
• Group ID not found – Double-check the numeric ID. You can also try using the group’s custom URL in the config (some versions accept it), but the numeric ID is more reliable.
• Whitelist works but admins are kicked – Admins are not automatically exempt. Add the admin Steam IDs to the <Administrators> list, but they still need to be in the whitelisted group.

Frequently Asked Questions

Can I whitelist multiple Steam groups?

No, the config only supports one group ID. If you need multiple groups, consider using a plugin or script that manages a list of allowed Steam IDs.

Do players need to set their group to public?

Yes, the server needs to be able to see the group’s member list. If the group is private, the server cannot verify membership and will reject everyone.

Will the whitelist affect offline mode?

No, the whitelist only applies to online multiplayer connections. If the server is in offline mode, it bypasses Steam authentication, so the whitelist won’t work.

Can I use the whitelist with a password-protected server?

Yes, you can combine both. The whitelist checks Steam group membership, and the password is an additional layer. Both must be satisfied to join.

How do I remove a player from the whitelist?

You remove them from the Steam group. The server will automatically deny them on their next join attempt. There’s no per-player whitelist in the config.

Does the server need to restart after changing the whitelist?

Yes, the config is read at startup. Changes take effect only after a restart.

Related

• Freezing vs Refrigerating Leftovers: Which Tastes Better?
• Upcoming Apple Watch Rumors: What to Expect Next
• Could Stranded Natural Gas Power an Offshore Data Center?