Back

MagicCookie#21410 SC2 Coach Intake v0.1

SC2Pulse public-data intake for Wingent / MagicCookie. This is not replay analysis yet.

Data Read

Recent 1v1 Signal

Capability Boundary

This is profile and match-history analysis, not replay review. I can identify a strong early-game signal, but I cannot yet distinguish cheese, scout miss, greed, control failure, build-order slip, or intentional/non-game without replays.

First Coach Read

The strongest signal is not late-game macro. The games are ending too early. Start with the first 3-7 minutes: scouting, opening safety, anti-cheese response, and first tech/read correction.

Main Hypothesis

experienced multi-race player
-> current ladder losses happen before stabilization
-> repair early-game safety before reviewing midgame

Training Priority

  1. Classify early losses: cheese/all-in, scout miss, greed punished, control loss, build-order slip, non-game.
  2. First scout checklist: natural timing, gas count, tech timing, missing worker clue, early unit count.
  3. Safe ladder re-entry: one main race, one safe build per matchup, no experimental opener for 10 games.

First Assignment

10 standard 1v1 ladder games
one declared main race
save all replays
at least 7 games should reach minute 10 in playable condition

Coach Verdict

MagicCookie/Wingent is clearly experienced. Generic advice is low value. The first actionable diagnosis is that the public sample says the game is breaking too early.

Human version: this player probably does not need basic SC2 lessons. They need an early-game audit, then we can review the real midgame.