BGH 3v3 AutoSave community coach report: 925 clear 3v3 games, BeibeiQ focus, meaningful player profiles.

BGH 3v3 AutoSave Community Coach Report v0.1

Focus player: BeibeiQ

Report date: 2026-06-03

Source: local AutoSave.zip replay pack shared for the 24HSC Brood War BGH community.

Parser: local screp plus BroodWar-AI-Coach/tools/bgh_batch_report.py.

Privacy boundary: this report uses replay header data, map names, player names, race, team, winner, APM/EAPM, game length, and BeibeiQ command-level aggregates. It does not quote chat and does not publish raw replay contents.

Sample Scope

The zip contained 4,884 .rep files.

BGH / Big Game Hunters / Hunters name matches: 1,771 replays.

The core sample was narrowed to clear 3v3 games:

• 6 human players
• two teams of 3
• parsed winner available
• BGH/Hunters map naming

Core 3v3 sample: 925 games.

Core 3v3 game types:

• Top vs Bottom: 698
• Use map settings: 227

Average core 3v3 length was about 10:54; median was about 9:56.

This is enough for community player profiling. It is not yet a full tactical VOD review. The current evidence can support:

• frequent player identification
• race tendencies
• win/loss shapes
• mechanical activity level
• teammate/opponent relationships
• BeibeiQ opening and command habit analysis

It cannot directly prove:

• why a specific fight was lost
• whether a defense was self-called or team-called
• exact minimap positioning and army pathing
• precise scouting, vision, and micro quality

Community Read

This replay pack is not a clean anonymous ladder pool. It is a long-running BGH community pool.

That matters because BGH 3v3 results are shaped by:

1. Team composition: fixed partners, race mix, and uneven sides can strongly move win rate.
2. Game length: short games are often opening collapse or early pressure; mid games test team shape; long games test macro, remax, anti-air, detection, and final-tech roles.
3. Community role: some players are carries, some are stabilizers, some are pure tempo, some are social/fun anchors.

So this report is a community coaching profile, not a ladder ranking.

BeibeiQ Profile

One-line read:

BeibeiQ is a high-presence, mostly Protoss BGH 3v3 community player. She is not a pure carry and not dead weight. Her best window is normal midgame team play. The repair lane is making her first 10 minutes safer and giving her a clearer Protoss job after 18 minutes.

Sample

BeibeiQ appears in 150 BGH-matched replays overall.

In the clear 3v3 core sample she appears in 80 games:

• record: 36-44
• win rate: 45.0%
• average APM/EAPM: 132.6 / 113.3
• race split: Protoss 70, Terran 6, Zerg 4

Race split:

The identity is clear: BeibeiQ should be coached as a BGH Protoss player. Terran and Zerg are too small as samples and should be treated as fun/random games, not the main repair lane.

Strengths

1. Stable attendance and usable mechanical activity.

80 clear 3v3 games is meaningful. 132.6 / 113.3 APM/EAPM is a stable, trainable community BGH level. Do not coach her like someone who has no rhythm.

1. Her Protoss opening is not random.

Command pass covered 80/80 BeibeiQ games. Her first building was:

• Pylon: 63
• Supply Depot: 5
• Drone: 4

In Protoss games, the first building was consistently Pylon. The first Pylon usually landed around 0:49-0:53. That is a real opening rhythm.

1. She participates in the game.

Aggregate BeibeiQ command signals:

• Probe: 10,651
• Zealot: 5,080
• Dragoon: 1,655
• High Templar: 320
• Dark Templar: 183
• Pylon: 804
• Photon Cannon: 500
• Gateway: 370
• Assimilator: 112
• Forge: 68
• Cybernetics Core: 56
• Citadel of Adun: 51
• Templar Archives: 39

This is a recognizable BGH Protoss path: Pylon / Cannon / Gateway / Zealot early activity into Dragoon, HT/DT, and selective tech support.

Main Repair Lane

The most important signal is the game-length split:

This is the coaching key.

BeibeiQ can win when the game enters stable midgame. Her 10-18 min win rate is 67.7%, which means she can follow a team shape and contribute once the game is not collapsing.

