Version 2.3.0: TTT Improvements, QOL Changes, and Bug Fixes

Updating

If using the Installer version, download the Installer below, and run it. It will all the files automatically (you do not need to resetup, as it may imply).

In theory, the updating process should be fully automatic (well, it'll prompt you) now. Run the program as normal (it may restart once or twice), if it asks you to overwrite constants, say yes.

Changelog

Added

• New log types to TTT Summary Output
  • Body IDing
  • Detective DNA Scans
  • Tasing
  • Shop Purchases
• Automatic checking for updated constants
• Add detection for wallhack purchases
• Option to show time for gunplant detection

Changed

• Added option to clear output.log on program start
• Cleaned up TTT implementation
• Ignore gunplant detection in LR/LG

Fixed

• Outdated default GameME link for eGO
• Ensured that users can see the FileNotFound error when searching for
  output.log
• Various minor errors in the documentation (spelling, old
  information, etc)

Version 2.2.0: Windows Installer & Bug Fixes

Version 2.2.0

Updating Procedure (READ THIS!!!)

As of this version, STonitor can now be installer via an Installer (yay! no more complicated Python installs). You can still manually install/update the Python script raw if you'd like (the Installer version is compiled, and may trigger antivirus warnings. it's also less stable, if you want more guaranteed setup, stick to the manual version assuming you know what you're doing).

The Installer version is separate from any manual version you may have installed previously, so you will need to port your data over. You can do this by seeing the Porting to Compiled (Installer) Version from Manual Installation section below. If you're sticking to manual installation, simply download the new Source Code ZIP and override as you normally would, then skip to Updating Manual Installation.

Porting to Compiled (Installer) Version from Manual Installation

• Follow the documentation on installing STonitor via the Installer, then come back here once it's complete (it's really simple!).
  • Make sure that you do not install it to the same folder as your old STonitor installation (it will still work, but may be confusing later on). The default installation location should work fine (unless you already installed it there)
  • Do not follow the normal setup process.
• If you already had STonitor installed previously, your autoexec.cfg should already be configured with a output_log line, if it's not for some reason, you'll need to do so.
• Now that STonitor is installed, you'll need to port your data over. Follow the following steps in doing so:
  • Find your old STonitor installation, this is wherever you installed STonitor previously while following the manual installation steps
  • Open the data folder in your old STonitor installation
  • Run the new STonitor once. This can be done by double-clicking the desktop shortcut (if you asked the Installer to create one), or by going into your Start Menu and finding STonitor. (this is the same way you run any other program).
  • The program will tell you that data files have been created, then ask you if you want to open the data folder. Enter Y, then press Enter. The data folder for the new installation should open in File Explorer. If not, see the FAQ entry on finding your data folder.
  • Copy the entire contents of your old STonitor data folder into the new data folder. Override all files if prompted.
• Run (the new) STonitor again. It will perform another data file update, you do not need to do anything this time (just press Enter).
• Run the new STonitor and verify that everything works as expected.
• You can now delete the old STonitor installation in it's entirety.
• Proceed to the Final Update Steps

Updating Manual Installation

• After you've overridden the contents of the old STonitor installation with the new files, run STonitor once.
• STonitor will move your data files to the new location, and update them along the way.
• Proceed to the Final Update Steps

Final Update Steps

• Open your data folder.
• Delete constants.yaml
• Delete buttons.yaml (you may want to copy any custom buttons you have made, and append them back after everything is regenerated)
• OPTIONAL: Delete settings.yaml so that the program uses the new colour defaults (make sure to backup any other settings), OR override the colours portion of your existing settings.yaml with these values
• Run STonitor once. It will regenerate the deleted data with the proper new values, you do not need to do anything additional (just press Enter).
• You can now use STonitor!

Changelog

Added

• Shows disclaimer on startup
• Created installer for Windows

Changed

• Added healthshot to gunplant ignore
• Updated GitHub update checking URL to new one
• Moved data folder to native data location (APPDATA, .config)
• Documentation updated to reference Windows installer
• The program now asks if you want to open the data folder if it generates it
• Clarify additional step in manual BAT setup instructions

Fixed

