Brood War / BGH / Duoduo autosave coaching package. Source: `duoduoduo-2026-06-03.rar`.
Duoduo Brood War Coaching Package
This package parsed 15,411 BGH/Hunters replay candidates, identified 12,196 main-alias games, and selected 10 representative replays for battle-report style review.
Coach Read
Duoduo is a Zerg engine. The sample is huge, the identity is clear, and the action quality is high: 192 / 158 average APM/EAPM over the main-alias sample. The strongest pattern is early Zerg tempo: speed, ling floods, Muta/Hydra pivots, and enough comfort to start fights instead of waiting. The repair lane is not “play faster.” It is second-phase choice and finish discipline: when the first pressure does not kill, the next plan must be declared before the game becomes busy but unresolved.
Profile
duoduoduo, duoduoduoduo, and [24H]duoduo.
6,313 wins / 5,013 losses. 870 unknown results excluded from rate.
Average APM / EAPM. This is a strong effective-action ratio, especially for BGH Zerg.
Zerg 9,483; Protoss 1,459; Terran 1,254. Zerg is the main weapon, not a side pick.
Training Priorities
| Priority | Issue | Training Method |
|---|---|---|
| 1 | First-phase Zerg pressure is strong, but not every pressure game becomes a clean finish. | At 8-10 minutes, force one second-phase call: Lurker contain, Defiler front, Muta extension, Hydra bust, drop cut, or air switch. |
| 2 | High activity can hide unclear team targeting. Duoduo can be very busy while the team has no single finish point. | At 12 and 16 minutes, ping one team target: break front, kill tech, defend drop, or collapse one side. No “just keep fighting” calls. |
| 3 | Protoss has a solid opening shell but needs a clearer midgame role once Templar tech arrives. | For every Protoss replay, write the role at 10-12 minutes: storm support, Archon front, Dragoon range control, or defensive anchor. |
| 4 | Terran games split between structured terrain wins and active-but-not-decisive losses. | Review Terran by terrain: first tank line, scan plan, rally path, and next tile. Vultures or M&M only matter if they buy map space. |
10 Representative Replay Reads
1. 2021-12-02 | duoduoduoduo Zerg | 10:26 Win
This is the clean “Duoduo engine” sample. Overlord at 0:58, Pool at 1:20, Extractor at 1:46, Zergling flow from 2:14, Speed at 2:39, Sunken at 2:56, second Hatchery at 3:07, then continuous ling production into Hydralisk Den at 9:16. The game ends at 10:26, so the early pressure did its job before the opponent could build a comfortable late-game wall.
Coach point: This is the baseline strength. Keep the early tempo, but do not let every win condition be “more lings.” If the game survives past 8 minutes, choose the second tool immediately.
2. 2021-12-02 | duoduoduoduo Zerg | 10:26 Loss
The opening is similar but slightly greedier: Pool at 1:31, Extractor at 1:42, Hatchery at 2:11, Speed at 2:45, extra Hatcheries around 3:24, then constant Zerglings and late defensive Creep/Sunken around 7-8 minutes. The activity is high, but the game is lost at the same 10-minute mark. That usually means the pressure was answered and the defensive reaction arrived after the team position was already damaged.
Coach point: In short Zerg losses, review the first three minutes of map contact. Was the Hatchery choice buying pressure, or did it delay the emergency defense?
3. 2021-11-29 | duoduoduoduo Zerg | 18:40 Win
This is a strong phased Zerg game: Pool at 1:20, Hatchery at 2:26, Speed around 2:50, Sunken at 3:15, Lair at 5:59, Spire at 7:07, Mutalisks from 8:28. It shows the best version of the style: early ground pressure does not stay one-dimensional. It becomes air, and the air gives the team a second map problem to solve.
Coach point: This is the replay to copy. The first phase creates pressure; the second phase changes the fight shape. That is Duoduo’s best Zerg formula.
4. 2021-12-13 | duoduoduoduo Zerg | 35:19 Loss
Pool at 1:32, Hatchery at 2:04, Extractor at 2:07, Speed at 3:27, Lair around 6:16, Spire at 7:26, Mutalisks before 9 minutes. The early and midgame structure is fine. The problem is the 35-minute result: the Zerg plan survived but did not mature into a decisive late-game layer. Against double Protoss style pressure, Muta activity alone eventually stops being enough.
Coach point: Long Zerg losses should be reviewed at 14-20 minutes, not only the opener. Ask: where was the Defiler, Lurker contain, drop threat, or air switch?
5. 2023-11-05 | duoduoduo Zerg | 27:08 Win
This win uses pressure and tech patience. Pool at 1:17, Extractor at 1:22, Speed at 2:23, Hatcheries at 2:55 and 3:45, Sunken around 5:47, Hydralisk Den at 8:10, Lair at 9:02. The enemy team is triple Protoss, so the game asks for disciplined ground pressure and anti-spell shape. Duoduo does not need to kill instantly; he builds the Zerg body that lets the team stay active into the long game.
Coach point: Good long-win sample. When facing Protoss stacks, earlier Hydralisk/Lurker/Defiler planning matters more than pure ling excitement.
6. 2023-11-01 | duoduoduo Zerg | 17:07 Loss
This is a defensive Hydra loss: Pool 1:35, Hatchery 2:10, Speed 2:44, several Creep/Sunken layers, Hydralisk Den at 5:22, Hydralisk speed/range around 6-7 minutes, Lair at 8:24. The structure is active, but it reads like the Zerg was forced into holding shape while the opposing Protoss side gained spell and positional value.
Coach point: Hydra defense is not enough by itself. If you are spending on Sunken + Hydra, the next question is what it buys: Lurker, Defiler, or a coordinated ally timing.
7. 2026-06-01 | duoduoduo Zerg | 13:38 Win
This is the modern fast-air version. Pool 1:17, Extractor 1:23, Lair 2:23, Spire 3:30, Mutalisks from 4:57, Scourge by 7:35, Flyer Carapace around 9:30, then more Muta production. The timing is sharp and very readable: get air fast, force reactions, and keep the opponent from playing a clean ground game.
Coach point: Strong recent sample. The next improvement is target discipline: fast air should have one declared job, either worker damage, tech denial, drop defense, or forcing the front to move.
8. 2026-05-31 | duoduoduo Protoss | 21:34 Loss
The Protoss shell is real: Pylon 0:50, double Gateway by 1:46, Zealots from 2:01, third Gateway at 2:53, Forge 4:04, Cyber Core 4:29, Cannon 4:39, Citadel 6:08, Templar Archives 7:38, Zealot Speed around 8:08. This is not a bad opener. The loss points at midgame role: after the tech arrives, what is Duoduo’s job in the 3v3?
Coach point: Protoss is playable, but it needs a role sentence after Templar Archives: storm support, Archon front, range control, or defensive anchor.
9. 2026-05-23 | duoduoduo Terran | 41:38 Win
This is the structured Terran win. Depot 0:56, Barracks 1:27, Refinery 1:53, Factory 2:52, second Factory 3:23, Vultures from 3:53, Mines/Speed around 5 minutes, Siege Mode by 7:26, Armory at 7:56. The APM is lower than Duoduo’s Zerg, but the plan is more terrain-based. This is how Terran should look: Vulture space first, then tank technology turns space into map control.
Coach point: Terran does not need Zerg-level speed. It needs sequence discipline: Vulture space, tank line, scan/rally, next tile.
10. 2026-05-15 | duoduoduo Terran | 34:24 Loss
This loss uses a different Terran shape: double Barracks by 1:53, Academy 2:55, Stim 4:16, ComSat 4:30, Range 5:13, Factory 5:53, Siege Mode around 7:24, Starport 7:10. The tech exists, but it arrives after a bio-heavy opening. Against a high-activity Zerg/Protoss/Terran enemy side, the Terran plan must avoid becoming “M&M first, terrain later.”
Coach point: If playing Terran in BGH, decide early whether you are bio pressure or terrain anchor. Mixing both without a clear first tank line can make the whole game reactive.
30-Day Plan
| Week | Theme | Completion Standard |
|---|---|---|
| 1 | Zerg second-phase discipline | After every Zerg game, write the 8-10 minute second task: Muta extension, Lurker contain, Hydra bust, Defiler front, drop cut, or air switch. |
| 2 | Finish call timing | At 12 and 16 minutes, make one team call. If there is no call, the review counts it as a missed decision even if APM was high. |
| 3 | Protoss role sentence | Every Protoss game needs a 10-12 minute role: storm, Archon, range control, defense, or timing finish. |
| 4 | Terran terrain language | Review the first tank line in every Terran game: safe tile, scan, rally, and next tile. No terrain, no Terran plan. |