Skip to content
This repository has been archived by the owner on Jul 17, 2023. It is now read-only.

Releases: CorruptComputer/ProtonDB-Tags

v1.2.2

29 Oct 17:20
02057cf
Compare
Choose a tag to compare

Changes:

  • Fixes #52
  • Improved caching logic around failed requests. Caches failed responses for 1 day to reduce server load on ProtonDB and Steam, making it faster to run after stopping a long-running check. In my testing, this reduced a 9000+ game library from over an hour to just a couple of minutes.
  • Adds a 3 second timeout to all requests, since by default there is no timeout for requests the script would wait indefinitely for a response that would never come. The exact timeout period may change in the future, this seemed like a good value to me for now though.
  • Add a time taken output at the end of the script to give some more info to the user. This should make it easier to spot when regressions that make it take longer happen as well.
  • Add a user agent to the script to allow ProtonDB and Steam to measure the traffic that is generated on their servers by this script.

v1.2.1

11 Jul 13:56
Compare
Choose a tag to compare

Changes:

  • Fixes issues when using the Flatpak version of Steam (#49)

v1.2.0

09 Jul 03:10
959cc73
Compare
Choose a tag to compare

Changes:

  • Improved caching logic, fixes #11
    • Both the Steam Native status and ProtonDB rating are cached for a minimum of 7 days + a random offset between 1 and 7 days per game.
    • This random offset should help speed up the scan times if you run this script multiple times per week and reduce the load caused on those services by this existing.
    • Current caches will be incompatible, however the script should handle these nicely so those old values won't be sitting around.
    • The cache can be bypassed by adding --skip-cache as a command-line flag. This will still add the value to your local cache, but will just skip reading it and force fresh data to be retrieved.
  • Option to read games list from Steam API
    • The first time you try it, this will ask you for your Steam API key and Steam ID.
      • These values can be cleared from the config by adding the --clear-config argument.
    • Both of these will only be stored locally, and will only be used to contact the Steam API.
      • This config will be located in one of these two locations, depending on if you have $XDG_CONFIG_HOME set.
        • $XDG_CONFIG_HOME/ProtonDB-Tags/config.json
        • $HOME/.config/ProtonDB-Tags/config.json
    • Be warned that using this option will most likely clear the current tags from some of your games, and should only be used as a work-around if games aren't showing up for you.
    • This can be used by adding --fetch-games or -f as a command-line flag.
  • Fixes #41
  • Fixes #42
  • Swap broken TravisCI tests with GitHub Actions tests.
  • Remove some skipped pylint checks, as these issues have been fixed.
  • Update README.md and add issue templates.

v1.1.1

22 Jun 15:50
Compare
Choose a tag to compare

Changes:

  • Better calling for "steam://resetcollections" on systems that don't use FireFox. Thanks @Rojikku!
  • Slightly longer sleep time for Steam API calls to reduce the chance of being rate-limited. Thanks @Rojikku!
  • Added counter to script so you can tell how far into it you are. Thanks @Rojikku!
  • Change cache location to be XDG compliant. Thanks @themadprofessor!
  • Remove Discord server from README since it was unused.
  • Updated dependencies.

v1.1.0 Workaround release for #32 and #33

01 Nov 03:10
7abf49e
Compare
Choose a tag to compare

This release fixes and issue with the AUR package not being able to create the steamNativeCache.json file and works around an issue with the script not being able to update categories for games with the new Steam Library.

v1.0.0 First Stable Release!

20 Aug 00:59
Compare
Choose a tag to compare

From now on this repo will conform to Semantic Versioning. All development work will happen in the dev branch, and all PR's should target that branch. Master will always be on the latest stable release, so it will always be safe to use when unsure.