Fixes an issue where reports could not be submitted.

https://github.com/BadgerCode/tttdamagelogs/releases/tag/v3.3.4

Updates version in code to 3.3.3

V3.3.3

See Github for the full list of bug fixes and improvements

https://github.com/BadgerCode/tttdamagelogs/releases/tag/v3.3.3

None Provided

v3.3.2 - Hotfix for kill credit

Fixes an issue - No matter how a player dies, if they were recently pushed, the player that pushed them gets blamed

Details here - https://github.com/BadgerCode/tttdamagelogs/releases/tag/v3.3.2

v3.3.1

This hotfix fixes an issue where the addon would not work for fresh installs.

Details here:
https://github.com/BadgerCode/tttdamagelogs/releases/tag/v3.3.1

(See the next update)

This includes the fix for 3.3.1, but I forgot to version bump.

Version 3.3.0.

v3.3.0 changes[github.com]
vbadger-3.2.0 changes[github.com]

• Multiple reports prevent a player from being able to respond and play the game
  
• Some rows are mistakenly highlighted as a team kill
  
• Admin chat can't be closed
  
• The default slay reason is not set
  
• There is a net message error when requesting old logs - "Warning! A net message (DL_SendOldLog) is already started!"
  
• The damage logs are completely broken for some languages
  
• After about 2 months, old logs stop working and new logs stop recording
  
• Fall damage caused by a team member isn't highlighted as a team kill
  
• Some types of death/suicide aren't correctly recorded
  
• Database errors are hidden from the server logs

• Discord notifications for reports have been greatly enhanced. Read more[github.com]
  
• Weapons can now emit custom equipment events to enhance the damage logs. Read more[github.com]
  
• The damage logs addon will now check the repository for this workshop addon for updates