Kick, Ban and Reserved Slots on Enshrouded
See who is on your Enshrouded server, kick or ban a player in game, find the ban list, keep slots free for your regulars, and deal with a problem player.
Seeing who is on
Three places, each useful for something different:
| Where | What it gives you |
|---|---|
| Overview | The Players count, against your slots |
| Console | Joins and leaves as they happen, each with the player's Steam name and SteamID64, and the permissions they were given. Player list opens a Players panel beside the log with who is online and recent joins and leaves |
| Live Map | Players online: everyone's character name, Steam name and grid square, and where they are on the map |
The live map's list is the most useful when somebody needs help: click a name to centre the map on them, and you can see at a glance whether they are stuck somewhere.
Enshrouded's own server reports only how many players are on, with no names, so the names come from the server's log and from GameGrid's server module. Players' IP addresses are never shown, anywhere in the panel.
Kicking and banning
These happen in game, not in the panel. Enshrouded has no console for a server to send a kick through, so Keen put it in the game's own interface.
1. Join the server with the password of a group that has the Kick/ban permission, normally Admin.
2. Open the in-game menu and go to the Social tab. It lists everyone on the server.
3. Select a player and choose kick or ban.
| Action | Effect |
|---|---|
| Kick | Removes them now. They can rejoin immediately |
| Ban | Removes them and adds them to the server's ban list. They are refused on every later attempt |
A kick is for "stop that". A ban is for "do not come back".
The ban list
The game writes bans into your server's settings file (enshrouded_server.json, under bannedAccounts), so they survive restarts. The ban list is not shown or edited on the Settings page.
To lift a ban you cannot lift in game, open a support ticket rather than editing the file by hand: the format matters, and a broken file stops the server from starting.
Reserved slots
Each user group can hold back slots for itself. While a group's reserved slots are free, the server reports itself as full to other groups once the remaining places are taken, so your regulars can still get in.
| You want | Set |
|---|---|
| Admins always able to join | A reserved slot or two on the Admin group |
| Friends to get priority over guests | Reserved slots on Friend |
| Nothing held back | 0 on every group, which is how a new server starts |
Set them in Settings โ Admin โ User Groups. A group's reserved slots cannot be more than your server's Player Slots, and the panel and the Discord bot both check that against your current slot count.
Enshrouded's own limit is 16 players, so plan reservations against that.
Permissions, briefly
What a player may do is decided by the group password they joined with, not by anything you set per player.
| Permission | Lets them |
|---|---|
| Kick/ban | Remove other players |
| Access inventories | Open storage, containers and workstations in bases |
| Edit world | Dig and build outside bases |
| Edit base | Build and remove inside bases |
| Extend base | Add, upgrade and remove Flame Altars |
Every group can fight, gather, explore and do quests in the open world regardless. Full detail: User Groups, Passwords and Permissions.
Dealing with a problem player
A practical order that avoids over-reacting:
1. Talk to them. Chat from your server reaches Discord if you have set that up, so you may already have the context: Sending Enshrouded Chat to Discord.
2. Check the Console for when they joined and what permissions they had. If a guest has been editing bases, their group is wrong, not their behaviour.
3. Change the group's password if a password has spread further than you meant. That is the real fix for "somebody gave the admin password away".
4. Kick to interrupt. Ban if they come back.
5. Restore a backup if something was destroyed. See Enshrouded Saves, Backups and Restore.
What you cannot do
- No in-game messages. Enshrouded gives a server no way to put text on a player's screen, so warnings go to Discord instead.
- No freezing or muting a player.
- No per-player permissions. Groups are the unit.
- No kick or ban from the panel, Discord or the API. Both are in-game actions.
- No player lists. Enshrouded has no admin list, whitelist or ban file of its own to edit, so its Settings page has no Player Management tab. Who may do what is set by the groups on the Admin tab.
What you can do from the panel: move a stuck player with teleport, and hand somebody an item from the live map.