HearthStats released hearthssgaming updates from hearthstats in 2026. The team added tracking, analytics, and sharing tools. Players will see clearer match history. Deckbuilders will see improved win-rate tables. Streamers will see new overlay options. This article lists the main changes, explains their impact, and shows simple steps to use the new features.
Key Takeaways
- Hearthssgaming updates from HearthStats introduce session tracking and detailed per-card play rates to enhance player insights.
- The update provides deckbuilders with improved win-rate tables and public deck-sharing features for faster iteration and collaboration.
- Streamers benefit from new live overlays and compact scoreboards that display current win rates and opponent classes while preserving privacy.
- Enhanced analytics visuals like sparkline charts and heat maps offer analysts powerful tools to monitor meta trends and mulligan choices.
- Users gain granular privacy controls, including anonymizing opponent names and role-based access for team accounts.
- Developers have access to comprehensive API documentation and example scripts to integrate HearthStats features efficiently.
Key Updates Rolled Out By HearthStats
HearthStats published a major release called hearthssgaming updates from hearthstats. The update adds session tracking that logs each game start and end. The update adds per-card play rates for each match. The update adds a new API endpoint that returns player aggregates. The update adds a public deck-sharing page with tags and comments.
HearthStats updated the match import process. The system now flags mismatched game versions and prompts users to confirm. The system now assigns a unique session ID to every run. The system now stores match timestamps in UTC and local time, which helps cross-region analysis.
HearthStats changed analytics visuals. The update adds sparkline charts for trend view. The update adds heat maps for mulligan choices. The update adds a table view for aggregate mulligan win rates. The update adds a new CSV export layout that matches third-party tools.
HearthStats improved streamer tools. The update adds a live overlay widget that shows active deck, opponent class, and current win rate. The update adds a compact scoreboard for OBS with SVG and PNG options. The update adds throttled API calls to avoid rate limits during high-traffic streams.
HearthStats added user controls. The update adds granular privacy settings to hide match lists. The update adds an option to anonymize opponent names for public shares. The update adds role-based access for team accounts. The update adds an approval queue for shared deck submissions.
HearthStats published developer docs. The update adds Swagger-style documentation for the new API calls. The update adds example scripts in Python and JavaScript. The update adds a rate-limit guide and code samples for client-side caching.
What The Changes Mean For Players, Deckbuilders, And Streamers
Players will gain clearer feedback from hearthssgaming updates from hearthstats. Players will see exact timestamps and session IDs for every match. Players will use per-card play rates to adjust mulligans. Players will export filtered CSV files to run offline analysis.
Deckbuilders will get faster iteration from hearthssgaming updates from hearthstats. Deckbuilders will compare win rates by version and ladder rank. Deckbuilders will test small card swaps and see immediate changes in play-rate and win-rate tables. Deckbuilders will share a public deck link with tags and gather comments from other builders.
Streamers will get smoother overlays from hearthssgaming updates from hearthstats. Streamers will add the live widget to their scene. Streamers will show viewers current win rate and opponent class without revealing names. Streamers will avoid API throttling through the new client-side caching examples.
Teams and content creators will benefit from role-based features in hearthssgaming updates from hearthstats. Teams will control who can publish shared decks. Teams will use approval queues to vet deck lists before public posting. Teams will use anonymize options to protect test accounts during public sessions.
Analysts will find new signals in hearthssgaming updates from hearthstats. Analysts will use heat maps to study mulligan choices. Analysts will use sparkline trends to spot meta shifts. Analysts will pull the new API aggregates to build custom dashboards.
Casual users will see less noise after hearthssgaming updates from hearthstats. Casual users will hide match lists when they share a deck link. Casual users will access simplified export files for spreadsheets.
How To Apply The New Features: Step‑By‑Step Tips And Best Practices
Install the latest HearthStats client. The app will prompt for an update when it starts. Users can also download the update from the account page.
Enable session tracking. Open Settings, toggle Session Tracking on, and click Save. The client will attach a session ID to every match. Users can view session IDs in match details.
Use the new API. Developers should read the Swagger docs under the API section. Developers should generate an API key from Account > API Keys. Developers should test calls in the provided Postman collection before deploying code.
Export targeted CSV files. Open Matches, apply a filter for rank and date, and select Export > CSV (Compact). The export will match the new column order. Analysts should load this CSV into a spreadsheet and run pivot tables on card play rates.
Add the live overlay to a stream. Go to Stream Tools, copy the Overlay URL, and add it as a Browser Source in OBS. Set the width to 1280 and the height to 200 for a compact display. Toggle the anonymize option if the streamer wants to hide opponent names.
Share a deck publicly. Open Decks, select a deck, and click Share. Add tags and a short note. Send the link to playtesters or paste it in social channels. Use the approval queue for team decks to keep quality high.
Use privacy settings. Go to Account > Privacy and set Match Visibility to Private or Team. Enable Anonymize Opponents to strip names from public shares. Review role assignments under Team Settings to limit who can publish.
Follow rate-limit best practices. Cache API responses on the client. Batch requests when possible. Respect the documented per-minute limits to avoid temporary blocks.
Monitor changes. Check the Release Notes page weekly. Subscribe to the HearthStats changelog to get alerts about patches and bug fixes. Apply small changes to workflows and measure the impact with a few sessions before large shifts.
