Blog & Changelog

After each finished match box-score ingest, we scrape the player profile page and expose a current rating / K-D / maps snapshot on GET /player/{id} and site player pages.

7/21/2026

Opt-in MFA for the cabinet: authenticator apps (TOTP) and WebAuthn passkeys. After email, Google, or Telegram identity, complete sign-in with a code or a passkey.

7/20/2026

Finished matches now auto-ingest per-map K/D/A box scores. Match pages show player tables; each player has a recent-maps profile page.

7/20/2026

Cabinet auth moves off localStorage Bearer tokens: httpOnly Secure cookies, silent refresh, and CSRF for cookie-authenticated writes.

7/20/2026

Match box scores land in the API: per-map K/D/A on finished games, player identity, and GET /player/{id} with recent maps.

7/20/2026

See remaining API requests in Cabinet → Usage, review 7/30-day history and per-key breakdown, configure alerts, and read X-RateLimit-* on every data API response.

7/17/2026

3 months for the price of 1 on Premium and Black, site-wide offer banner with goals, flip countdown, and cleaner pricing UX. Toggle the offer from Admin → Tariffs.

7/17/2026

Hit 429 on launch day? Free tier is 3 req/day—enough to prototype, not to poll from the browser. Cache server-side, budget requests, upgrade when logs say so.

6/25/2026

Trackers, bots, and widgets need two feeds: match results (who won, maps, scores) and fixtures (what plays next). Scraping usually means two brittle HTML parsers. GGScore is a paid CS2 match data API — both played and upcoming matches over REST, one auth model, JSON you can map to UI.

6/9/2026

Ship a Discord match tracker on GGSCore REST JSON—API key, one GET for played matches, cache and 429 handling. No HTML parsers. Free tier works for a prototype; check docs for paths and limits.

6/4/2026