Holynub

Just wanted to follow up. I got everything back up and running again. That's totally a way to specify a version for steamCMD to run, at least for 7 days to die. I didn't even need to restore from the backup of the server to get it working. In the GAME_ID field, you can put "294420 -beta alphaXX.X" where XX.X is the version you want, and the steamCMD will "opt-in" for that beta version. Thank god. We were prepping for a big zombie horde night and were looking forward to the chaos this weekend. Here's the procedure I did. Stop the docker container running the 7DTD instance Edit the config Under GAME_ID: set it to "294420 -beta alpha19.0" Start the 7DTD docker container Keep the logs open and wait for the container to finish updating Stop the container after its updated Re-copy Darkness Falls 3.02 server files into the installation (Done through either Crusader or Windows Explorer if you have it mapped) Start start the container after the server files have been pasted into the server directory Enjoy the older version of Darkness Falls

Thanks Ich. To answer some things: No, I actually have a backup of the server prior to the outage. So I can restore the files in the server folder to a pre-update state. I was mainly looking for a way to prevent steamcmd from updating or changing it to update to a specific version when I start up the docker container. Passing the beta parameter to steamcmd sounds like that would work. Would I need to change the appID in the docker config to something like: "294420 -beta alpha19.0"? Or does appID only look for an integer?

Hey Ich777, I have a very peculiar use-case that I could use some assistance with. I'm running a 7 Days To Die instance with the Darkness Falls mod on it. The scenario is like this: We have a group playing 7 Days to Die Alpha19, with Darkness Falls V3.02 There is an update for both 7 Days to Die (Alpha 19.1) and Darkness Falls (3.10) Both of those are completely incompatible with our current game, and requires a complete map restart Everyone is running a rolled back instance of 7dtd on their client and the server was not updated so we can keep playing on our current map A power outage hits the server causing it to reboot On boot, steamcmd runs through and updates the server 7dtd instance making the server no longer compatible with our Darkness Falls version and game save I have a backup of the server files prior to today's power-outage/update I can restore the files on the 7dtd server to put it back to how it was before Is there any way to start the container and not have steamcmd update the 7dtd base application? Any advice would be super helpful.