Hello,

I'm trying to spin a Valheim PTR server. According to doc, I just need to add "-beta public-test -betapassword yesimadebackups" to the launch. I tried adding it to gameparams but it doesn't seem to work. When I try to connect with my client, it says version missmatch.

 

Thank you

 

edit: I found out why it doesn't work. It's a steam command. Could you update the start-server.sh script so we can add custom Steam CMD from template like the GAMEPARAMS does for the game launcher? would be great for any of the steam game in the end.

 

For now, I replaced the script with modified option, but since it's in a place where files aren't saved between container reload, it's not a permanent solution

Edited December 4, 20223 yr by Nodiaque

@ich777 Apologies if this isn't the place for the question but I was using your docker for a dedicated server in satisfactory and came across an issue. It looks like my server version" does not match the "game version". I've tried updating, restarting, and uninstalling/reinstalling the docker now but I keep getting the same message when I get into satisfactory. 

 

I saw in your notes you state to "restart" the container if a new version of the game comes out but wasn't sure if that meant something different from what I tried above?  I'm still pretty new when it comes to this stuff so apologies if it is a dumb question.

2 hours ago, Nodiaque said:

For now, I replaced the script with modified option, but since it's in a place where files aren't saved between container reload, it's not a permanent solution

Why? Please read the variables from the container and you will see how and where to put that, there are multiple posts about that too.

A few posts above yours is the solution:

 

Please also set the vairiable Automatically Update Game to false like mentioned here:

 

4 hours ago, sgtdiddlywink said:

I've tried updating, restarting, and uninstalling/reinstalling the docker now but I keep getting the same message when I get into satisfactory. 

I don‘t know if you still have to update the Client (on your local PC) to the experimental branch, that was necessary back then when I created the container.

Have to look into that.

 

EDIT: I've tried it now and have no issue whatsoever connecting to the server:

 

This is the vanilla Satisfactory container, nothing changed in the template, on the right upper side from the screenshot you can see that I'm connected to the server and on the right lower side that beta or experimental on my local PC (client) is not enabled.

 

So to speak, if you leave everything as it is (Server and Client side) without anything custom and beta or experimental not enabled everything is working as expected.

8 hours ago, ich777 said:

Why? Please read the variables from the container and you will see how and where to put that, there are multiple posts about that too.

A few posts above yours is the solution:

 

Please also set the vairiable Automatically Update Game to false like mentioned here:

 

My search failed when I search for the word ptr thus I didn't see this post. 

 

But again, I understand it work with the var GAMEID but wouldn't it make the template cleaner to have simple STEAMPARAM so it's explicit? This is more of a "hack" if through another param that just happen to work. 

1 hour ago, Nodiaque said:

but wouldn't it make the template cleaner to have simple STEAMPARAM so it's explicit? This is more of a "hack" if through another param that just happen to work. 

No, this is not in any way a hack.

Why would you even consider that this is a hack? I think in all of my templates it is mentioned that if you want to use a static, beta or whatever version you have to append -beta, -beta experimental or whatever the case is.

 

You always have to append the parameters for a beta or experimental branch to the GAME_ID or better speaking Steam App ID and these parameters ar tied to the GAME_ID.

 

A hack would be if you pass over another SteamCMD parameter for example +@sSteamCmdForcePlatformType windows in the GAME_ID variable.

A hack is using something that is meant for one thing for another. In the template, under game_ID, is just say to input gameid from a list. I also don't see anywhere that it says to use this to pass other command to steam. Maybe I got the only template without that info? Still, if a param says GAME_ID, I don't expect to input anything else under GAME_ID. Does it work? Yes, I'm not saying it doesn't. I'm saying it's far from obvious that other steamcmd should be enter under this param, specially when there's so many other variable and even a game params one. I'm simply offering a suggestion that would simply make it easier to see "hey there's a place to put steam cmd" that will change 3 lines in the exec script. In the end, you're the owner, you do what you want.

 

Edited December 4, 20223 yr by Nodiaque

31 minutes ago, Nodiaque said:

A hack is using something that is meant for one thing for another. In the template, under game_ID, is just say to input gameid from a list.

Then you have a really old template:

Valheim:

 

7DtD:

 

Satisfactory:

 

I added this descriptions about a year ago if I'm not mistaken because especially for 7DtD users this wasn't really clear how to do.

 

 

 

