The Isle Dedicated Server: App ID 412680, Branches & the Legacy Trap

The Isle Dedicated Server: App ID 412680, Branches & the Legacy Trap

Two numbers and one branch name decide whether a The Isle server installs at all. Getting them wrong does not produce a helpful error. On Linux it produces an install that looks like it worked and then a server that cannot start, because the files were removed rather than downgraded.

Everything below is read from Steam's own app records for app 412680, checked on 28 August 2026.

The two app IDs are not interchangeable

Both appear in a working setup, which is why they get swapped. Use 412680 for the download; the client ID belongs in the runtime environment, not in the SteamCMD command.

The three branches, and which one is alive

App 412680 publishes exactly three branches. None requires a password:

public is the Steam default. That is the trap: when a branch is not specified, SteamCMD does not give you the current server, it gives you a February 2022 build of a version of the game that no current client can join.

Why -beta public deletes a Linux server

On Windows the default branch installs an obsolete server. On Linux it does something worse, and this is the part that wastes an afternoon.

The Linux depot is 412682. It carries manifests for two branches only:

• evrima: 1.48 GB
• spiro0.11.59.04: 3.51 GB

There is no public manifest for Linux. The branch exists on the app, but the Linux depot has nothing to serve for it. So app_update 412680 -beta public does not download an older server. It resolves to an empty file set and SteamCMD reconciles your install down to match. The install directory collapses to little more than steamapps/, and:

TheIsle/Binaries/Linux/TheIsleServer-Linux-Shipping

is gone. The next start fails with a missing-file error pointing at a binary you watched download successfully an hour earlier. Nothing in the output says "this branch has no Linux build", which is why this reads as a corrupted install or a disk problem rather than a branch mistake.

The correct install

steamcmd +force_install_dir /path/to/server \
         +login anonymous \
         +app_update 412680 -beta evrima validate \
         +quit

Keep -beta evrima on every subsequent update too. An update that omits it silently switches the install back to the default branch and removes the server again.

Check what you actually installed

The app manifest records the branch a directory is currently tracking. Read it rather than trusting the command you meant to run:

grep -E '"betakey"|"buildid"' steamapps/appmanifest_412680.acf

A healthy Evrima install shows "betakey" "evrima" and a build ID matching the table above. If betakey is absent, the directory is on public and the Linux binary will not be there.

Verifying against Steam yourself

Branch build IDs move whenever the developers ship. To read the current state directly rather than trusting any guide, including this one:

steamcmd +login anonymous +app_info_update 1 +app_info_print 412680 +quit

The branches block lists every branch with its build ID and last update time, and the depots block shows which branches have a Linux manifest at all. This is read-only and downloads nothing.

The client has to match

Branch selection is not only a server concern. A player running the default Legacy client will not see an Evrima server in the browser, because they are running a different game. Players opt into evrima in the Steam client's beta properties for The Isle, the same way the server does.

Related guides

• Server not showing up in the browser: the symptom this trap usually produces first
• Full Evrima dedicated server setup: SteamCMD, Game.ini, Engine.ini and EOS start to finish
• Update and version mismatch: keeping the branch pinned across updates
• Server won't start: EOS errors: the failure that happens after the branch is right

If you would rather not manage branches by hand, our The Isle server hosting pins the Evrima branch on every update, so an install cannot fall back to Legacy and delete itself.