Web Analytics Made Easy - Statcounter
Server Tools

Tools / The Isle

The Isle Server Doctor

Paste your Evrima Game.ini, your TheIsle.log, or both. This checks the failures that actually happen on Isle servers, including the ones that leave the server running and looking fine. Everything stays in your browser.

Findings

What this checks, and why each one bites

Keys under the wrong section header. Admin IDs, whitelist and AllowedClasses belong to TIGameStateBase; everything else belongs to TIGameSession. A key under the wrong header is ignored in silence, so the server runs on defaults and the log says nothing. This is the single most common reason a setting "does nothing".

Comma-joined class lists. AllowedClasses and DisallowedAIClasses repeat once per entry. Joined onto one line they parse as a single invalid class, and the server starts perfectly with nothing anybody can spawn as.

A password that is not switched on. ServerPassword holds the value and bServerPassword switches it on. Set one without the other and your private server is either open to everyone or joinable by nobody.

RCON reusing the join password. Every player who connects knows the join password. Reuse it and each of them can kick, ban, save and wipe. The log check also flags RCON bound to 0.0.0.0 and any unauthenticated connection attempts, which is someone probing the port.

Whitelist lockout. bServerWhitelist=true with an empty WhitelistIDs locks out everyone including you.

EOS failures. On Evrima the Epic Online Services credentials are launch arguments, not config. If the log shows an EOS initialisation failure, nothing you change in Game.ini will help, and the Doctor says so rather than sending you round the config again.

Load that will not fit the plan. AI density is one of the largest CPU costs on an Evrima server, and high slots with high density compound. Growth above 20 is documented as breaking growth outright rather than speeding it up.

If you would rather not maintain this file at all

Every fault above is something you find by editing a config, restarting, and watching what happens. On a managed The Isle server the config is generated from the settings you pick, the EOS launch arguments are already correct, RCON is firewalled rather than merely password-protected, and a backup is taken before every game update, so patch day is a check rather than a scramble.

Build a clean Game.ini instead → · EOS startup failures · Server not showing up · AI density and slots

Want this on a real server? Supercraft hosts The Isle →

Frequently asked questions

Why does my The Isle server ignore settings I changed?

Almost always the section header. Admin IDs, whitelist and AllowedClasses belong under [/Script/TheIsle.TIGameStateBase], while server name, slots, passwords, RCON and every world multiplier belong under [/Script/TheIsle.TIGameSession]. A key under the wrong header is silently ignored and the server runs on defaults, with nothing in the log to say so.

Why can nobody spawn on my Isle server?

AllowedClasses was almost certainly written as a single comma-separated line. Evrima reads one class per line, so a joined list parses as one invalid class and the server ends up with no playables at all. The server still starts, which is what makes it confusing.

My Isle server will not start and the log mentions EOS. What is wrong?

The Epic Online Services credentials are launch arguments on Evrima, not Game.ini settings. If they are missing or wrong the server exits at boot with an EOS initialisation failure, and no change to Game.ini will fix it. Check the launch command line.

Is it safe to use the same password for RCON and joining?

No. Every player who connects knows the join password, so reusing it as RconPassword gives all of them kick, ban, save and wipe. Use a different password, and firewall the RCON port rather than relying on the password alone.

This tool: v1.6 · updated 18 Sep 2026