31 minutes ago, Nodiaque said:

I'm saying it's far from obvious that other steamcmd should be enter under this param, specially when there's so many other variable and even a game params one. I'm simply offering a suggestion that would simply make it easier to see "hey there's a place to put steam cmd" that will change 3 lines in the exec script. In the end, you're the owner, you do what you want.

Thank you for the suggestion but not every user is doing it properly like you do it here, you even can put it in like that:

beta public-test betapassword yesimadebackups

without the dashes but this will only work if you append it right after the Steam ID.

 

I'm not completely against what you are saying but you have to keep that in mind what I've wrote above without the dashes, I really don't want to make things more complicated and most users get it how to do it, especially new users which will see the description.

If you look up several tutorials on how to install a experimental or beta branch it is common practice to put it right after the GAME_ID and strictly speaking it is tied to the GAME_ID

11 hours ago, ich777 said:

I don‘t know if you still have to update the Client (on your local PC) to the experimental branch, that was necessary back then when I created the container.

Have to look into that.

 

EDIT: I've tried it now and have no issue whatsoever connecting to the server:

 

 

This is the vanilla Satisfactory container, nothing changed in the template, on the right upper side from the screenshot you can see that I'm connected to the server and on the right lower side that beta or experimental on my local PC (client) is not enabled.

 

So to speak, if you leave everything as it is (Server and Client side) without anything custom and beta or experimental not enabled everything is working as expected.

I went back through and confirmed everything was vanilla on my side as well. Nothing changed from when I installed the docker and BETA turned off on steam side as well. See below for the message I keep receiving when I connect to the server. 

 

And here is the docker page.

 

I appreciate your time and let me know if I'm missing something obvious.

 

55 minutes ago, sgtdiddlywink said:

I appreciate your time and let me know if I'm missing something obvious.

Have you removed the satisfactory folder too which lives in your appdata directory before reinstalling the container?

 

I can confirm that my container is on version 209846

Question: Is this right? seems the update for the docker is unlinked which makes me think something in my config is off

4 minutes ago, Necrotic said:

Question: Is this right? seems the update for the docker is unlinked which makes me think something in my config is off

No, this is not related.

 

The container pulls the game on the first start and it is saved to the appdata directory.

 

Please answer the question: have you removed the satisfactory folder from your appdata directory before reinstalling the container from the CA App?

4 hours ago, ich777 said:

Then you have a really old template:

Valheim:

 

7DtD:

 

Satisfactory:

 

I added this descriptions about a year ago if I'm not mistaken because especially for 7DtD users this wasn't really clear how to do.

 

 

 

Thank you for the suggestion but not every user is doing it properly like you do it here, you even can put it in like that:

beta public-test betapassword yesimadebackups

without the dashes but this will only work if you append it right after the Steam ID.

 

I'm not completely against what you are saying but you have to keep that in mind what I've wrote above without the dashes, I really don't want to make things more complicated and most users get it how to do it, especially new users which will see the description.

If you look up several tutorials on how to install a experimental or beta branch it is common practice to put it right after the GAME_ID and strictly speaking it is tied to the GAME_ID

I understand. With the new template having the information for it, it's already more obvious that it can be used for something else. 

2 hours ago, ich777 said:

No, this is not related.

 

The container pulls the game on the first start and it is saved to the appdata directory.

 

Please answer the question: have you removed the satisfactory folder from your appdata directory before reinstalling the container from the CA App?

Looks like the folder for satisfactory and steamcmd are still in appdata. Do I need to remove both directories completely from appdata? 

8 hours ago, sgtdiddlywink said:

satisfactory

If you remove this folder from your appdata directory it should do the job just fine.

Just make sure that you remove the container first, then the above mentioned directory and then pull a fresh copy from the CA App.

 

Usually the container should pull the update on it's own, don't know what's preventing that on your system, do you maybe have some AdBlocker or something like that on your network?

9 hours ago, ich777 said:

Usually the container should pull the update on it's own, don't know what's preventing that on your system, do you maybe have some AdBlocker or something like that on your network?

No adblocker on the system. I only removed the "satisfactory" directory and left the "steamcmd" directory in place. Now I'm just getting the message that the "The server appears to be offline". Which is weird because the address and port should still be the same? Any issues with me wiping both the "satisfactory" and "steamcmd" directory and reinstalling the container completely? 

1 hour ago, sgtdiddlywink said:

