BGH Group Batch Coach Report v0.2
Date: 2026-06-02
Update: added Jun's broader replay aliases:
Dimsumsum[STA]PurE)Rabbit-SFUncleTiger[24H]UncleTiger
Corrected Sample
The BGH replay count remains 433.
After alias expansion, Jun-related samples increase from 57 games to 362 games.
PurE)Rabbit-SF is the largest main sample:
301appearances- almost random-race distribution:
- Terran
99 - Protoss
101 - Zerg
101 - around
108W-163Lamong decidable results, with some unknown/remake/drop noise
After removing ultra-short remake/drop games, Jun aliases have 327 meaningful-length samples.
Meaningful samples by race:
| Race | Wins | Losses | Unknown | Avg APM/EAPM | First read |
|---|---|---|---|---|---|
| Protoss | 53 | 55 | 4 | 225 / 180 | closest to stable baseline |
| Zerg | 43 | 60 | 4 | 233 / 179 | active, but not converting enough |
| Terran | 33 | 65 | 10 | 229 / 184 | first repair target |
Corrected First Read
The previous report only saw Dimsumsum[STA], which undercounted the real sample and overestimated Zerg.
After including PurE)Rabbit-SF / UncleTiger, the read changes:
- Jun is a long-term random/multi-race BGH player.
- APM/EAPM is high enough across all races; speed is not the first issue.
- Terran is the clearest weakness.
- Protoss is the best baseline race to stabilize first.
- Zerg has activity, but needs a conversion review.
Priority 1: Make Protoss The Baseline
Protoss is nearly even at 53W-55L-4U.
That makes it the best first coaching baseline:
- BGH Protoss responsibilities are clear.
- Pylon/Gateway/Forge/Cannon shape is rubric-friendly.
- Zealot/Dragoon/Templar transition is easy to compare between wins and losses.
- It is easier to validate whether Protoss became front-line defense, side pressure, or late-game core.
Training rule:
In every Protoss BGH game, define your role first: front defense, side pressure, or late-game core.
Review questions:
- Was my spawn front-line or back-line?
- Did my first Pylon/Gateway/Forge/Cannon shape serve the team defense?
- Did my first Zealot/Dragoon movement protect an ally, pressure an enemy, or wander without purpose?
- Did I become a team core by midgame?
Priority 2: Terran Is The Repair Lane
Terran is the clearest weak sample: 33W-65L-10U.
The mechanical baseline is not low: around 229 / 184 APM/EAPM.
The likely issue is that Terran activity is not reliably converting into BGH team value:
- early buildings may be busy but not defending the shared entrance
- Marines/Bunkers/Depots may exist but fail to stop the first timing
- tech may be personal instead of team-timed
- the player may be busy while an ally side collapses
Terran target:
Prove team value before 6-8 minutes.
Review standard:
- Did I create defense that protected an ally?
- Did my first army force a real enemy response?
- Did my tech choice match team need?
- Was I front-line, support, or greedy back-line?
Priority 3: Zerg Is A Conversion Problem
Zerg is 43W-60L-4U with around 233 / 179 APM/EAPM.
This is not slow Zerg. It is a conversion question:
Did the first Zerg activity actually change the team game?
Zerg review should check:
- early units that do not create pressure
- fighting small when the correct move is economy
- staying local when an ally needs rescue
- random-race habit causing unclear Zerg objectives
Training target:
In every Zerg game, identify whether the first unit wave changed the team position.
Product Direction
This corpus is enough to start a real BGH coach.
The coach can already produce:
- alias-aware player identity
- small-circle player frequency
- race distribution
- result structure
- APM/EAPM baseline
- spawn/team/mode context
- deep-dive replay candidates
The next product is not generic Brood War AI.
It is:
WeChat BGH group match report + coaching system
Core loop:
- Upload a replay batch.
- Detect group aliases.
- Produce player profiles.
- Identify strong/weak races.
- Select the top 3 review candidates.
- Give friend-readable coaching advice.
Immediate Next Deep Dives
Terran repair:
- meaningful Terran losses around 6-12 minutes
- high APM/EAPM but losing game state
- prioritize common losing starts such as 5/6/10/11/12
Protoss baseline:
- choose 3 Protoss wins
- choose 3 Protoss losses
- compare wall/defense, first army movement, and midgame core conversion
Zerg conversion:
- choose high-APM Zerg losses
- check whether first unit wave changed the team state
- check whether ally rescue or economy timing was missed
Coach Verdict
With aliases corrected, the conclusion is stronger:
Jun already has a long-term multi-race BGH corpus.
The first AI coach should:
- unify
PurE)Rabbit-SF / Dimsumsum[STA] / UncleTigeridentity - use Protoss as the stable baseline
- treat Terran as the first repair lane
- investigate Zerg conversion separately
Human version:
You do not lack speed. You have played too much random-race BGH, and Terran team value is not consistently converting. Build the baseline with Protoss, repair Terran, then inspect why Zerg activity is not winning more.