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 →