Which is weird because the address and port should still be the same?

What does the log from the container say? Did you wait so that the container fully started and downloaded the game?

2 hours ago, ich777 said:

What does the log from the container say? Did you wait so that the container fully started and downloaded the game?

Never mind, I restarted the container and now it is back up. Thanks for the help.

On 12/4/2022 at 3:26 PM, ich777 said:

No, this is not related.

 

The container pulls the game on the first start and it is saved to the appdata directory.

 

Please answer the question: have you removed the satisfactory folder from your appdata directory before reinstalling the container from the CA App?

Hmm no, this container has been there with its folder for a long time. I haven't re-installed the container at all. Is this a new requirement? Do I just remove the folder and docker, add it back, start it and then copy over the savefile as well as the config file?

19 minutes ago, Necrotic said:

Hmm no, this container has been there with its folder for a long time. I haven't re-installed the container at all. Is this a new requirement?

Uh, sorry I responded to the wrong user.

 

No, this is not a new requirement.

You can also set validation to true, let it finish validation and then set validation to nothing or false.

 

Usually the container pulls the files on start because it‘s checking through SteamCMD if there is an update.

How can I revert my beta valheim to standard without loosing the save?

17 minutes ago, Meatballs said:

How can I revert my beta valheim to standard without loosing the save?

First of all I have to point out that I don't know if the new save file (beta) is compatible with the stable one.

 

To revert back to stable:

1. In the template set the GAME_ID back to: 896660 and set Validate Installation to true
2. Let the container fully start (open up a log to see the progress)
3. After it fully started stop the container again and delete true from Validate Installation in the template so that it is empty again
4. Start the container

You should be back on stable, but keep in mind I don't know if the save files are interchangeable.

1 hour ago, ich777 said:

First of all I have to point out that I don't know if the new save file (beta) is compatible with the stable one.

 

To revert back to stable:

1. In the template set the GAME_ID back to: 896660 and set Validate Installation to true
2. Let the container fully start (open up a log to see the progress)
3. After it fully started stop the container again and delete true from Validate Installation in the template so that it is empty again
4. Start the container

You should be back on stable, but keep in mind I don't know if the save files are interchangeable.

Thank you, according to the devs they should be.

EDIT: Just did it, works perfectly fine! Thanks!

 

Edited December 6, 20223 yr by Meatballs

now that Creativerse Definitive Edition just released they have added support for setting up a dedicated server via SteamCMD:
https://docs.google.com/document/d/1rAeuk7qFinUyPRJGk4x6Dim3rmQN2zoLaR3PNR0roU4/edit
is there any chance you could add this to unraid like you've done with so many other server thanks 😁

Not sure if anyone is seeing this with the new Mistlands update. Not even sure if it's related to this docker container or if it's something with the Mistlands update. Just figured I would put what I'm seeing and doing here in case anyone else comes across this.

 

My buddies told me the update came out today and asked me to update the server. I thought some of these steam servers had auto updates so I checked logs this morning and it looked like it was checking for update every hour and failed on something, then restarted the server. So I did what any IT pro would do, I turned it off and turned it back on again. I kept logs up and watched it download and install the update. I go back to work and heard some buddies were playing on steam deck and computer during the day. No one says anything so I think all is fine. I get on to play this evening after work and then saw a 1995 style icon of a computer/server with a wire to a modem and an red X in the line flashing in the top left hand corner? I was like wts mate? and my buddies were like oh yea your going to get booted. Then we all saw it and got booted. That's when my buddies said they had this happen to them a couple times today and one said he thought it was just because he was on steam deck and had bad signal. So, I checked logs again and saw the same thing I saw this morning where it looked for an update a bunch of times and a couple of the times i saw logs said "Redirecting stderr to '/serverdata/serverfiles/Steam/logs/stderr.txt'". So I checked this file and all it said was "CAppInfoCacheReadFromDiskThread took 154 milliseconds to initialize". Logs for the auto update check before were like 2 and 4 milliseconds. 

 

Long story short, I think there is an issue with the auto update game. Again, I dunno if it's the docker container (i doubt), or if it's the new Mistlands update (i tried checking but didn't see anything on their end yet), or if it's just release day and the servers couldn't handle all the auto update request and timed out causing this issue. 

 

What did I do? I turned off the auto update game setting and everything seems to be fine so far. Just a heads up.