Skip to content

Releases: Baricus/salmonstats

v1.2.0

Choose a tag to compare

@github-actions github-actions released this 19 Nov 05:42

Another release no one in particular asked for! This adds a players subcommand and a --list option to show all your teammates! Along with this comes re-works to ensure that any players who change their name are consistently tracked. As a nice bonus of this, you can search for a player by their ID (displayed as the first row of the new command) or by any username they've used while playing with you.

The above but as a bulleted list for some reason:

  • Added "players" sub-command
    • Displays all players matching your provided filters
    • Shows the nintendo ID of the player and all usernames you've seen them use

v1.1.0

Choose a tag to compare

@github-actions github-actions released this 28 Oct 03:45

This release adds a new sub-command for tracking wins, losses and related statistics. The full changelog is below.

  • Added "game" sub-command
    • Displays:
      • Games won/lost/disconnected
      • Win-rate/loss-rate/disconnect-rate
      • Average wave reached
  • Internal reworks/code cleanup

v0.1.0

Choose a tag to compare

@github-actions github-actions released this 22 Aug 00:48

salmonstats is a program now! It is definitely unfinished, but it is functional enough that I'm using it to track my statistics.

Normally I'd go over the changelog here, but since this is the first version, here's a few notable features:

  • Automatically parses splatnet3 json as dumped by nxapi or equivalent programs
  • Provides CSV output of boss kill data and king kill/scale data
  • Provides basic statistics for both boss kill data and king kill/scale data
  • Allows for filtering by:
    • Time period (before/after)
    • Last X matches
    • Players (with/without)
    • Stage
    • Private battles (normally filtered; can be added to statistics)
  • Configurable offsets for individual boss kills (for badge tracking)

If you do find any of that interesting, give salmonstats a try! Let me know how it could be improved for your use-case by opening an issue.