Talk:Dedicated servers

Proposed new section: Connecting To a Server

Suggested place in sequence

Between Port Forwarding and Console Commands.

Topics to Cover

• Connecting from the same host the server is running on
• Connecting from another host on the same LAN
• Connecting from a host not on the same LAN (e. g. via the Internet)

Purpose

Addresses the confusion from people attempting to connect via Session IDs and the like, gives examples of why connecting to e. g. 127.0.0.1; 192.168.75.143; and myserver.example.com may or may not work in given contexts and situations.

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. — Preceding unsigned comment added by 93.255.17.146 (talk • contribs) at 05:41, 4 November 2021‎ (UTC). Please sign your posts with ~~~~

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 <ip address>, where <ip address> is the ip address of your home system (ex: sh FactoryServer.sh -multihomme=192.168.0.5 ) — Preceding unsigned comment added by 24.243.82.15 (talk • contribs) at 17:13, 4 November 2021‎ (UTC). Please sign your posts with ~~~~

Completed Changes

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

— Preceding unsigned comment added by DopeGhoti (talk • contribs) at 19:00, 31 October 2021 (UTC). Please sign your posts with ~~~~

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. — Preceding unsigned comment added by PhonicUK (talk • contribs) at 13:48, 1 November 2021‎. Please sign your posts with ~~~~

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. — Preceding unsigned comment added by Itzhayleyuk (talk • contribs) at 23:03, 1 November 2021‎ (UTC). Please sign your posts with ~~~~

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 CubGeek (talk)00:31, 2 November 2021 (UTC)}}

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. — Preceding unsigned comment added by DopeGhoti (talk • contribs) at 01:11, 2 November 2021 (UTC). Please sign your posts with ~~~~‎

The system requirements should also be a nicely formatted table. — Preceding unsigned comment added by PhonicUK (talk • contribs) at 09:27, 2 November 2021‎ (UTC). Please sign your posts with ~~~~

Potential new system reqs table:

System Requirements

Processor	Recent x86/64 (AMD/Intel) processor. No 32 bit or ARM support. The server favours higher single-core performance over multiple cores.
Memory	6GB minimum, 8GB RAM is recommended for larger saves or to host more than 4 players.
Storage	10GB for the game server itself
Operating System	Any currently supported version of Windows or major Linux distribution. Out-of-support OSs such as Windows 7 are explicitly not supported.
Internet Connection	Broadband internet connection. Hosting from home will require the ability to configure port forwarding.

— Preceding unsigned comment added by PhonicUK (talk • contribs) at 09:48, 2 November 2021‎ (UTC). Please sign your posts with ~~~~

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

Autosave interval

rolled into the ini configuration updates. Cubgeek (talk) 17:05, 10 November 2021 (UTC)

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

separate page created Dedicated servers/Configuration files, main Dedicated servers page updated Cubgeek (talk) 17:05, 10 November 2021 (UTC)

?listen argument

Per Bogdan, that argument should not be necessary to set the game port; just using -Port should suffice. I'm removing references to it from the main article but making a note here in case a version ends up being necessary.

See: https://discord.com/channels/370472939054956546/902621736602861588/908421372483608637

DopeGhoti (talk) 18:34, 11 November 2021 (UTC)

Beta updates

From the steamCMD ( https://developer.valvesoftware.com/wiki/SteamCMD#Automating_SteamCMD ) Note: When using the -beta option on the command line, it must be quoted in a special way, such as +app_update "90 -beta beta". Note: If this does not work, try putting it like "+app_update 90 -beta beta" instead.

Would imply that for experimental branch on the server you would need:

steamcmd +force_install_dir ~/SatisfactoryDedicatedServer +login anonymous +app_update "1690800 -beta experimental" validate +quit

or

steamcmd +force_install_dir ~/SatisfactoryDedicatedServer +login anonymous "+app_update 1690800 -beta experimental" validate +quit

I have not tested these commands

Feedback to above

Everything in the foregoing section is demonstrably incorrect. If a an available beta as two words in it, its name must be quoted (e. g. `-beta "Super Special Edition"`) but the suggestion of quoting the app ID and the `-beta branchname` arguments is wholly wrong. DopeGhoti (talk) 06:23, 27 November 2021 (UTC)