What you get
Single demo & multi-demo analysis
- Drop one demo for a full match review: tick-by-tick radar, live scoreboard, and sidebar deep-dives.
- Drop several demos for habits analysis: same-map or mixed-map series, focal team filters, buy-type buckets (pistol / eco / force / full), and an aggregated overlay of paths, trails, and heat.
- Parse in the browser (Web Worker + WASM) — large GOTV files stay local; nothing is uploaded.
Radar replay
- 2D overview with players, yaw, loadouts, floors (upper / lower where the map has them).
- Grenades, shot tracers, deaths, openings, names, view cones, heat, and nade summaries — toggle layers as you like.
- Freeze countdown, C4 / defuse timers, live clutch banner, kill feed, and spectator economy.
- Playback: scrub, speeds, skip freeze, round autoplay, keyboard hotkeys, and a round strip with event marks.
Scoreboard & player detail
- FACEIT-style live board through the current tick: K/D/A, ADR, KAST, rating, entry, money, CT/T splits.
- Side swaps and overtime scored the way you expect from competitive matches.
- Per-player detail: trades, flashes, utility damage, clutches (1v1–1v5 W/A), multikills, plants / defuses.
- Export a full-match stats CSV from the header (handy for spreadsheets and rating experiments).
Review, Action & Utility
- Review — openings, clutches, and mistake-style moments you can jump straight into.
- Action — round story, executes, plants, retakes, and fights with site / callout labels.
- Utility — every throw by kind and place; filter by match or selected player; series mode adds frequency and first-wave util sets.
- Rounds — expandable event timeline with configurable lead-in.
- Weapons — kill breakdown for the current window or the whole game.
Notes & drawings
- Draw on the radar: pen, arrow, text, bookmarks; undo / redo; color palettes; moment-timed strokes.
- Layers, clocks, groups, and round-scoped visibility.
- Notes auto-save in the browser; export / import JSON backups from Settings; re-link a demo to restore drawings with the match.
Callout layouts (development)
- In
npm run dev / ./scripts/run.sh --dev, Settings → Layouts editor lets you draw map callout polygons used by Action and Utility labels.
- Editor is not shipped in production builds.
Run it locally
Everything goes through scripts/run.sh:
| Flag | What it does |
|---|
--prepare | Install Rust toolchain, wasm-bindgen-cli, and npm deps |
--fetch-demos | Download test demos listed in test-demos/manifest.json into test-demos/files/ (skip when sha256 matches). Every pull request and push to master runs the Real demos check; the ignored release tests run only when crates, Cargo.toml, Cargo.lock, the manifest, test-demos/output-hashes/**, scripts/run.sh, or that workflow changed. A cached demo dir is still sha256-checked. |
--update | Update Rust and npm deps within current semver ranges, keep wasm-bindgen pinned to the CLI, rebuild WASM, and run tests. Does not commit. |
--upgrade | Bump Rust and npm deps to the newest peer-compatible versions, including outside current semver ranges. Skips the =0.5.10 source2-demo pin, every wasm-bindgen* crate, js-sys, and web-sys. Rebuilds WASM, runs tests, then the production build. Does not commit. Restores the dependency tree on failure. |
--latest | With --upgrade only. Take the newest versions even when they break peer dependencies. |
--build-wasm | Compile the parser WASM into the web app |
--check | rustfmt, clippy, prettier, eslint, typecheck |
--test | Rust + web test suites |
--dev | Dev server at http://localhost:5173/ (layouts editor at /layouts) |
--prod | Production build + preview (default http://localhost:4173/) |
--update and --upgrade need a clean dependency tree: every workspace Cargo.toml, Cargo.lock, apps/web/package.json, apps/web/package-lock.json, and apps/web/src/parser/. Commit or stash those first. The two flags are mutually exclusive.
--upgrade
--update stays inside the ranges already written in the manifests. --upgrade rewrites those ranges to the newest published versions that still satisfy peer dependencies (npm-check-updates --peer), refreshes the lockfiles, rebuilds WASM, and runs the Rust tests, the web tests, and npm run build (the production prerender). It prints a table of resolved version changes and leaves the diff in the working tree. It does not commit.
--upgrade --latest drops --peer and takes the newest versions even when another package's peer range cannot accept them. --latest on its own is an error.
If a step fails after files have changed, or the run is interrupted with Ctrl-C or SIGTERM, the script puts every workspace Cargo.toml, Cargo.lock, apps/web/package.json, apps/web/package-lock.json, and apps/web/src/parser/ back to the pre-run state, runs npm ci in apps/web so node_modules matches that lock, and does that restore only once. A failed step names the step and exits non-zero. Ctrl-C exits 130 and SIGTERM exits 143. If npm ci fails, it tells you to run that command manually and does not try again. A second interrupt during that restore leaves whatever was already restored in place and prints once: check git status, then run npm ci in apps/web.
Not a CI step. On success, review git diff and commit the bumps you want to keep.
Requires cargo-edit (cargo install cargo-edit). npm packages are bumped with npx npm-check-updates@22 (no global install). Major 23 rejects Node 24.11 (^24.15.0); major 22 accepts >=24.
Left unchanged:
This is the beginning of the README. Read the rest at the original. Read the full README ↗
