All info about the channeltag var is now on the wiki. It is now the standard method to have info relating to vars in the wiki rather than in the script.
)
* Improvements up command_backup.sh
added backup trap and improved lockfile support
changes to the messages displayed on screen
renamed some functions
other misc changes
(close double quote)
* move -type f before -mtime
* New gameservers & features (#1158
)
* Two # is now one block of settings & descriptions
* directories comments and logs naming
* dgibbs revision and root check
* update_steamcmd.sh Check is now done out of functions
* Better way to detect screen #1154
)
* Added no of days since last backup
* Added lock file creation to logs
* Improvements up command_backup.sh
Changes to the messages displayed on screen
added trap and improved lockfile support
renamed some functions
other misc changes
* Updated Version numbers
* Two # is now one block of settings & descriptions
* directories comments and logs naming
* dgibbs revision and root check
* Backup & Layout rework
* removed duplicate updateonstart
* Fixed missing space on [ERROR ]
[ ERROR ] instead of [ERROR ]
* Error space wasn't missing
Used to fit other comment sizes, i guess
* Anonymous login is now an info
Since login variable is removed for servers that don't need steam auth, this won't show a failure anymore but a simple info and anonymous login will be used.
* update_steamcmd.sh Check is now done out of functions
* solves hanging on update if steamuser is not set
* New gameserver layout & functionalities
* Better way to detect screen
As per #1154
Fixes https://github.com/dgibbs64/linuxgsm/issues/685
Tickrate needs to be lowered in order to be able to handle a large amount of players.
Default tickrate is 66.66, but the -tickrate commnand will round numbers to the lower integer. So i'll default at 66 and not -the more accurate- 67 to not worry anyone with a "non standard" value.
For the +r_hunkalloclightmaps 0, it fixes the hunk overflow crash on server startup when using maps with too much lights (and there are a lot of them). It changes the way lights are stored in RAM, the 0 mode (default one a few years ago, and still default one on clients) can handle a way larger amount of lights, but a theoretically a bit slower way. I noticed no difference, so it's a good thing to fix it by default.
I checked the default value, it's 4, not 2. A value of 2 is causing issue with physics while running complex builds' physics, a value of 4 fixes it.
To check the default value, input gmod_physiterations into your gmod console
gmod_physiterations
"gmod_physiterations" = "2" (def. 4)
I useful feature for developers.
This will enable a log to be created of everything that ran when
executing a command. It uses the set command.
When you run a command a file dev-debug.log is created and will output
set -x