This article explains the dedicated server administration commands and configuration options for Enshrouded, covering how to kick or ban players, manage roles, and adjust server settings. You will learn the exact commands, where to enter them, and how to edit the server config file to control your game world.
Understanding Enshrouded Server Administration
Enshrouded dedicated servers are typically run through the enshrouded_server.exe executable (Windows) or a Linux binary. Unlike some games that have a full in-game admin menu, Enshrouded’s server administration is primarily done through a console window (the terminal where the server runs) and a configuration file (enshrouded_server.ini). There is no built-in web admin panel in the base game, though third-party tools may exist.
To execute any admin command, you must have the server console open. Commands are typed directly into that window and executed by pressing Enter. The output appears in the same console. For most commands, you do not need to be logged into the game itself; the console is the authority.
Essential Admin Commands
The following are the core commands you will use to manage players. Replace <player> with the player’s name (as shown in the player list) or their Steam ID, and <reason> with an optional message.
kick <player> [reason]— Disconnects the player from the server. They can rejoin immediately unless also banned.ban <player> [reason]— Kicks the player and prevents them from rejoining. The ban is stored in the server’sbanlist.txtfile.unban <player>— Removes a player from the ban list, allowing them to rejoin.list_players— Displays all currently connected players with their names and Steam IDs. This is essential for identifying the correct player to target.save— Forces a world save. The server normally autosaves periodically, but this command ensures a save before maintenance.shutdown— Gracefully shuts down the server, saving the world first.broadcast <message>— Sends a message to all connected players (e.g.,broadcast Server restart in 5 minutes).
Note: The command syntax is case-insensitive, but player names are case-sensitive. If you have a player named “Alex” and type kick alex, it may not work. Use list_players to get the exact name.
Player Roles and Permissions
As of the current game version, Enshrouded does not have a granular role system (like Admin, Moderator, etc.) for dedicated servers. There is only one level of administration: the server owner or the person with access to the server console. This is a common point of confusion. If you see references to “admin roles” online, they are usually referring to the fact that the server console is the only admin interface.
However, there is a distinction between the server host and in-game players. The server host (the person who started the server) has full console access. Players who join do not have any special commands unless they also have access to the server’s console (e.g., via remote desktop or SSH). For co-op play, the host can use the in-game pause menu to manage players, but that is separate from the dedicated server console.
If you need to give another person admin capabilities, you must give them the server’s console credentials (e.g., Windows login or SSH key). There is no in-game command to promote a player.
Configuration File Settings
The main configuration file is enshrouded_server.ini, located in the server’s root folder (e.g., C:\Program Files (x86)\Steam\steamapps\common\EnshroudedServer\ on Windows). You can edit it with any text editor while the server is stopped. Here are the key settings:
Name="My Server"— Sets the server name visible in the server browser.Description="A cozy survival server"— Optional server description.Password=""— Leave empty for no password, or set one for a private server.SlotCount=16— Maximum number of players (default is 16).IP=0.0.0.0— Bind address. Usually leave as 0.0.0.0 to accept all connections.GamePort=15636— UDP port for game traffic (default 15636).QueryPort=15637— UDP port for server browser queries (default 15637).SaveDirectory=./savegame— Path to save game files.LogDirectory=./logs— Path to log files.AutoSaveInterval=300— Autosave interval in seconds (default 300).PlayerKickTimeout=60— Time in seconds to wait before kicking an unresponsive player (default 60).
After editing, save the file and restart the server for changes to take effect. Always back up the file before making changes.
Ban Management and Persistent Storage
Bans are stored in a file named banlist.txt in the server’s root directory. Each line contains a Steam ID or player name. You can manually add or remove entries while the server is offline. When the server is running, use the ban and unban commands to modify the list.
To see who is banned, open banlist.txt. If you need to ban a player who hasn’t joined yet (e.g., you know their Steam ID), you can add their Steam ID to this file manually. The server will reject them on connection.
Important: If you use a hosting provider, the banlist file might be in a different location or managed through their control panel. Check your provider’s documentation.
Common Issues and Troubleshooting
Here are frequent problems and how to solve them:
- Command not recognized: The console only accepts commands exactly as listed. If you type
banplayerinstead ofban, it will fail. Check the official server documentation for the exact syntax. - Player name not found: The name must match exactly. Use
list_playersto copy the name. Sometimes names have special characters; you can use the Steam ID instead. - Ban not working: Ensure the server has write permissions to the
banlist.txtfile. If the server runs as a service, it may be running under a user without write access to the folder. - Config changes not applying: The server must be fully stopped before editing the INI file. If you edit while it’s running, the changes are overwritten on shutdown.
- Ports not opening: For players to connect over the internet, you must forward both
GamePortandQueryPorton your router and allow them through your firewall.
Frequently Asked Questions
How do I give a player admin rights?
There is no in-game command to grant admin. The only way is to provide that person with access to the server console (e.g., via remote desktop or SSH). Some hosting panels offer a “console” feature that you can share with a trusted player, but that is external to the game.
Can I ban a player by Steam ID?
Yes. Use ban <SteamID> in the console, or add the Steam ID to banlist.txt. To find a player’s Steam ID, use list_players which displays both name and ID.
What is the difference between kick and ban?
Kick removes a player from the server temporarily; they can immediately rejoin. Ban removes them and prevents reconnection by adding them to the ban list. Use kick for minor issues and ban for repeat offenders.
Where is the server config file located?
It is in the server root folder, named enshrouded_server.ini. If you installed via Steam, it’s typically in steamapps/common/EnshroudedServer. If you use a hosting provider, they may expose it through their file manager.
How do I change the server name or password?
Edit Name and Password in the INI file, then restart the server. Ensure the server is stopped before editing, and save the file before restarting.
Why can’t I see my server in the browser?
Check that QueryPort is forwarded and that the server is not behind a strict NAT. Also, the server may take a few minutes to appear. If you are using a password, players must enter it to see it in the browser.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.
More cards in this drawer
- Tongue Escape Codes: What They Are0.20 movements/s
- HDMI 2.1 Explained: Why It Matters for Gaming
- Veeam Plugin for VMware Cloud Director: How It Works
- Claude Code Workflow Habits Worth Trying
- Best Path of Titans Server Hosting: Top Picks
- Oppo First Foldable: 120Hz Display & Snapdragon 888