Skip to content

WindowsGSM v1.25.4.8

Latest

Choose a tag to compare

@PapaGordon PapaGordon released this 09 Nov 23:32

WindowsGSM asked for a Steam Guard code again and again on account-based servers, even with a saved password. WGSM always started SteamCMD with the username and password, so SteamCMD never used its own saved login. This update fixes that.

Before each account login, WGSM now tests SteamCMD's saved login for that account. If it works, WGSM logs in with the username only. If it is missing or expired, WGSM uses the saved password as before. This covers installs, updates and DayZ/Arma 3 Workshop downloads. The test adds a few seconds to each account update.

Encrypt-SteamPassword.cmd now connects to Steam once after saving the password. Enter your Steam Guard code if SteamCMD asks for it and wait for Steam login saved. After that, updates should run without another code. If you already logged in by hand in bin\steamcmd, you do not need to run the helper again.

SteamCMD can print Assertion Failed: Failed to write file after download during login. That line comes from Steam's cloud sync and does not stop the login.

To update, close WindowsGSM, back up the old EXE and replace it with the new WindowsGSM.exe, or use the ZIP. Your servers and saved credentials stay as they are.

Tested: Release build, 42 Workshop checks, 11 encrypted-password checks, 63 plugin compatibility checks and the helper against a stand-in SteamCMD. Repeated logins without a password or Steam Guard code were confirmed with SteamCMD on the live server.