• Incorrect default colours listed in settings documentation
• Typo in default button config
• TTT summary output not showing damage dealt
• Edge case in which the program would crash if there was a specific issue retrieving account age
• Broken update checking as a result of repo URL change

Version 2.1.2: Better Defaults

Version 2.1.2

This minor patch can be skipped, there's not much changing in it. See changelog. Last feature update was 2.1.1

Changelog

Changed

• Default colours so that they're more readable with default Command Prompt

Removed

• Unused colour playtime

Version 2.1.1: COLOURS, New & Updated Detections, and More

Version 2.1.1

Updating

• Delete constants.yaml in the data folder
• Extract new release ZIP into old folder and override all files when prompted
• Reinstall requirements (pip install -r requirements.txt)
• Run STonitor once, allow it to generate new files, then you can run it as usual
• OPTIONAL: Review and update new settings

Changelog

Added

• jb_undertale pictionary draw button to default ignore
• Various entries regarding JB logging in the known bugs documentation page
• Coloured output to make wall of text easier to understand
• ST kill detection
• Summary output for weapon pickup

Changed

• Better invalid status line logging
• Version number now shows in ready message
• Gunplant detection now simply checks if a T picks up a CT's weapon before that CT dies

Fixed

• Outdated default GameME link for eGO
• Space padding incorrect on button grief output
• Fix odd invalid status line error
• Typo in documentation index page

Removed

• Feature list is no longer shown in README

Version 2.0.1: Status Regex Bug Fix

Version 2.0.1

Updating

• Delete constants.yaml in the data folder
• Extract new release ZIP into old folder and override all files when prompted

Changelog

Fixed

• Regex not matching status lines when space padded

Version 2.0.0: Buttons, Better Encoding, Bug Fixes, and More

Version 2.0.0

Updating

• Delete constants.yaml in the data folder
• Extract new release ZIP into old folder and override all files when prompted
• Run STonitor once, allow it to generate new files, then you can run it as usual

Changelog

Added

• Clarification on common status issues in documentation
• Check if output.log exists at runtime
• Ability to hide world actions from summary output
• Steam level to status
• Basic support for new ST role in logs
• FAQ entry for new GameME detections
• Known bugs page on documentation
• Show error message on status error
• Button ignore & alias file

Changed

• Output.log now opens in UTF-8 encoding
• Non-context roles now show as T/CT to avoid confusion
• Rewrote status parsing code to have less spaghetti
• Other retrievable options are still retrieved if account is private
  now

Fixed

• KeyError on invalid weapon name (MFD Detection)
• Status getting stuck wo/ #end
• Multi-parse edge cases causing odd bugs
• Early vent false positive on some maps

Version 1.1.2: TTT Bug Fix

Version 1.1.2

Updating

• Delete constants.yaml in the data folder
• Extract new release ZIP into old folder and override all files when prompted

Fixed

• TTT damage regex not matching if damage was dealt with a headshot

Version 1.1.1: Server Playtime

Version 1.1.1

Updating

• Reinstall requirements, to do this, run the command pip install -r requirements.txt again. If you don't remember how to do this, check the documentation.
• Extract new release files into old directory and override when prompted
• Delete constants.yaml and let the program regenerate it

Added

• Ability to retrieve server playtime using GameME

Version 1.0.1

Version 1.0.1

Updating

No additional steps are needed to update STonitor, just extract and override all files from this release to your original release. Run the program once, and the new settings parameters in this release will be updated in your settings.yaml, you can leave everything as default or change it. You can also delete session.json as it is now unused, but leaving it makes no difference.

Added

• Ability to wipe output.log on error to try to automatically resolve errors arising from corrupted logs

Changed

• Exempt potential FK/FD during LR and LG instead of just LG
• TTT now uses caching similar to status and JB
• Parsed arrays are now cleared as soon as output.log is cleared to minimize unneeded memory usage

Fixed

• LR detection reporting wrong death
• IndexError in case of corrupted TTT logs
• TTT full logs not being parsed if sm_logs was run during the round to retrieve partial log

Deprecated

• session.json is no longer used, and can be removed

Initial Release

Version 1.0.0

Initial STonitor release, no need for any notes here. Fingers crossed, and good luck!