-
-
Notifications
You must be signed in to change notification settings - Fork 834
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Satisfactory changed startup parameter on 0.5.0.6 patch #3661
Comments
I will fix this tomorrow. |
Thanks. This will need to be addressed soon. Hopfully they dont need to make too many more changes like this |
I have the feeling that we'll see even more changes like this due to the experimental nature of the servers current state. I will try to convince Bogdan to tell us changes like these beforehand so we could bring up fixes like these closer to the release time. |
i have work on this so you can also set the ip if ya want to but need to figure out how to code it in now
|
CSS fixed the Linux Server crash issue. Don't know if Guess we still could benefit from the PR - just for documentation that the issue was addressed internally at CSS. |
CSS added a Parameter today with the release of Update 5 to the Early Access branch. If you are or want to still playing the Experimental Branch, the server needs to be started with |
this is probably only a flag for steamcmd, as this is in the wiki, not for the server itself: Edit: the branch can be changed all the time with the following howto: |
Yeah, should have mentioned it. Maybe make a check if the user wants to install the Early Access Branch or Experimental Branch during installation? Like |
You can set your branch in the config file. No additional parameters needed. |
oh I see. Thanks! |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
User Story
As a server admin, I want to request a change to the
sfserver
startup command so that it works in an automated way after introducing-multihome
parameter as a requirement in patch 0.5.0.6.Basic info
Further Information
With 0.5.0.6 update tonight CSS introduced
-multihome
as a server parameter (see wiki entry: https://satisfactory.fandom.com/wiki/Dedicated_servers). I think to address demands to have multiple instances running on the same machine but with different ips. Somehow the server crashes if the parameter is not set and the default settings 0.0.0.0 will apply. Curiousily this only applies to Linux servers. Windows server are not being affected by this. This could make this request obsolete with 0.5.0.7 however. On the other hand it could be beneficial to have this automated workaround to be sure.I've changed common.cfg to these settings and it works now automatically without specifying the IP:
To Reproduce
Steps to reproduce the behaviour:
./sfserver details
Expected behaviour
The server will work without any issues again.
The text was updated successfully, but these errors were encountered: