gitwtfhub

wtf is hots-party-stats?

daniellav/hots-party-stats — explained in plain English

Analysis updated 2026-05-18

3JavaScriptAudience · generalComplexity · 3/5Setup · moderate

TL;DR

A tool that reads your local Heroes of the Storm replay files and builds a win-rate dashboard for a regular group of teammates, split by map, hero, and game mode.

Mindmap

mindmap
  root((HotS Party Stats))
    What it does
      Parse replay files
      Build win rate dashboard
      Track group games
    Tech stack
      Python
      heroprotocol
      Docker
    Use cases
      Group win rate tracking
      Merge teammate stats
      Fearless draft tracker
    Setup
      Configure GROUP names
      Run parse_replays.py
      Open dashboard.html
    Audience
      Gamers
      Regular team groups

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Why would anyone build with this?

REASON 1

Track win rates, hero picks, and team compositions for a regular Heroes of the Storm group.

REASON 2

Merge replay stats from multiple teammates into a single shared dashboard.

REASON 3

Run a live Fearless Draft tracker for a real-time series where heroes cannot repeat.

What's in the stack?

PythonJavaScriptDockerFlaskNginx

How it stacks up

daniellav/hots-party-statsabhagsain/bayut-maps-ratingsabhishek-kumar09/who-is-imposter
Stars333
LanguageJavaScriptJavaScriptJavaScript
Last pushed2021-04-12
MaintenanceDormant
Setup difficultymoderatemoderateeasy
Complexity3/52/53/5
Audiencegeneralgeneralgeneral

Figures from each repo's GitHub metadata at analysis time.

How do you spin it up?

Difficulty · moderate Time to first run · 30min

Requires Python 3.9+, a virtual environment, and editing config.py with your group's battletags before first use.

Wtf does this do

This project turns your local replay files from Heroes of the Storm, a team based video game, into a dashboard showing win rates and statistics for you and your regular group of teammates. It looks specifically at games where several named members of your group played on the same team, automatically filtering out solo matches or games with random strangers, though it can be set up to track solo play instead if that is what someone prefers. To use it, a person needs Python installed on a Windows or Mac computer, along with a specific library that Blizzard, the maker of the game, provides for reading replay files. The setup process involves cloning the project, creating an isolated Python environment, and installing the required packages, all done through the command line. Before running anything, the user must edit a configuration file to list the battletags, the in-game usernames, of everyone in their group, along with optional nicer display names and any alternate accounts that should be counted as the same person. The tool comes with placeholder example data so the dashboard can be tried out immediately before anyone plugs in their real group. Once configured, two scripts do the work: one scans every local replay file and writes the results to spreadsheet style data files, and the second reads those files and generates a single self-contained webpage showing the dashboard. That webpage can simply be opened by double-clicking it, no separate web server needed for most of its features. The dashboard includes several tabs covering overall stats, awards, hero talent choices, and graphs, plus a special Fearless mode inspired by competitive drafting rules, where a hero cannot be picked twice across a real-time series of games. That one feature does need a small server running locally or online so that hero picks stay in sync for everyone watching the same series live. Because the tool always determines a group's "team" the same way regardless of who runs it, teammates can each generate their own data and merge it together safely, building a shared history of games without anyone's results overwriting another's.

Yoink these prompts

Prompt 1
Help me configure hots_lib/config.py with my group's battletags and MIN_KNOWN setting.
Prompt 2
Walk me through running parse_replays.py and build_dashboard.py to generate my HotS stats dashboard.
Prompt 3
Explain how this tool merges replay data from multiple teammates without overwriting anyone's games.
Prompt 4
Show me how to run the Fearless tab locally using dev/run.sh and Docker.

Frequently asked questions

wtf is hots-party-stats?

A tool that reads your local Heroes of the Storm replay files and builds a win-rate dashboard for a regular group of teammates, split by map, hero, and game mode.

What language is hots-party-stats written in?

Mainly JavaScript. The stack also includes Python, JavaScript, Docker.

How hard is hots-party-stats to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is hots-party-stats for?

Mainly general.

View the repo → Decode another repo

This repo across BitVibe Labs

Don't trust strangers blindly. Verify against the repo.