@Tr33Fr0g

ADDED THE DUCK ATTACK AND WADDLING AND EVERYTHING IS WORKING NOW THAT TOOK WAY LONGER THAN IT SHOULD’VE!!

Fixed the posture tracking, a couple syntax errors, and just basic things i forgot to add correctly.

Added webcam access and a few other small things also fixed like 50 other things ngl

“Created the bare bones HTML screen and file directory”

Fixed security issues with the api key and vercel issues. that took so long for no reason but now it wont take like 8 years to load anymore!

Added a short line that makes it so that I could change the date on the calendar and it’d update. Also did a bit of bug fixing. Changed the clicking function thing to be a bit better looking.

Added the Nasa apod api data and made it fetch the picture and statement of the day based on the calendar. the code checks for a successful repsonse and then updates the page by parsing the data into a readable JSON object.

Added hidden .loading, .error, and .content and made the interface viewable on mobile devices. Btw css sucks bro takes 100 years to just write the same repetitive code it feels like it took years and it was only like 20 minutes. VS code extension is the best for colour picking. (nothing looks like it changed cause its all display=none)

Added basic initial HTML stuff and the style.css

Finished the final part added a new player comparison feature that attempts to pull stats from the current session then from saved JSON files if not found, does the math for analytics for both players, and displays a formatted side-by-side table with arrow indicators showing who leads in each category using cool arrows!

Project Overview
Goals and motivation
In this project I’m building a menu driven CLI that records a volleyball players performance, calculates analytics like hitting percentage, kill efficiency, and serve efficeincy, and persists stat sheets and JSON files and connects them to a live sports API for professional league to learn basics of GIt and Github, JSON save/load systems, API’s and command-line tools

Devlog 1. Building the Stat Recorder
Stat categories and input validation
My stat tracker now records kills, errors, attempts, aces, digs, blocks, and sets played. The special rule for sets_played is that it cannot be less than 1 since it’s a special stat.

Devlog 2. Calculating Volleyball Analytics
What this step accomplishes
In this next step, I’m building a function to turn regular stats into more readable and relevant volleyball stats
Understanding hitting percentage
A hitting percentage of .350 means the player is amazing because the formula calculates all players averages and classifies them ex: 20 kills and 50 errors would be a 0.4 hitting percentage 0.400 would be classified as amazing.

Devlog 3/4. Saving and Loading Stat Sheets
In this step, I’m setting up JSON saving and loading stat sheets so that I can optimally save and load stats for each player.

Devlog 5. What this step accomplishes
In this step, I’m connecting to the Highlightly API so that I can get live data from professional volleyball teams and league standings. This way I can also learn about API development my code now calls the Highlightly teams endpoint with the header x-rapidapi.