Moving from Diamond to Master in StarCraft II isn't about a single tweak or a magic build — it's about sustainable, focused improvement across macro, decision-making, execution, and mindset. Over the years I’ve climbed and coached players through similar breaks, and this 6-week macro roadmap is what I’d run on myself or a student who wants efficient, measurable gains without burning out. It’s practical, daily-friendly, and rooted in real-game testing and replay-based iteration.
What I want you to commit to
This roadmap assumes you’re Diamond-level: you have basic mechanics, can execute a few builds, and understand general timings. The commitment is modest but consistent:
1.5–2.5 hours per weekday, 3–4 hours on at least one weekend day.At least 3 ladder games per practice session, with focused drills and replay reviews after each block.Open mind to change settings (hotkeys, camera, graphics) and try targeted hardware tweaks if needed.Targets I track weekly: APM trends, worker count at 6/10/12 minutes, supply block occurrences per game, average income saturation, and win rate against the matchups you most face. I recommend keeping these in a simple spreadsheet.
Core principles guiding the plan
My approach focuses on four pillars:
Macro stability: consistent worker production, injects (for Zerg), orbital/scans, and economy management.Decision cadence: knowing when to attack, defend, or tech based on scouting.Execution quality: minimising supply blocks, making efficient unit control, and hitting key timings.Feedback loop: fast replay review to turn mistakes into drills for the next day.Weekly structure (what a week looks like)
Each week has a theme. Daily sessions combine warm-up drills, focused ladder games, and a short replay analysis. Below is a template I follow; adjust durations to your schedule.
| Segment | Duration | Purpose |
|---|
| Warm-up (micro/aim) | 15–20 min | APM ramp, control group practice, splitting, kiting |
| Drill block | 20–30 min | Macro drill or build-order practice vs AI/custom |
| Ladder block | 60–90 min | 3–5 games with specific focus |
| Replay review | 20–30 min | One critical loss/win analysis |
Week 1 — Clean baseline & essential fixes
Goal: Eliminate easy leaks that lose you games — supply blocks, missed injects, poor worker production. You want a solid baseline to build on.
Drills: Play custom games vs easy AI practicing worker production only. Stop every minute and ensure you’re on constant worker production until 70–80 workers is automatic in long games.Hotkeys & UI: Simplify camera hotkeys and control groups. If your hotkeys are messy, spend a day cleaning them. I often recommend grid or hybrid binds if you’re still on default.Hardware check: Make sure mouse polling (1000Hz), DPI (400–800 for RTS), and keyboard debounce are stable. Brands I like: Logitech G series, Zowie, SteelSeries for mice; Corsair and Ducky for keyboards.Metrics: Count supply blocks per game (target ≤1). Track worker count at 6 minutes (target: Protoss 48+, Terran 45+, Zerg 60+ depending on style).Week 2 — Build-order consistency & scouting windows
Goal: Learn one or two reliable builds per matchup and master the scouting that informs mid-game choices.
Pick a main build for each matchup (e.g., Terran 1/1/1, Protoss Stargate expand, Zerg 3-base ling/bane macro). Practice it in custom games until you hit the key timings consistently.Scouting drills: Play 5 games where your primary focus is the scout timing — did you see gas down, early tech, or a third? Pause replays at the scout time and note how that changes your plan.Replay note: Create a short log of “what scout I saw → how I reacted → was it correct?” This trains the decision mapping between information and action.Week 3 — Macro under pressure & multitasking
Goal: Practice keeping your economy healthy while handling harass or drops.
Drills: Use the “dual task” custom scenario or practice vs aggressive bot builds. Force yourself to build workers and infrastructures while microing defense.Split sessions: 30 minutes of ladder games focusing on avoiding worker losses and maintaining saturation under harassment.Metrics: Track average workers lost to harass per game (target: minimize but accept occasional losses if trade/serviceable).Week 4 — Transitions and tech timing
Goal: Make transitions smooth — recognizing the right time to tech up, add production, or shift army composition.
Study 3 pro replays of your race’s popular transitional timings (mutalisks timing, 2-2 timing, charge transition). Pause and write down exact supply/tech states at the transition moment.Drills: Start a game with a planned transition at a given minute: e.g., “At 6:30 I start +1 and 3rd base; at 8:00 I add extra factories/4th gate/tech lab.” Hit that rhythm.Replay focus: For each loss, ask ‘did I transition too late/early?’ and mark it. These are the highest ROI errors.Week 5 — Midgame decision-making & mid-late timing attacks
Goal: Know when to take a fight and when to reset. This is where macro converts into wins.
Drills: Play games where you intentionally delay an attack for 30–60 seconds to get more units or better upgrades. Learn the incremental power of one more medivac, one more colossus, or a +1 timing.Map control: Practice vision points — watch professional games and note what watchtowers/risks they value. Push for incremental map control instead of all-in mindsets.Replay checklist: For each successful midgame fight, record the supply, upgrade lead, and concave/positioning that won the fight. Replicate it.Week 6 — Polish, ladder focus, and psychological prep
Goal: Convert practice into consistent ladder performance with mental resilience.
Play concentrated ladder sessions with a 1-win/1-loss cooldown. After a loss, do a 10–15 minute targeted drill before the next game (e.g., worker production or injects).Mental drills: Short breathing routine between games, and a note of one tactical takeaway from the last match. Avoid tilt by limiting consecutive games to 3–4 before a longer break.Hardware & ergonomics: Ensure your monitor refresh rate is optimal (144Hz+ if possible), game settings favour clarity (low input lag, crisp unit outlines). These small comfort improvements scale across sessions.Replay review template I use
Use this for each critical loss:
Time stamp of decisive mistakes (e.g., 7:12 lost all workers to drop).Root cause (e.g., no scan, no oversights in patrol path, mis-timed production).Fix for next session (drill, hotkey change, build variation).Common hurdles and quick fixes
Stagnant win rate despite practice: You’re likely reinforcing bad habits. Do a week of strict replay-based corrections where you refuse to play more than one ladder run until you fix the chief leak.APM plateau: Lower your focus to quality actions. Remove meaningless actions with the “meaningful APM” exercise — play five minutes trying to maintain only useful keystrokes/clicks (build, attack, camera jumps).Burnout: Cut sessions to one focused hour and do only replay analysis for a few days. Mental rest accelerates learning as much as repetition.Stick to the six-week rhythm, but be flexible — if a particular week’s theme uncovers more issues, extend it until you’ve fixed the leak. The goal isn’t to blindly grind hours, but to build a reproducible system: reliable macro, informed decisions, clean execution, and quick replay adjustments. If you want, I can give you a downloadable spreadsheet template for tracking your metrics and a sample hotkey layout I use — say the word and I’ll share them.