Jamstats

Latest version: v1.4.12

Safety actively analyzes 638925 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 2 of 5

1.3.0

These enhancements all apply to the web interface. They were requested by announcers who use JamStats to help with calling games.

* Added **Jammers table**: a page with a table for each team, with a row for each jammer. Provides jams jammed, total points, jams with lead, % jams with lead and jams with lead lost
* Added **All Penalties table**: a page with a table for each team, with a row for each skater. Provides penalty count. Rows are colored by penalty count: 0-4 green, 5 yellow, 6 orange, 7 red
* Added **Pronouns to skater roster**: only available with CRG v2023, which can capture skater pronouns

![image](https://github.com/dhmay/jamstats/assets/714077/0c0dc4df-a3c1-4ac5-9e71-2b12867dd30e)
![image](https://github.com/dhmay/jamstats/assets/714077/8b0ee9cb-1b14-4a48-a665-7c7283d1eed8)

1.2.1

This release incorporates some minor bugfixes reported by announcers, as well as some new features for the Caller Dashboard:

* in between jams, if the next jam's jammers are entered into the scoreboard, they'll show up in a table
* for the current and previous jam, each team's score is shown
* interface now indicates whether jam clock is running

1.2.0

Implemented a number of enhancements after JamStats was used for calling games at the Clover Cup.

* Added Announcer Dashboard, with current skater table and also game summary table
* Added penalty count to current skater table
* Improved handling of dropped proxy connections
* Added button on the top left to minimize and restore the left pane

Here are [instructions on setting up a proxy and connecting to a proxied scoreboard](https://github.com/dhmay/jamstats/blob/main/README.md#connecting-to-a-proxied-scoreboard-from-the-internet).

1.1.3

This release implements an enhancement to automatically try reconnecting to the scoreboard if the scoreboard connection drops. This is critical for maintaining a connection to a scoreboard running through a proxy from a bad internet connection at the track.

This is a bugfix release on top of [v1.1.2](https://github.com/dhmay/jamstats/releases/tag/v1.1.2), the original Jamstats for Remote Announcers release. [Instructions for setting up a proxy and connecting to it remotely](https://github.com/dhmay/jamstats/blob/main/README.md#connecting-to-a-proxied-scoreboard-from-the-internet) remain the same.

1.1.2

Connect to a scoreboard from anywhere on the Internet, through wsproxy!

This release adds an "ssl" argument, which supports secure Websockets connections. That allows you to connect to a scoreboard that's being proxied with [wsproxy](https://github.com/DerbyStats/wsproxy), from anywhere in the world. Great for **remote announcing**!

You can even take advantage of an existing hosted proxy service, so that all you have to do is run the proxy at your scoreboard and connect Jamstats to [live.derbystats.eu](https://live.derbystats.eu/)!

Here are [instructions on setting up a proxy and connecting to a proxied scoreboard](https://github.com/dhmay/jamstats/blob/main/README.md#connecting-to-a-proxied-scoreboard-from-the-internet).

1.1.1

This release fixes the critical Issue 130 introduced in v1.1.0. That bug broke the method that Jamstats uses to get up-to-date data from the scoreboard during a game, and also made browsing to Jamstats extremely slow, if both these conditions applied:

1. there was no connection to the Internet available
2. the laptop being used to *access* Jamstats through the browser had never done so before

It's important to upgrade to v1.1.1 in case you ever end up in that situation in the future.

Page 2 of 5

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.