Releases: BadgerCode/tttdamagelogs
v3.11.0 - Non-innocent bots, non-latin report reasons/answers, voice chat fix
To download the update, follow the steps in the Installation Guide.
Release Notes
Bug Fixes
v3.10.0 - CR4TTT RDM logic for all teams
To download the update, follow the steps in the Installation Guide.
Note: When updating from a version before 3.6.0, you should backup your Lua configuration file
Otherwise, you may accidentally delete your configuration changes!
Release Notes
Features
v3.9.1 - Fix health stations in TTT2
To download the update, follow the steps in the Installation Guide.
Note: When updating from a version before 3.6.0, you should backup your Lua configuration file
Otherwise, you may accidentally delete your configuration changes!
Release Notes
Bug Fixes
v3.9.0 - Simplified chinese
To download the update, follow the steps in the Installation Guide.
Note: When updating from a version before 3.6.0, you should backup your Lua configuration file
Otherwise, you may accidentally delete your configuration changes!
Release Notes
Features
Code Quality
v3.8.0 - 64-bit bug fix, config sync bug fix, code improvement
To download the update, follow the steps in the Installation Guide.
Note: When updating from a version before 3.6.0, you should backup your Lua configuration file
Otherwise, you may accidentally delete your configuration changes!
Release Notes
Bug Fixes
- #98 - Fixes the report response menu failing to open on the 64-bit branch of Garry's Mod
- Fixes #96
- Thanks wgaylord
- #94 - Fixes configuration not fully synchronising to the client
- This should fix #88 (some roles can't access the RDM manager)
- Thanks wgaylord
Code Quality
- #93 - Various code improvements (thanks Noahbg)
v3.7.0 - sAdmin support & improvement
To download the update, follow the steps in the Installation Guide.
Note: When updating from a version before 3.6.0, you should backup your Lua configuration file
Otherwise, you may accidentally delete your configuration changes!
Release Notes
Bug Fixes
- #89 - Optimises use of think hook
- Thanks Noahbg
Features
- #87 - Adds support for sAdmin system
- Thanks DSomik
v3.6.2 - Some small fixes/improvements
To download the update, follow the steps in the Installation Guide.
Note: When updating from a version before 3.6.0, you should backup your Lua configuration file
Otherwise, you may accidentally delete your configuration changes!
Release Notes
Bug Fixes
- #85 - Fixes a typo in the new configuration loader
- Thanks Flapchik
Additional changes
- #86 - Tidies up map cleanup code
- Thanks Flapchik
v3.6.1 - Fix scripted entities names
To download the update, follow the steps in the Installation Guide.
Note: When updating from a version before 3.6.0, you should backup your Lua configuration file
Otherwise, you may accidentally delete your configuration changes!
Release Notes
Bug Fixes
- #82 - Fixes some scripted entities showing up with the wrong name
- Thanks wgetJane
v3.6.0 - Use data folder for addon configuration (JSON)
To download the update, follow the steps in the Installation Guide.
Note: When updating from a version before 3.6.0, you should backup your Lua configuration file
Otherwise, you may accidentally delete your configuration changes!
Release Notes
The big change in this version is to the addon configuration.
- Previously, configuration was managed in a lua file-
lua/damagelogs/config/config.lua- This made it impossible for Workshop users to configure the addon
- It made updating the addon risky, as you may accidentally overwrite your configuration changes with the new files
- Now, configuration will be stored in a JSON file, in the server's data folder
gmod_server/garrysmod/data/damagelog/config.json
- The damagelogs will first try to load configuration from the lua file, then load configuration from the JSON file
- Configuration settings in the JSON file will overwrite the settings from the lua file
The wiki has been updated to document how the new system works and what each setting is for.
Features
v3.5.2 - Patch for old logs around midnight not being accessible
To download the update, follow the steps in the Installation Guide.
Note: When updating your copy of the damage logs addon, backup your configuration files!
Otherwise, you may accidentally delete your configuration changes!