The installer will do the following on an issue downloading the server
files in an attempt to fix the problem.
# Attempt 1-4: Standard attempt
# Attempt 5-6: Validate attempt
# Attempt 7-8: Validate, delete long name dir
# Attempt 9-10: Validate, delete long name dir, re-download SteamCMD
# Attempt 11: Failure
All goldsrc files will run a validate multiple times as well to reduce
the chance of the files not downloading due to a bug in steamCMD.
Fixed the server looping when it shouldnt
Sometimes I need to delete the SteamCMD dir for testing. I have added
functionality to automatically re download if missing. Will also prevent
any risk of steamcmd.sh command no found error.
Added fn_tmuxcheck for all the special people who do not know how to
RTFM or use Google then leave a comment asking what 'tmux: command not
found means' I'm not bitter...honest!
Added fn_tmuxcheck for all the special people who do not know how to
RTFM or use Google then leave a comment asking what 'tmux: command not
found means' I'm not bitter...honest!
* Major changes to terminal and log messages.
* More constant and improved wording of terminal and log messages.
* New local variable "modulename" that is displayed in terminal and log
messages.
* Added commented descriptions to most functions.
This moves all the defining functions to its own file and out of the
main script file. This has made the main scrip file much smaller and
moved most code to the functions dir
Created update checker using SteamCMD. After some advice from SteamDB on
Twitter I found out you can get depot files directly from SteamCMD.
SteamDB update checker is still present however is only used if steamcmd
fails (SteamDB advised they cannot guarantee the accuracy of there depot
files).
https://twitter.com/SteamDB/status/546720685260017664
There are 3 different update checkers available as a failover and will
run in the following order as required.
1. SteamCMD update checker
2. SteamDB.info update checker
3. Server Log update checker
Daniel Gibbs
Ben Lyall
Scarsz