To install a server-side Empyrion mod, stop the dedicated server, place the mod’s DLL and support files in its own folder under Content/mods, restart the server, and confirm the load in the newest dedicated-server log. You can do this on a machine you administer directly or through a host’s file browser or FTP service. The important distinction is that Game API mods are not installed like Steam Workshop scenarios: they are files on the server, and each mod must have the directory structure and dependencies specified by its author.
What kind of Empyrion mod are you installing?
The procedure in this guide applies to Game API server mods, normally distributed as a DLL with optional configuration or dependency files. These mods are loaded by the dedicated server at startup from its Content/mods directory. A Workshop scenario or scenario asset follows a different distribution model and does not replace the DLL installation described here.
Before downloading anything, read the mod’s release notes. Confirm that the release is for the Empyrion dedicated server/Game API rather than only the client, note the game build it supports, list every dependency, and check whether the author requires a particular folder name or a compilation step. A ZIP that contains only client-side Workshop content will not become a server mod simply by copying it into the server directory.
What do I need before installing a mod?
You need a working Empyrion dedicated-server installation, permission to stop and start that server, and file access to its root directory. The server software is available without owning the client game.
- Dedicated-server software: Install Empyrion – Galactic Survival Dedicated Server from Steam Library > Tools, or install it with SteamCMD.
- Administrative access: You must be able to stop the process before changing files and restart it afterward.
- Mod package: Obtain the Game API release and all files named in its release notes. Keep the original archive until you have confirmed the server loads correctly.
- File access: For self-hosting, use the Windows filesystem. For a managed host, use its file browser or FTP credentials.
- A way to inspect logs: You will verify the installation in the newest folder under
Logs.
The Empyrion Admin Helper (EAH) ships with the official dedicated-server installation. It can configure, start, stop, and maintain a local server, so you can use it instead of manually controlling every process if your setup includes EAH.
How do I install the Empyrion dedicated server?
Steam’s Tools library is the simplest route for a Windows server. SteamCMD is useful when you want a scripted or unattended installation.
Install through Steam
- Open Steam and select Library.
- Change the library filter to Tools.
- Find Empyrion – Galactic Survival Dedicated Server and install it.
- Record the installation directory; this is the server root used in the mod paths below.
The official dedicated-server guide from Eleon was posted September 9, 2024 and updated November 2, 2024. Use that guide for the initial network and server setup, including firewall and port configuration.
Install with SteamCMD
Run SteamCMD with an installation directory of your choice. Replace the path in the command with the directory where you want the server files stored:
steamcmd +force_install_dir <Install Directory> +login anonymous +app_update 530870 validate +quitThe 530870 application ID installs the Empyrion dedicated server. The validate option checks the downloaded files, which is useful if a previous update was interrupted or files are missing.
How do I install a Game API mod on a self-hosted server?
Use one folder per mod and put the DLL directly in that folder. The complete target pattern is <server root>/Content/mods/<mod folder>/.
1. Read the release notes
Identify the supported Empyrion build, required dependencies, configuration files, and any mandated directory name. Some releases require you to compile a project or place additional files beside the DLL. If the author specifies a name, follow it instead of choosing your own.
2. Stop the server completely
Use EAH, the server’s control script, or the console process to stop the instance. Wait until the process has exited before editing files. Changing a DLL while the server is reading it can leave an incomplete or locked installation, and hosted-server procedures explicitly require the instance to be stopped before an upload.
3. Open or create the mods directory
Open the server root and browse to Content. If there is no mods directory, create it with that name. The documented path is:
<path to your server-root>/Content/modsKeep the spelling and location literal. Do not place the mod beside the server executable or under a client installation’s Workshop directory.
4. Create a separate folder for the mod
Inside Content/mods, create one directory for each mod. A descriptive name containing the mod name and version is practical unless the release notes demand a specific name. Separate directories prevent one mod’s files from being mistaken for another’s during updates and make log entries easier to interpret.
5. Extract the archive at the correct level
Extract the supplied DLL and every required support file directly into the mod’s directory. For example:
<server root>/Content/mods/SpotGuard/SpotGuard.dllA common mistake is an extra directory created by the ZIP itself, such as Content/mods/SpotGuard/SpotGuard/SpotGuard.dll. Open the extracted folders and move the files up one level when necessary so the mod folder itself contains the DLL. Preserve any configuration file names and subfolders required by the author.
6. Restart the server
Start the dedicated server again through EAH or the same script you normally use. Game API mods are applied during server startup; changing files without a restart does not load a new DLL.
7. Verify the startup log
After startup, open the newest numbered directory under Logs, then open the latest Dedicated_*.log file. Search for a line similar to:
Loaded mod Mod5 from SpotGuardThe exact mod name varies, but a Loaded mod entry confirms that the server found and initialized the package far enough to register it. Save the log when asking the mod author for help; the startup context is more useful than a screenshot of the folder alone.
How do I install a mod on a hosted Empyrion server?
On a managed service, the files still belong under empyrion/Content/Mods; only the way you reach that path changes. Nitrado documents both a web file browser and FTP workflow.
Using the host’s file browser
- Stop the server from the host control panel and wait for the status to show that it is offline.
- Open the provider’s file browser.
- Follow
empyrion>Content>Mods. Create the directory if the panel does not show it. - Upload the already extracted mod folder, keeping each mod in its own directory.
- Save or apply the file operation if the panel requires a separate confirmation.
- Start the server and wait for the instance to finish booting.
- Use the panel’s log viewer, or download the newest log, and search for
Loaded mod.
Using FTP
Connect with the FTP credentials supplied by the host using an FTP client such as FileZilla. Navigate to empyrion/Content/Mods, then drag the extracted mod folder into that directory. Check the transfer queue for failed or partial files before closing the client, and restart the server from the control panel after the upload completes.
Do not upload the ZIP as a single file and expect the server to unpack it. The server needs the DLL and its support files in the folder hierarchy, so extract locally first and transfer the resulting directory.
Why is my Empyrion server mod not loading?
Most failures are path, packaging, compatibility, or restart problems. Work through the symptom that matches your log and directory.
| Symptom | Likely cause | Fix |
|---|---|---|
No Loaded mod line |
The DLL is outside Content/mods, the directory is misspelled, or the server was not restarted. |
Stop the instance, verify <server root>/Content/mods/<mod folder>/<mod>.dll, then start it again. |
| The log shows a folder but not the DLL | The archive created an extra nested directory. | Move the DLL and support files up so they sit directly in the mod’s own folder. |
| The server reports a dependency or configuration error | A required library, configuration file, or supported build is missing. | Re-read the release notes, install every named dependency, and use the configuration format required by that release. |
| The upload appears complete but the host does not load it | The files went to the wrong instance or an FTP transfer failed. | Confirm the path is the active instance’s empyrion/Content/Mods, inspect the transfer queue, and restart from the host panel. |
| A mod worked before an update and now fails | The new release changed configuration tags or no longer matches the game build. | Compare the changelog with your existing configuration and merge new tags instead of blindly replacing local settings. |
When troubleshooting, check the newest log rather than an older run. The numbered directories under Logs let you distinguish a fresh startup from stale evidence. A line reporting an error while executing a Game_Event means the mod loaded far enough to run code, but encountered a runtime problem; investigate the event, dependency, or configuration details in the same log and then consult the release notes.
How do I keep server configuration safe during updates?
Do not edit the stock dedicated.yaml in place if you expect to update the server. The official guidance is to copy it, make changes in the copy, and launch the server with that custom file.
- Copy
dedicated.yamlto a separate file with a clear name, such asmy-server.yaml. - Copy the boot script you use:
EmpyrionDedicated.cmdorEmpyrionDedicated_NoGraphics.cmd. - Edit the copied script and append
-dedicated <custom-file>.yamlto its launch command. - Start the server with the copied script and confirm that it uses the custom configuration.
This arrangement keeps your settings separate from stock files that a server update may replace. It also makes the launch configuration explicit when you move the instance or diagnose a startup problem.
How do I update or remove a server mod?
Updating uses the same directory structure as the initial installation. Stop the server, keep a copy of the current configuration, replace the old release files with the new ones, and restart.
- Read the new release notes and changelog before touching the files.
- Stop the server and wait for the process or hosted instance to finish shutting down.
- Remove or replace the old DLL and support files in that mod’s folder. Do not mix files from unrelated versions unless the author instructs you to do so.
- Merge configuration changes described by the new release. Configuration files can gain new tags, so replacing your existing file wholesale may discard local settings.
- Start the server and inspect the newest
Dedicated_*.logfor a successful load or a specific error.
To remove a mod, stop the server, delete only that mod’s directory from Content/mods, restart, and confirm that its load entry is no longer present in the new startup log. Leave other mod folders untouched.
What is the difference between Game API mods, Workshop scenarios, and SharedData?
Game API mods are DLL-based server extensions installed under Content/mods. The Game API overview states that these mods do not have Steam Workshop integration; authors distribute them as downloadable files or through community posts.
Steam Workshop scenarios and scenario assets are separate content. The official guide describes SharedData as custom files that clients download on first connection or when the host changes them. It also documents an optional cloud-storage URL for SharedData. Those mechanisms can distribute scenario files, but they do not install a Game API DLL and cannot substitute for the Content/mods folder.
Should I self-host or use managed hosting for modded Empyrion?
Both approaches load the same mod files. The practical difference is who controls the filesystem, updates, networking, and diagnostic access.
| Area | Self-hosted server | Managed host |
|---|---|---|
| File access | Direct access to the Windows server filesystem. | Provider file browser or FTP, usually under empyrion/Content/Mods. |
| Game updates | You manage Steam or SteamCMD updates and choose when to apply them. | The provider manages the underlying infrastructure; you control mod uploads through its panel. |
| Configuration | You can copy YAML files and boot scripts and launch with a custom file. | Configuration controls depend on the provider’s panel and file access. |
| Networking | You manage firewall rules, ports, and any router forwarding. | The host supplies the network endpoint and its own control-panel settings. |
| Troubleshooting | Full process, filesystem, and log access. | Panel logs and file access, with provider support for infrastructure issues. |
Choose self-hosting when you need direct control over scripts, files, and update timing. A managed instance is simpler when you do not want to administer Windows networking or maintain the machine, but you must learn the provider’s restart and file-transfer workflow.
What security precautions matter during setup?
Use the official server guide’s network instructions and limit administrative access to people who need it. In particular, do not expose or forward the Telnet port while configuring remote administration; the official guide warns that Telnet is insecure. Prefer the host panel, local administration, or a protected management network instead of opening an unencrypted control channel to the internet.
For self-hosting, apply firewall and router changes deliberately and document which ports are open. For managed hosting, protect the control-panel and FTP credentials because anyone who obtains them can upload files, alter configuration, or stop the instance.
Installation checklist
- The dedicated server is installed from Steam Tools or SteamCMD.
- The mod release is explicitly for the Empyrion Game API/server and matches the supported game build.
- Every dependency and required configuration file is present.
- The server was stopped before files were changed.
- The path is
<server root>/Content/mods/<mod folder>/, with one folder per mod. - The DLL is not hidden behind an accidental extra ZIP directory.
- The instance was restarted after installation or updating.
- The newest numbered log contains the expected
Loaded modentry, or a specific error to investigate.
Frequently Asked Questions
Why are Empyrion log folders numbered?
The server stores separate startup runs in numbered directories under Logs. Open the directory with the highest number after each restart so you do not mistake an old successful load for the current result.
What does an “Error on executing Game_Event” line mean?
That message indicates the server loaded the mod far enough to execute one of its event handlers, then encountered a runtime failure. Check the surrounding lines for the event name and missing dependency or configuration detail before contacting the mod author.
Can I install two versions of the same mod for testing?
The documented layout gives each mod its own directory, but running duplicate versions can create conflicts or ambiguous behavior. Test one release at a time by stopping the server and replacing the files in the mod’s existing folder.
Does the dedicated server need the client game installed on the same machine?
No. EAH documentation states that the dedicated-server software is available from Steam’s Tools library and does not require owning the client game. Players still connect with their normal Empyrion client installation.