Back

Brood War replay fingerprint coach report. Source: Lastscer AutoSave pack, 8,157 parsed replays.

Lastscer Player Coach Report

This report focuses on the primary Lastscer ID, with alias-cluster context used only where useful. It is based on command fingerprints, not chat or raw replay publication.

Lastscer player infographic

Coach Read

Lastscer is a BGH battle anchor: high sample, Protoss-leaning, comfortable in repeated team-game patterns, and unusually battle-command heavy. He is not just pressing buttons; he is issuing a lot of target/fight instructions. The next level is converting that fight activity into cleaner timing rules.
Primary sample4,097

Games under the Lastscer ID.

Alias-cluster sample6,665

Largest cluster in this pack.

APM / EAPM195 / 148

Good community-level activity, not empty spam.

Main identity59% Protoss

Protoss anchor is the clearest role.

Player Shape

RaceGamesAPM / EAPMHotkeyCoach read
Protoss2,414201 / 1480.215Main weapon. Best identity for BGH anchor, army control, and midgame conversion.
Zerg866191 / 1540.206Functional and active, with the highest first-minute activity.
Terran817183 / 1400.187Playable, but less crisp than Protoss.

Strengths

Coach Advice

1. Stop taking every fight

Your command density is a strength, but it can turn into over-fighting. Before engaging, decide whether the fight is for defense, contain, punish, or finish.

2. Make Protoss the main job

Your best identity is a Protoss anchor. Build around stable production, detection, and prepared army positions instead of improvised trades.

3. Clean up timing rules

BGH comfort can become autopilot. Write simple triggers: move when ally is ready, when detection is present, or when enemy economy is exposed.

4. Review first bad fight

Do not review only the final loss. Find the first low-value engagement where your army got busy without gaining map value.

One-Line Prescription

Keep the battle-command edge, but make every fight buy something: position, economy, tech, or a finish.