yfricke/experimental-satisfactory-server repository overview

⁠Dockerized experimental Satisfactory dedicated server

⁠About this repository

This repository contains everything to start an experimental dockerized dedicated Satisfactory server.

⁠Early access version

See this repository for the stable (early access) version: YannickFricke/Satisfactory-DS-Docker⁠

⁠Differences to other docker images

Some images on Docker hub are storing the server files in volumes or on the host filesystem. This is not a best practice in the Docker ecosystem as described here⁠.

Volumes should ONLY be used for user specific configuration / files. The server files are not a part of it and should not be stored in volumes or on the host.

Imagine Coffee Stain Studios breaks the dedicated server software and you wanna play with your friends. Other images would download and store the new server files in the volume. Now every time you start a new container it would read the broken server files and then crash.

It wouldn't even help to completely remove the local image due to that these kind of images are using Shell scripts to download and update the server files dynamically.

With this image this can't happen due to that the server files are stored as immutable data inside the container. Coffee Stain Studios broke the build? No problem! Just use the previous build id to run the old image and play with your friends!

⁠Do I really need a dedicated server now?

Definetly not! Satisfactory still has the "old" multiplayer mode (through sessions and invites) which is probably less buggy than the dedicated servers.

⁠When do I need a dedicated server?

There are only three reasons why you need a dedicated server:

• You want to play with your friends and all of you have a bad internet connection
• Your computer can't handle a second player (due to old computer components)
• You wanna play in a local network where you don't have internet access

⁠Requirements

• Docker⁠
• docker-compose⁠ (if you don't wanna use the Docker CLI directly)

The minimum hardware requirements for running the dedicated server which are listed here⁠.

⁠How to setup

Download the repository to your computer or server and run the following command:

• docker-compose up

⁠Further ingame setup

Take a look at the awesome video of Jace (one of the Community Managers @ Coffee Stain Studios) how you set up the server ingame here⁠.

⁠Loading a savegame

The folks at Satisfactory wiki have a pretty neat guide on how you can upload the savegame to your server here⁠.

Everything that you need to know regarding this Docker setup is, that you need to place the file in the shared/SaveGames directory. docker-compose will then mount the directory to the required location inside the container.

As far as I know there will be the possibility that you can upload your savegame directly to the server once it is implemented. Then you won't need the linked guide anymore.

⁠Known problems

• The dedicated server crashes when you use the Rebar gun. It has already been reported here⁠.
• The dedicated server crashes when you try to mass dismantle buildings. It has already been reported here⁠.

Checkout the Satisfactory Q&A platform for the most recent information regarding server crashes and co here⁠.

⁠How do I report bugs?

If you found a bug in the server / ingame you can report the bug directly to Coffee Stain Studios here⁠.

When it comes to the Docker support you can use the issue tracker⁠ of this repository.

⁠License

This repository is licensed under the MIT license. You can find the exact license in the LICENSE file.