Installing mods on The Isle depends on which branch your server runs. Evrima has no supported mod loader or Steam Workshop integration, so its community mods use unofficial UE4SS or PAK/SIG file methods that can stop working after a game update. Legacy uses a different, older configuration-based workflow on some hosting panels. Before touching files, stop the server, back up its save and configuration, verify the mod’s exact server build and dependencies, and install only one mod at a time.
Which version of The Isle does your server run?
Identify the branch before downloading anything. Evrima and Legacy are separate versions with different mod histories, file paths, and server procedures. A Legacy mod or Workshop-style instruction is not automatically compatible with Evrima.
| Branch | Current mod situation | What this guide covers |
|---|---|---|
| Evrima | No supported mod loader and no Steam Workshop integration. Community methods are unofficial and version-sensitive. | UE4SS on Windows, or PAK/SIG files in the server’s Content/Paks tree. |
| Legacy | Older server and mod ecosystem. Some hosting panels document ID-based activation through configuration and a “Modded Server” command-line option. | Panel-specific EnabledMods configuration, clearly labeled as Legacy guidance. |
Do not assume that a server advertised as “modded” is using the same method as another host. Ask the mod author and the host which branch, build, operating system, and installation path are required.
What should I check before installing an Evrima mod?
Prepare a reversible installation and confirm compatibility before uploading files. Evrima modding is unsupported, so a small mismatch can prevent startup or leave clients unable to join.
- Server branch and build: Confirm that the server is Evrima and record its current build. Match the mod author’s stated build exactly.
- Operating system: UE4SS installation in the cited current guide is supported only on a Windows server. A Linux server cannot use that workflow as written.
- Dependencies: Read every required library, framework, load order, and companion mod. A mod can appear in the directory yet fail because a dependency is missing.
- Client requirements: Some mods require files on every player’s game installation. Determine the client path and files before enabling the server copy.
- File access and restart control: You need access to the server’s files and the ability to stop and start it cleanly.
- Backups: Save a copy of the world/save data, configuration files, and the unmodified directories you will change.
Use a separate test server when possible. Install one mod, restart, and verify it before adding another; this is the fastest way to identify the file that caused a failure.
How do I back up and stop an Evrima server safely?
Stop the process first, then copy the save and configuration to a location outside the live server directory. Never overwrite a running server’s files while it is writing data.
- Warn players and issue the host panel’s normal stop command.
- Wait until the panel and console show that the process has exited. If the host exposes a task list, confirm no The Isle server process remains.
- Copy the save/world directory and configuration directory, preserving their folder names and timestamps.
- Record the current server build, launch arguments, installed mods, and any custom ports.
- Only after the backup completes, upload or replace mod files.
If the mod prevents startup, remove the last change and restore the backup rather than deleting unrelated files.
How do I install an Evrima mod with UE4SS?
UE4SS is an unofficial community method. The current installation guidance calls for a Windows server and an experimental UE4SS build, not stable UE4SS v3.0.1. Support can disappear when Evrima or the mod changes.
1. Obtain the correct UE4SS package
Download the experimental build specified by the current mod or hosting instructions. Do not substitute stable v3.0.1 merely because it is easier to find. Confirm whether the package includes a loader, configuration files, and the required runtime components.
2. Stop the server and open its Win64 directory
With the process stopped, locate the server’s executable tree and open:
TheIsle/Binaries/Win64/
Upload the extracted UE4SS files into that directory, keeping the package’s folder structure intact. Uploading the archive itself, or nesting the files inside an extra directory, can leave the loader undiscoverable.
3. Start once to create and inspect the loader log
Start the server without adding the gameplay mod yet. Look for:
TheIsle/Binaries/Win64/ue4ss/UE4SS.log
Some hosts expose an equivalent log location in their file manager or console. A log confirms that the loader was found; it does not prove that a particular mod is compatible.
4. Upload the mod into the UE4SS Mods folder
Stop the server again, then place the extracted mod folder in:
TheIsle/Binaries/Win64/ue4ss/Mods
Follow the author’s required folder name and nesting. Do not rename a package unless its instructions explicitly allow it.
5. Restart and verify one mod
Start the server and watch the console and UE4SS log for load errors, missing dependencies, or version warnings. Join with a compatible client only after the server reaches its normal ready state. If it fails, remove the last mod, compare the server build with the author’s requirement, and ask the author which path and client installation are expected.
How do I install Evrima PAK and SIG mods?
PAK/SIG mods are installed in the server’s Unreal content package tree rather than through a supported Workshop service. Obtain both files from the mod author or community source, and treat every package as build-specific.
1. Confirm the package and client instructions
Check that the download contains the matching .pak and .sig files when both are required. Read whether players must install a client-side copy, a companion mod, or a particular load order. There is no verified central official mod hub for Evrima, so source quality and instructions vary.
2. Stop the server and open Content/Paks
After making a backup, open:
TheIsle/Content/Paks
Do not place PAK files in the UE4SS Mods directory unless the author explicitly combines the two systems.
3. Use the author’s required subfolder
Current community guides commonly reference LogicMods and ~mods beneath the Paks tree, but paths differ by mod. Use the exact subfolder specified by the author; if no path is stated, ask before guessing.
| File type | Typical location | What controls the final choice |
|---|---|---|
| PAK package | Under TheIsle/Content/Paks, often in LogicMods or ~mods |
The mod author’s instructions and server build |
| SIG signature | Usually alongside the matching package in the required Paks subfolder | The author’s package layout; do not separate a required pair |
4. Restart and inspect output
Start the server and watch its console or log for package-load errors. Verify that all required files are present and that server and client versions match. If the server stops loading, remove the most recently added pair and restore the previous working state.
What ports and server settings are relevant to an Evrima dedicated server?
A dedicated-server reference lists practical defaults, but treat them as guide-specific values and verify them against your current build and host panel.
| Setting | Reference value | Protocol | Qualification |
|---|---|---|---|
| SteamCMD application ID | 412680 |
Not applicable | Reference value for the Evrima dedicated server; verify before deployment. |
| Game port | 7777 |
UDP | Guide-specific default. |
| Queue port | 10000 |
TCP | Guide-specific default. |
| RCON port | 8888 |
TCP | Guide-specific default. |
Changing ports does not install a mod, but incorrect firewall or panel values can look like a mod failure because players cannot connect. Confirm that the host exposes the same ports configured in the server launch settings.
How was mod installation handled on The Isle Legacy?
Legacy instructions found in older hosting-panel documentation are branch-specific and should not be copied into an Evrima setup. They describe enabling mod IDs in a configuration file and launching the server in modded mode.
Legacy panel procedure
- Stop the Legacy server and back up its save and configuration.
- Open
TheIsle/Saved/Config/WindowsServer/Gameusersetting.ini. - Add or edit the
[TheIsle.Mods]section. - Enter the required comma-separated mod IDs in
EnabledMods=. - Enable the panel’s Modded Server command-line option.
- Save the configuration and restart the server.
- Watch the console for the server’s mod check or download process, then test with a Legacy client.
The exact panel UI and ID syntax can differ. This is historical Legacy or panel-specific guidance, not evidence that Evrima supports Steam Workshop IDs or automatic downloads.
Why is my modded The Isle server not starting?
Most failures come from a branch mismatch, unsupported loader, wrong path, missing dependency, or a client/server version difference. Diagnose the newest change first.
Server crashes immediately after adding a file
- Stop the server and remove the last mod or PAK/SIG pair.
- Restore the backed-up configuration if launch arguments were changed.
- Check the server log and UE4SS log for the first error, not the final cascade of messages.
- Confirm the mod targets your exact Evrima build or Legacy version.
UE4SS creates no log
- Confirm that the server is Windows-based.
- Verify that you installed the experimental build required by the guide, rather than stable v3.0.1.
- Check that files are directly under
TheIsle/Binaries/Win64/and were not placed in an extra nested folder. - Ask the host whether it redirects logs to another location.
The server starts, but players cannot join
- Determine whether the mod requires client-side files and whether every player installed the same version.
- Check that the package and signature files are in the author’s required Paks subfolder.
- Verify server and client builds, then remove any mod that reports a version mismatch.
- Check game, queue, and RCON port settings and firewall rules separately from the mod files.
A Legacy configuration does nothing on Evrima
Remove the Legacy EnabledMods entries and do not enable a historical “Modded Server” command line on an Evrima server. Choose either the UE4SS workflow or the PAK/SIG workflow specified for your Evrima mod.
How can I update or remove an Evrima mod without losing the server?
Treat updates as a replacement and rollback exercise, not as an in-place overwrite on a live server.
- Stop the server and make a fresh backup of the save, configuration, and currently working mod files.
- Record the old mod version and server build.
- Remove the old mod’s complete folder or matching PAK/SIG files according to the author’s uninstall instructions.
- Install the new version in the same required path.
- Restart and inspect logs before allowing players to return.
- If the update fails, stop the server, restore the previous files, and return to the recorded build.
Install updates one at a time. Updating the game, loader, and several mods together removes the information needed to identify the incompatible change.
Is modding The Isle Evrima officially supported?
No supported mod loader or Steam Workshop integration is documented for Evrima in the current guidance. UE4SS and PAK/SIG methods are community techniques, so an official game update can change file layouts or invalidate a loader without notice.
The developer has historically described a long-term goal of richer modding tools, but that statement is more than four years old according to the Steam page’s warning and should not be treated as a current feature promise. Plan for manual maintenance, keep backups, and be prepared to remove mods after updates.
What is the safest repeatable installation checklist?
- Identify Evrima or Legacy before downloading a mod.
- Confirm the exact server build, operating system, dependencies, and client requirements.
- Stop the server and back up saves, configuration, and working mod files.
- Choose the correct method: experimental UE4SS on Windows, PAK/SIG under
Content/Paks, or Legacy panel configuration. - Install one mod at a time and preserve the supplied folder structure.
- Restart after each change and read the console and relevant logs.
- Test with a matching client before opening the server to everyone.
- Keep a rollback copy for every working combination.
Frequently Asked Questions
Can Linux run UE4SS mods for an Evrima server?
The cited UE4SS guidance supports Evrima modding only on Windows. If your host runs Linux, use a PAK/SIG method only when the mod author explicitly supports it, or move the server to a Windows environment; do not assume a compatibility layer is supported.
Do all players need to install an Evrima mod?
Not necessarily. Some server-side packages require no client file, while others require every player to install matching files. The mod author’s client-install instructions decide this, and a mismatch can prevent joining even when the server starts.
Where can I find official Evrima mods?
There is no verified central official mod hub for Evrima in the current guidance. Obtain files from a source the mod author identifies, verify signatures or paired files when supplied, and avoid packages whose build and installation path are undocumented.
Should I install several mods before restarting the server?
No. Restart after each mod so you can associate a crash, log error, or connection problem with one change. Batch installation makes rollback and diagnosis substantially harder.