Talk:Dedicated servers

Page order
I'm thinking sequencing the sections might be wise; they seem kind of scattered right now. I suggest: - Summary - Requirements - Steam/SteamCMD installation - Starting the Server - Initial Setup / Configuration - Port Forwarding / Firewall - Running as a Service - Docker - Automated install / Server manager options - Common errors - History


 * Running as a service should probably be its own page since there are so many options. That section alone accounts for a lot of clutter.


 * I agree with the point by PhonicUK, also it might be worth a mention, that for SystemD configurations to work - at least for me on CentOS - SELinux needs to be disabled.


 * Good idea on breaking things into a more logical sequence, thank you! I would also agree that Running As A Service likely needs to be split off to it’s own page, with sub-sections for the various distros and OS flavors


 * Thanks for the feedback. I've done a first pass on re-ordering the main page and broken out Running as a Service to its own page. ‎


 * The system requirements should also be a nicely formatted table.
 * Potential new system reqs table:


 * I like it. DopeGhoti (talk) 09:49, 2 November 2021 (UTC)

Page protection
> You do not have permission to edit this page, for the following reason:

> This page has been protected to prevent editing or other actions.

Why tough? Were there a edit war? This is gatekeeping and doesn't do any good besides a selected circle of few.


 * So far as I know, only anonymous editing is blocked right now. Create a free account and you can freely contribute. DopeGhoti (talk) 05:47, 4 November 2021 (UTC)


 * Yes there was an edit war and we have only blocked anonymous users, simply make a free account to make edits or suggest the edits here in the talk page and someone will likely add it for you. Also keep in mind this block is not permanent and will expire in a few weeks.
 * Silarious 15:25, 4 November 2021 (UTC)

Multihome option
You might add a some advice:

If you're getting errors about being unable to bind to 0.0.0.0:15777, trying using the -multihome option -multihome, where is the ip address of your home system (ex: sh FactoryServer.sh -multihomme=192.168.0.5 )

Autosave interval
There is another command to set the interval between auto saves: FG.AutoSaveInterval value_in_seconds This could be a potential workaround for users who get kicked when they drive with a vehicle and get kicked when the server is doing an autosave

Cleanup
Absent objection, I'm going to remove the 0.5.0.6 Linux crash section in the troubleshooting section today. It's no longer relevant as there's no point in even trying to run out of date servers. DopeGhoti (talk) 18:28, 6 November 2021 (UTC)

Done and done. DopeGhoti (talk) 04:29, 7 November 2021 (UTC)
 * I wasn't initially sure whether to remove it immediately once 0.5.0.7 was released, as the crash might've persisted. It doesn't seem to happen anymore, so the section indeed isn't relevant anymore. --Ondar111 (talk) 10:20, 7 November 2021 (UTC)

Configuration ( A.K.A. "ini" ) Files
((STILL VERY MUCH WORK IN PROGRESS)) Cubgeek (talk) 14:34, 9 November 2021 (UTC)

Overview:
The Unreal Engine, which is what Satisfactory is built upon, stores many of it's vital settings and configurations in various "ini" (short for "initilization") files. These files are located in a directory relative to the game's base installation folder, as noted below:

Example:
When connected to a server as the administrator via the in-game Server Manager window, on the Server Config tab there are options to "Pause server when empty" and "Autosave when player disconnects." If a server admin leaves the "Pause server when empty" option unselected, but does select the "Autosave when player disconnects" option, those settings are then saved in the ServerSettings.ini file, located in the directory noted above. Opening the ServerSettings.ini file, the following will be listed:

While some settings in the ini files can be edited via the in-game options such as this, there are many, many more settings need to be changed manually by editing the appropriate ini file. Below are some of the settings that the community has discovered:

Crash Reporting

By default, the server uploads crash reports when running on Linux. If you want to disable this behavior, add the following lines to the "Engine.ini" configuration file:

[CrashReportClient] bAgreeToCrashUpload=false