a6963bbb41
- Adds the newly discovered `-multihome` flag to fix 0.5.0.6 update's IPv6 related issue, where the IP binds to IPv6 by default, causing a crash on boot. Server will now bind to IPv4 by default. As this is a hotfix, IPv6's possible support will be investigated at a later date. - Adds the newly discovered `?listen` flag to the `-Port` flag to explicitly declare the port. This will prevent the server from possibly auto-incrementing the port if, for whatever reason, it thinks there's another Satisfactory server present in the same container. |
||
|---|---|---|
| .. | ||
| egg-satisfactory.json | ||
| README.md | ||
Satisfactory
Server version currently marked as experimental by the Satisfactory developers! Egg loads fine, but your mileage may vary in-game.
Authors / Contributors
 Red-Thirten 💻 🔨 |
 Kubi 💻 💡 |
 matthewpi 💻 💡 |
 Software-Noob 💻 💡 |
 Zarklord 💻 💡 |
Game Description
From Coffee Stain's Website:
Satisfactory is a first-person open-world factory building game with a dash of exploration and combat. Play alone or with friends, explore an alien planet, create multi-story factories, and enter conveyor belt heaven!
Egg Capabilities
- Configuration of the Server Query, Beacon, and Game ports.
- Configurable to automatically check for server updates on start via SteamCMD. Forcing validation is also configurable.
- [Experimental] Max player configuration.
- Misc. settings listed below can be configured by an admin client via the game's UI, and are currently not set via the Egg:
- Server Password
- Admin Password
- Auto-Save on Player Disconnect
- Pause When No Players Online
- ...and possibly more as the client's UI is developed further for more configuration options.
Server Ports
- Default server ports are listed below, but all three ports can be changed freely.
- Note: The Primary/Default/Game Port for your server in Pterodactyl will be Satisfactory's
-Port=????game port, even though clients will connect with the Query port. - It is recommended to distance ports of other running Satisfactory servers in Pterodactyl by increments of 100 (it is currently unknown what the minimum increment is, but an increment of +1 caused cross-server talk in testing). Also, your internal ports must match your external ports on your network (ie. you can't have an external port of 7778 forwarded to your 7777 internal port; they must match).
- All three ports are required to be open for normal server behavior!
| Port | Default (UDP) |
|---|---|
| Game (Primary Port in Pterodactyl) | 7777 |
| Beacon | 15000 |
| Server Query | 15777 |
Installation Requirements/Instructions
- No major requirements, other than RAM and Disk space noted below.
- You do not need to own the base game to host this server.
- However, to fully "initialize" your server, a client who owns the game must log into the server to "claim" it and create a new session. The generated session will not be written to disk until the first save occurs.
- Currently, there is no way to save the session on server stop. Therefore, ensure the session is saved or the last player has disconnected (causing an auto-save) before stopping the server.
Minimum RAM Requirement
This server requires a minimum of 4096 MiB of RAM to boot, but the developers recommend 6144 to 8192 MiB of RAM for 4 players or large save files.
Minimum Disk Requirement
This server requires just under 5 GB of disk space to safely run properly. However, save files could easily surpass this amount, so 7-10 GB is recommended.
Save File Location
According to the developer, save files will be able to be uploaded and downloaded by clients via their game client in the future. Until then, below is the save file location in case you would like to upload or download a save file manually:
/home/container/.config/Epic/FactoryGame/Saved/SaveGames/server
Single-player save files can be uploaded here and are playable if desired.
Console Commands
As of v5.0.4, the console tab in the client server manager is the only way to execute commands. Entering commands via Pterodactyl do nothing.
List of known commands can be found via the Wiki
Errors/Warnings
The following errors or warnings you see in the console can safely be ignored:
steamclient.so: cannot open shared object file: No such file or directory
[S_API] SteamAPI_Init(): Loaded '/home/container/.steam/sdk64/steamclient.so' OK. (First tried local 'steamclient.so')
LogSteamShared: Warning: Steam Dedicated Server API failed to initialize.
The local file of 'steamclient.so' was attempted to be loaded, but could not because it is not present, causing the warning message. However, the backup /home/container/.steam/sdk64/steamclient.so is loaded successfully (this is the correct behavior according to the Wiki).
Warning: failed to init SDL thread priority manager: SDL not found
This is a common error with Steam related software on Linux, but can safely be ignored.
...Error: Couldn't find file for package...
...Error: Navmesh bounds are too large!...
...Warning: NiagaraSystem...
LogStreaming: Warning: Failed to read file '../../../FactoryGame/Saved/SaveGames/GameAnalytics.sav' error.
These seem to be common error messages with the current experimental version of the game.