{"id":20985,"date":"2026-04-02T14:38:40","date_gmt":"2026-04-02T14:38:40","guid":{"rendered":"https:\/\/xgamingserver.com\/blog\/the-isle-evrima-server-admin-guide-commands-bans-and-moderation\/"},"modified":"2026-06-15T19:22:36","modified_gmt":"2026-06-15T19:22:36","slug":"the-isle-evrima-server-admin-guide-commands-bans-and-moderation","status":"publish","type":"post","link":"https:\/\/xgamingserver.com\/blog\/the-isle-evrima-server-admin-guide-commands-bans-and-moderation\/","title":{"rendered":"The Isle Evrima Server Admin Guide: Commands, Bans, and Moderation"},"content":{"rendered":"\n

Moderating a busy The Isle Evrima server is a different job from setting it up. Once players are pouring in, you need to grant admin powers, broadcast announcements, kick the griefers, ban the cheaters, and adjust the game live without restarting. The trouble is that The Isle’s admin system is poorly documented and full of Legacy-branch myths \u2014 half the “command lists” floating around the web are for the old build and will not work on Evrima. This guide cuts through that. Every key, port, and command below is verified against the current Evrima build (App ID 412680).<\/p>\n\n\n\n

We will cover, in order: how to grant in-game admin powers via Game.ini<\/code>, how to enable and connect to RCON, the full list of RCON commands that actually exist, how kick\/ban\/unban work, the in-game admin abilities, and \u2014 just as importantly \u2014 what does not<\/em> exist so you do not waste hours chasing commands that were never real.<\/p>\n\n\n\n

Setting Admins in The Isle Evrima<\/h2>\n\n\n\n

There is no admin console password and no separate admin file in Evrima. Admins are defined directly in Game.ini<\/code> by their Steam64 ID. On Windows your config lives at TheIsle\\Saved\\Config\\WindowsServer\\Game.ini<\/code>; on Linux it is TheIsle\/Saved\/Config\/LinuxServer\/Game.ini<\/code>.<\/p>\n\n\n\n

The admin list belongs to the [\/Script\/TheIsle.TIGameStateBase]<\/code> section \u2014 this is the access\/roster section, separate from the gameplay section. Add one Steam64 ID per line:<\/p>\n\n\n\n

[\/Script\/TheIsle.TIGameStateBase]\nAdminsSteamIDs=76561198000000001\nAdminsSteamIDs=76561198000000002\n\nWhitelistIDs=76561198000000003\nVIPs=76561198000000004<\/code><\/pre>\n\n\n\n
Each player you add gets in-game admin abilities the next time the server starts. The same section holds WhitelistIDs<\/code> (players allowed in when bServerWhitelist=true<\/code>) and VIPs<\/code> (players who get priority\/queue-bypass). All three use the same one-Steam64-per-line format.<\/p>\n\n\n\n
A Steam64 ID is the long 17-digit number beginning with 7656119...<\/code>. Players can find theirs through any Steam ID lookup site or from their profile URL. After editing, you must restart the server<\/strong> \u2014 Evrima reads admin and roster keys only at boot. If a single header or key is misspelled, the server silently reverts that value to default and your admins will not be granted, so copy the section header exactly as shown.<\/p>\n\n\n\n
Enabling RCON on The Isle Evrima<\/h2>\n\n\n\n
RCON (Remote Console) is how you run admin commands without being in-game \u2014 broadcasting messages, kicking, banning, saving, and adjusting AI on the fly. RCON in Evrima is configured in the [\/Script\/TheIsle.TIGameSession]<\/code> section of Game.ini<\/code> (the gameplay\/identity section). This is the authoritative location for the current build. Some older third-party templates placed these keys under [\/Script\/Engine.Game]<\/code> \u2014 ignore those for Evrima.<\/p>\n\n\n\n
[\/Script\/TheIsle.TIGameSession]\nbRconEnabled=true\nRconPassword=\"use-a-long-random-string-here\"\nRconPort=8888<\/code><\/pre>\n\n\n\n
RCON listens on TCP port 8888<\/strong> by default. You must open\/forward that port in your firewall and router, and you should restrict access to trusted IP addresses \u2014 anyone who reaches the RCON port with the password has full control of your server.<\/p>\n\n\n\n
There is one critical gotcha that trips up almost every new host: standard Source-style RCON clients and mcrcon<\/code> do not work with Evrima.<\/strong> The Isle uses its own RCON protocol. You must use an Evrima-compatible RCON client \u2014 a community tool or Discord bot that speaks The Isle’s protocol. If you connect with a generic RCON tool and get silence or garbage, that is the reason, not a config error.<\/p>\n\n\n\n
RCON, Queue and game ports at a glance<\/h3>\n\n\n\n
Purpose<\/th>Default Port<\/th>Protocol<\/th><\/tr><\/thead>
Game \/ query port<\/td>7777<\/td>UDP<\/td><\/tr>
RCON<\/td>8888<\/td>TCP<\/td><\/tr>
Queue<\/td>10000<\/td>TCP<\/td><\/tr><\/tbody><\/table>
Evrima reuses the game port for queries on 7777\/UDP; forward the 7777\u20137779 UDP range to be safe. Legacy-era Steam ports (27015\u201327017) do not apply to Evrima.<\/figcaption><\/figure>\n\n\n\n
If you run multiple servers on one machine, increment each port in a clean block: Port 7777 \u2192 7787, RconPort 8888 \u2192 8889, QueuePort 10000 \u2192 10001, and forward each. For the full install and first-launch process, see our companion walkthrough on how to set up a The Isle Evrima dedicated server<\/a>.<\/p>\n\n\n\n
The Real RCON Command List<\/h2>\n\n\n\n
These are the RCON commands confirmed to exist in Evrima across multiple host references. The arguments are comma-delimited, but the exact order and spacing can vary slightly depending on which RCON client or bot you use \u2014 so treat the syntax below as a guide and always check your specific tool’s documentation for the precise format.<\/p>\n\n\n\n
Command<\/th>What it does<\/th><\/tr><\/thead>
announce <\/code><\/td>Server-wide broadcast to all players<\/td><\/tr>
playerlist<\/code><\/td>List all connected players<\/td><\/tr>
getplayerdata <\/code><\/td>Retrieve info on a specific player<\/td><\/tr>
kick <\/code><\/td>Kick a player by Steam64 ID<\/td><\/tr>
ban <\/code><\/td>Ban a player by Steam64 ID<\/td><\/tr>
directmessage <\/code><\/td>Send a private message to one player<\/td><\/tr>
save<\/code><\/td>Force a save of all game data<\/td><\/tr>
togglewhitelist<\/code><\/td>Turn whitelist mode on or off<\/td><\/tr>
addwhitelist <\/code><\/td>Add a player to the whitelist<\/td><\/tr>
removewhitelist <\/code><\/td>Remove a player from the whitelist<\/td><\/tr>
getplayables<\/code><\/td>Show the current playable dino roster<\/td><\/tr>
updateplayables <\/code><\/td>Update the playable species list live<\/td><\/tr>
toggleai<\/code><\/td>Toggle AI creature spawning<\/td><\/tr>
disableaiclasses <\/code><\/td>Disable specific AI classes<\/td><\/tr>
aidensity <\/code><\/td>Set AI spawn density live<\/td><\/tr>
setgrowthmultiplier <\/code><\/td>Change the growth multiplier live<\/td><\/tr>
wipecorpses<\/code><\/td>Remove all corpses on the map<\/td><\/tr>
getqueuestatus<\/code><\/td>Report the current server queue status<\/td><\/tr>
pause<\/code><\/td>Toggle server pause<\/td><\/tr><\/tbody><\/table>
Verified Evrima RCON commands. Argument order may differ per client.<\/figcaption><\/figure>\n\n\n\n
The standout commands for live moderation are announce<\/code> (warn the whole server before you wipe corpses or restart), playerlist<\/code> (grab Steam64 IDs of who is online before you kick), and save<\/code> (run it before any risky change so a crash never costs progress). The live tuning trio \u2014 aidensity<\/code>, setgrowthmultiplier<\/code>, and toggleai<\/code> \u2014 let you respond to performance problems or community votes without a restart. If you want to make a growth change permanent, set it in Game.ini<\/code> instead; our guide on adjusting growth speed on a The Isle Evrima server<\/a> walks through the GrowthMultiplier<\/code> key in detail.<\/p>\n\n\n\n
Kick, Ban, and Unban Workflow<\/h2>\n\n\n\n
Moderation in Evrima is identity-based: everything keys off the Steam64 ID, not the in-game name (which players can change). The reliable workflow is:<\/p>\n\n\n\n
  1. Run playerlist<\/code> to see who is connected and capture the offender’s Steam64 ID.<\/li>
  2. For a temporary removal, use kick <\/code> \u2014 the player can rejoin immediately, so this is for warnings and disconnecting AFK or disruptive players.<\/li>
  3. For a permanent or timed removal, use ban <\/code>. The Time<\/code> argument controls the ban length; consult your RCON client’s docs for the exact unit and format, as this varies by tool.<\/li><\/ol>\n\n\n\n
    There is no dedicated, universally documented unban<\/code> RCON command across all clients in the verified command set. In practice, unbanning is handled either through your RCON tool’s own ban-management interface or by editing the server’s ban list and restarting. If you are running a community panel or bot, look for its ban list view \u2014 that is almost always the safest way to remove a ban. Because exact unban behavior is client-dependent, do not assume a one-line console command exists for it; check the documentation for whatever RCON tool you have chosen.<\/p>\n\n\n\n
    Whitelist as a moderation tool<\/h3>\n\n\n\n
    For private or heavily-moderated communities, the whitelist is your strongest lever. Set bServerWhitelist=true<\/code> in the [\/Script\/TheIsle.TIGameStateBase]<\/code> section and populate WhitelistIDs<\/code>, or manage it live with togglewhitelist<\/code>, addwhitelist <\/code>, and removewhitelist <\/code>. With the whitelist on, anyone not on the list is refused entry \u2014 effectively a pre-emptive ban for the entire internet except your approved players.<\/p>\n\n\n\n
    In-Game Admin Abilities<\/h2>\n\n\n\n
    Players added to AdminsSteamIDs<\/code> gain in-game admin abilities when they connect \u2014 this is separate from RCON. RCON is your out-of-game remote control surface; the in-game admin role is what lets a trusted moderator handle situations while actually playing or spectating on the server. The two together form the complete moderation toolkit: AdminsSteamIDs<\/code> for in-game powers, RCON for everything from a console, bot, or panel.<\/p>\n\n\n\n
    If you want to lean on a managed control panel rather than wiring up RCON tooling yourself, our The Isle documentation<\/a> covers panel-based admin management, and you can skip the bot setup entirely by running on a managed Evrima hosting plan<\/a> where RCON and admin config are exposed through a clean interface.<\/p>\n\n\n\n
    What Does NOT Exist (Avoid These Myths)<\/h2>\n\n\n\n
    The most valuable part of any Evrima admin guide is knowing what to ignore. These are the dead ends that waste the most time:<\/p>\n\n\n\n