Mistake → Macro Impact Map

Visualizing the butterfly effect of defeat. We map micro-errors to round losses, showing players exactly how one untraded death cascades into a lost game.

Comment

💡 Inspiration

We've all been there. You hold an angle, you get timing'd, you die. Your teammate says "unlucky". But was it? We realized that most players view CS/Valorant as a series of gunfights, but high-level play is a game of probability and control. We wanted to build a tool that stops players from saying "my bad" and starts showing them the actual cost of their mistake. We wanted to verify the invisible: how a single death at 1:45 destroys the economy at 0:30.

🦋 What it does

Mistake → Macro Impact Map is a causality engine. It doesn't just tell you that you died; it visualizes the nightmare you initiated.

  1. Impact Cascade: Shows the chain reaction from a micro-error (e.g., untraded death) to the strategic collapse (loss of map control, forced rotation, eco loss).
  2. Tactical Correction: Provides a prescriptive "fix" for the specific error, acting as an automated coach.
  3. Visualized Cost: We map the "Hidden Cost" in terms of economy tier drops and map control percentages.

⚙️ How we built it

We built this to be fast, beautiful, and responsive—just like the esports titles we analyze.

  • Runtime: Powered by Bun for blazing fast dev server start-ups and testing.
  • Frontend: Built with React 19 and Vite 7 for immediate UI feedback.
  • Styling: We used Tailwind CSS 4 with OKLCH colors to create a "Dark Mode" aesthetic that feels right at home on a second monitor next to a gaming setup.
  • Data: Mocked match data is processed through our custom TypeScript analysis engine (analyze-match.ts) to simulate the "Impact Score" algorithm.

🚧 Challenges we ran into

Defining "Impact" is hard. K/D/A is easy to calculate, but how do you calculate the "cost" of losing mid control? We had to create a heuristic model that assigns "Impact Scores" based on when and where a mistake happened, not just the result. Balancing this logic while keeping the UI clean and "gamified" was our biggest design challenge.

🏆 Accomplishments that we're proud of

We are incredibly proud of the UI/UX. We didn't want a spreadsheet; we wanted a command center. The result is an interface that feels "premium" and authoritative. We're also proud of the Impact Cascade visualization—seeing the timeline of failure is a powerful wake-up call for any player.

🧠 What we learned

We learned that "Macro" is just the sum of "Micros". By building this, we realized that coaching isn't about telling people what to do; it's about showing them what they did and letting the data scream the consequences.

🚀 What's next for Mistake → Macro Impact Map

  • Real Data Integration: Hooking into the GRID Data API/Live Parser to analyze live scrims.
  • Team View: Allowing IGLs (In-Game Leaders) to see the cumulative impact of their teammates' errors.
  • AI Coach Persona: Integrating an LLM (via Junie?) to "roast" or "encourage" the player based on the severity of the mistake.

Built With

Share this project:

Updates