Flashback Challenges

Challenges are time-limited events where users compete on CS2 performance metrics and win prizes. They are organized by Flashback today and are planned to become self-serve for approved Community Leaders.

This section is the canonical source of truth for the feature. It is written for both humans and agents.

Read first

• Product plan — Community Leader MVP scope, scoring, payments, release-ready definition, and backlog.
• Architecture — system map, file map, data flow, scoreboard sources, and persistence model.
• Debugging — production triage, live queries, common failure modes, and operational checks.
• Change checklist — rules to follow before editing challenge code.
• Technical debt — accepted MVP compromises and intended follow-ups.

Code ownership map

• Flashback UI: src/app/challenges/*
• Flashback API: src/app/api/v1/challenges/*
• FACEIT sync: src/app/api/v1/cron/faceit-match-sync/route.ts
• Analytics: src/lib/challenges/challenge-analytics.server.ts
• Demo pipeline contracts: ../demo-pipeline/contracts/queues.md

Maintenance rule

When changing challenge architecture, data flow, operational behavior, debugging knowledge, product behavior, release criteria, or accepted debt, update these wiki pages in Gamesense.

Agents should load this section through the Gamesense MCP tools before changing challenge code. If Gamesense cannot be reached, they should warn the human clearly before continuing.