Web Analytics Made Easy - Statcounter

Tools / The Isle

The Isle RCON Command Builder

The Isle does not speak Source RCON, which is why every generic RCON client and web panel fails against it. Pick a command and get the exact bytes, plus a snippet you can actually run. Built in your browser; this page never connects to your server.

Command bytes (hex)


  

Escaped, for a string literal


  

Login frame you must send first


  

Runnable snippet


  
Your RCON password never goes in this page, and should never go into any page. The snippet leaves it as a placeholder for you to fill in locally. That password can kick, ban, save and wipe, so treat a site that offers to "connect for you" the way you would treat one asking for your Steam login.

The protocol, in four lines

The Isle uses its own TCP protocol rather than Source RCON:

These opcodes come from the client we run against real Evrima servers in production, not from a forum thread. That matters here more than usual: the community documentation for this protocol disagrees with itself, and a wrong opcode silently does nothing or does something else.

The player-list reply trips almost everyone

The reply to 0x40 is a PlayerList header followed by comma-separated values whose first half is Steam IDs and second half the matching names, in the same order. They are not interleaved id,name pairs. Parse it as pairs and every name attaches to the wrong player, which looks like a server problem and is not.

If you would rather not hand-roll a socket

On a managed The Isle server the player list, growth and health readouts are already in the panel, RCON is firewalled rather than merely password-protected, and the EOS launch arguments are set correctly, which is the other thing that stops an Evrima server dead.

Diagnose a Game.ini or TheIsle.log → · Build a clean Game.ini →

Opcodes from our production client Never connects - builds bytes only Your RCON password stays a placeholder

This tool: v1.3 · updated 29 Aug 2026