Server setup issue
Moochie
Join Date: 2011-10-18 Member: 128058Members
Hi, I have set up NS2 servers in the past but I can't seem to update my servers to Build 221. I installed a new server from scratch with SteamCMD and it was version 220. Is there something that I am missing or does it take a few days to get the server files updated to 221? I can set up a server with my steam install but cause I have my servers on a dedicated server box I can not play NS2 cause steam has to be logged in for the server to run with the steam files.
Comments
The client and server are updated at the same time on Steam's servers.
I just tried it again and it updated to 221... Idk :P Thanks for your time.
True enough, but this won't be the case forever. Eventually, you'll just have to specify the mod # in your server config file and it should automatically download/update the mod whether or not the game is on that account. Also, there are a couple of current workarounds:
- Download the map/mod on your client account then copy the AppData\Natural Selection 2\Workshop folder over to the server
- Use your free copy of (or find someone with a free copy of) NS2 to put on the server account
Everyone gets the same error as the old version of the mod is not available in Steam Workshop anymore so the connection clients can't download the old version from there anymore. This severely hampers the mod development as you're literally going to break every server that runs your mod every time you update it.
Would be great to see it there, so we won't need to use steamcmd anymore.
"Natural Selection 2 Dedicated Server"
Then again, endar is right.
Which is why the current workaround is a bit poor, but can be done if you are vigilant about updating the server workshop files regularly.
Sorry I don't understand what you are saying.
What workaround?
What can be done?
What workaround?
What can be done?<!--QuoteEnd--></div><!--QuoteEEnd-->
I think i'm correct in saying he's talking about having the mod subbed on a client, then harvesting the workshop files from that client and uploading them to the server instance on a regular schedule. This doesn't work perfectly for the exact reasons you specify, hence the current workaround being poor :)
Honestly, other than us creating a script that runs scheduled git pulls, and having the server reboot on any changes (if empty) there's no other way right now; and trying to combine that with workshop files would be a nightmare.