Web Analytics Made Easy - Statcounter
Server Tools

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





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


    

  
Frequently asked questions

  
Why does my RCON tool not work with The Isle?

  
Because The Isle (Evrima) does not speak Source RCON. Generic RCON clients, web RCON panels and A2S query sites all assume the Source protocol, and The Isle uses its own: a login frame of 0x01 followed by the password and a null byte, then commands as 0x02, a one-byte opcode, an optional payload and a null byte. A2S is not answered either, verified against a live server, which is why server-query sites show an Isle server as offline even while people are playing on it.

  
What are The Isle RCON opcodes?

  
Player list is 0x40, server details 0x12, per-player data 0x77, announce 0x10, ban 0x20, kick 0x30 and save 0x50. Commands that take an argument carry it as the payload between the opcode and the trailing null byte; kick and ban take a Steam ID rather than an in-game name.

  
How do I read The Isle player list reply?

  
The reply 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, which is the mistake most parsers make and the reason names end up attached to the wrong player.

  
Does this tool connect to my server?

  
No. It builds the bytes and a runnable snippet in your browser and never opens a connection. A page that accepted your RCON password and connected on your behalf would be asking you to hand an admin credential to a website, and your RCON password is the credential that can kick, ban, save and wipe.



    
    

      This tool: v1.5 · updated 18 Sep 2026