Інсталювати Steam
увійти
|
мова
简体中文 (спрощена китайська)
繁體中文 (традиційна китайська)
日本語 (японська)
한국어 (корейська)
ไทย (тайська)
Български (болгарська)
Čeština (чеська)
Dansk (данська)
Deutsch (німецька)
English (англійська)
Español - España (іспанська — Іспанія)
Español - Latinoamérica (іспанська — Латинська Америка)
Ελληνικά (грецька)
Français (французька)
Italiano (італійська)
Bahasa Indonesia (індонезійська)
Magyar (угорська)
Nederlands (нідерландська)
Norsk (норвезька)
Polski (польська)
Português (португальська — Португалія)
Português - Brasil (португальська — Бразилія)
Română (румунська)
Русский (російська)
Suomi (фінська)
Svenska (шведська)
Türkçe (турецька)
Tiếng Việt (в’єтнамська)
Повідомити про проблему з перекладом
./steamcmd.sh +login [USER] [PASSWORD] +force_install_dir /home/steam/arkdedicated +app_update 376030 +quit
this might be useful to you also
http://www.ark-survival.net/en/2015/07/18/automatic-update-for-linux-servers/
The one I'm using has bits and pieces from the script on the page you've linked to, the problem isn't with the script though, its with steam retrieving an unupdated buildid for ARK, in this case 716656 whenever run.
For whatever reason, updating the game forces steamcmd to update its cache of information and then the correct buildid is displayed when running the steamcmd.sh command listed above.
Is there a bug in steamcmd or am I passing incorrect parameters into steamcmd.sh in order to get just the version number of the latest patch?
try that without quotes
^ thats what your looking for i believe
Tried this, same result with or without quotes.
Makes me wonder if there's a temporary file somewhere that i need to delete before steam is able to fetch this info.
./steamcmd.sh +login anonymous +force_install_dir /steam_temp/ +app_update 376030 +quit
It will fail if ShooterGame is already running, which is fine because it still retrieves the new database info on the version number. Now add in +app_info_print to get the latest version number, compare and off you go.
Well done, Valve!
You then check first the errorcode. If it is not 0, the login has failed.
If it is 0 you check the output which should contains something like this:
If you can't pipe the output to the next command: This is SteamCMDs fault, which directly writes to console windows instead of just printing. to 'fix' that you just need to flood SteamCMDs buffer with data, so it is flushed in a more normal behaviour. In this case doing this helps:
Greetings
However, I found a workaround for this issue: you have to remove appcache/appinfo.vdf before checking for updates every time. The folder appcache is located inside the steamcmd directory.