Her problem is on both ends:

• short games under 10 minutes: vulnerable to early pressure, opening collapse, or teammate collapse chains
• long games after 18 minutes: unclear Protoss final role, remax, detection, anti-air, spell value, and team fight contribution

The repair frame:

First lane: survive the first 10 minutes without becoming pure cannon turtle.
Second lane: after 18 minutes, know what Protoss value the team needs.

Teammate And Opponent Context

Frequent teammates:

• Azhi_Dahaki: 46 same-team games
• duoduoduo: 11
• NO0Bs: 10
• Marsox: 9
• [24H]WeiJia: 7

Frequent opponents:

• Marsox: 34
• GYRGYR~: 15
• Lastscer: 15
• UncletosS: 12
• duoduoduo: 10

Notable BeibeiQ teammate pairs:

BeibeiQ Coaching Prescription

1. Protoss first-10-minute stability

The goal is not to make her an APM monster. The goal is to make her fixed Protoss opening harder to break.

Training points:

• Keep first Pylon discipline around 0:49-0:53.
• Forge/Cannon should not become pure turtle. Defense must connect into Gateway production.
• Early Zealots should not be donated. They should protect an ally or pressure a real target.
• When paired with Z/T teammates, her job is often shield + bridge into midgame.

Measurable target:

Next 30 clear 3v3 games:
raise BeibeiQ's sub-10-minute win rate from 34.2% toward 45%+.

2. Preserve the midgame sweet spot

Her 10-18 min win rate is 67.7%. Do not over-repair this window.

Training points:

• Around 10 minutes, connect Zealot/Dragoon/HT into one usable team army.
• Keep at least one army that can join teammates. Do not leave all supply parked at home.
• Cannons are a position, not a win condition.
• When ahead, attack or defend the same side as the team instead of probing alone.

3. Define the long-game Protoss job

Her long-game record is 2-9. That is the loudest repair signal.

Training points:

• After 18 minutes, check three things: anti-air, detection, spell value.
• If she makes HT, they need protection and team timing.
• If she goes Arbiter/Carrier, ground Gateway mass still has to hold the front.
• If the team is already fighting, her job is to add Protoss control and sustain, not restart the game by rebuilding cannons at home.

Short Version For BeibeiQ

BeibeiQ should not be treated as only the cute community mascot. The sample says more than that:

• she is a stable Protoss community player
• she can win midgames
• her losses are concentrated in short collapse games and unclear long-game Protoss role games
• her repair words are first-10-minute stability, midgame join timing, and post-18-minute Protoss team value

Coaching sentence:

You can win the midgame.
Now make the first 10 minutes safer,
and make the 18-minute Protoss job clearer.

Core Player Profiles

Core threshold: clear 3v3 sample >= 40 games.

This is not a power ranking. It is a profile of each player's shape in this AutoSave community pool.

Watchlist

Players close to the core threshold:

• Tian.: 39 games, 20-19, mainly P, 204.6/149.3 APM/EAPM
• LineaPB: 39 games, 18-21, Z/P, 210.7/170.6 APM/EAPM

Coaching Conclusion

This replay pack is valuable because it captures a real community, not just isolated games.

Best next deep-dive lanes:

1. BeibeiQ: Protoss first-10-minute stability and post-18-minute team value.
2. wulawula / [24H]Yida / ShiBuYeSha: high APM, low win conversion.
3. [24H]Mr-J / [24H]MoFan / Temporarias: strong community carry samples.
4. EyeofTheStorm / LongZhu.: lower or moderate APM, positive results.
5. BeibeiQ + NO0Bs + WeiJia and BeibeiQ + Azhi_Dahaki + duoduoduo: fixed-team shape review.

The right product loop for Brood War AI coaching:

batch metadata
-> meaningful player profile
-> one focus player deep dive
-> fixed team composition comparison
-> selected replay VOD/manual tactical review

For BeibeiQ, the next replay selection should be:

• a set of sub-10-minute losses to see how she gets pulled into collapse
• a set of 10-18-minute wins to see why her sweet spot works

That is real coaching, not just a scoreboard.