Hello,
I am lost on this one, for hours cannot find what is going on.
Creating a new machine with a rust server, to install run the steamcmd and then
force_install_dir C:\rustserver
login anonymous
app_update 258550
After install when try to connect to the server I get that my client needs to be updated, checked on the server and the message said I was trying to connect with protocol 2357 and needed 2359.
Did a lot of work and figure the 2359 is actually the staging version, if I run my staging client it connects.
Try remove everything, reinstall many times, same all the time app_update 258550 is installing the staging branch.
Anyone has any idea on what is going on here, where I am doing wrong?
Thank you for any help or suggestions.
Install app_update 258550 is installing the staging version.Not An Issue
Check your server startup parameters and see if you have a +beta setting
delete the entire contents of your steamcmd directory except for the steamcmd.exe
when complete click the steam cmd and wait for it to do its thing. type quit in the cmd window. then run your rust server update as usual.
Hello,
Thank you for the suggestions, the reinstall of steamcmd worked.
Now why did that the fist time is a mistery, I installed steamcmd the same way the first time.
ive had that happen to myself a few times over the last 6 months or so.. its either steam or probably fb that fook up ... maybe something cashed who knows as long as it's sorted is all that matters ..
It's a SteamCMD issue. You can completely avoid it by just specifying the branch with -beta.
-beta public
Wulf
It's a SteamCMD issue. You can completely avoid it by just specifying the branch with -beta.
-beta public
no he set up a regular server not the staging.
app_update 258550 ive also had it myself when you do a steam update it loads staging files for some reason. its either steamcmd or fp. doing something wrong or cranky
Yes, and I can be avoided by setting what I said above. Setting the branch specifically makes it use that branch. This is not a new issue.nashslash
no he set up a regular server not the staging.
app_update 258550 ive also had it myself when you do a steam update it loads staging files for some reason. its either steamcmd or fp. doing something wrong or cranky
sorry wulf just to clarify using this syntax with the steamcmd will only download the latest stable released rust version and NOT the staging?
its confusing to add the term beta, it even says on the fp wiki Rust is Rust has the Steam App ID 258550 with no mention of -beta public
+app_update 258550 -beta public +quit
-beta is just for specifying the branch. The reason the people are having the issue here is that they somehow were given the staging branch instead of public.sorry wulf just to clarify using this syntax with the steamcmd will only download the latest stable released rust version and NOT the staging?
its confusing to add the term beta, it even says on the fp wiki Rust is Rust has the Steam App ID 258550 with no mention of -beta public
+app_update 258550 -beta public +quit
still asking for clarification... so for a regular rust server the correct syntax is
+app_update 258550
with nothing afterwards ? as stated in the fp wiki.
no one was asking about how to download the staging branch only that they had somehow downloaded it using this correct rust syntax
Every version of Rust has a BRANCH. The -beta arg specifies the BRANCH.still asking for clarification... so for a regular rust server the correct syntax is
+app_update 258550
with nothing afterwards ? as stated in the fp wiki.
no one was asking about how to download the staging branch only that they had somehow downloaded it using this correct rust syntax
public = the release version of the game
staging = staging
Specifying the branch tells SteamCMD to specifically download that BRANCH. This is correct syntax, just the way to make sure you get that branch.
Locked automatically