Build & Strategy Definitions

Detected if 4 Gateways exist before 6:00 and before the 2nd Nexus.

3 or 4 Gateways have been made along with Blink before 6:30 without a second Nexus.

Detected if a Photon Cannon is built near your base (Proxy) before 4:30.

Detected if Charge is researched, 7+ Gates, and low gas count.

Mid/Late game composition fallback based on Archons and Chargelots.

Detected if a Dark Shrine is built before 5:00 AND at least one real (non-hallucinated) Dark Templar is on the field by 6:00 -- a true DT harass opener. Mid-game DT-tech additions (Shrine going down after a Stargate or Robo opener) and Sentry-hallucinated Dark Templars are excluded.

Detected if Twilight Council + Glaives researched + High Adept count by 6:30.

Detected if a Gateway is started by 1:45 more than 50 units from the opponent's own main (a proxy) and no natural Nexus is started before 4:30 -- a proxied 2-Gate / 3-Gate aggression. Timing separates it from a proxy Robo / Stargate (proxied at ~2:00-3:00); 3+ proxied Gateways before 4:30 are the Proxy 4 Gate.

Detected if 3+ Gateways are started before 4:30 more than 50 units from the opponent's own main (a proxy) and no natural Nexus is started before 4:30.

Detected if a Robo is built away from the opponents base before 6:30.

Detected if a Stargate is built away from the opponents base before 6:30.

Mid/Late game composition fallback based on Colossi or Disruptors.

Detected if a Robotics Facility is built before 6:30 AND no Twilight Council was started before it (a 2-Gate Expand Blink build with a later Robo is a Twilight-first opener, not a Robo Opener).

Mid/Late game composition fallback based on multiple Stargates or Carriers.

Detected if the 2nd Nexus starts before 6:30.

Detected if Protoss has 3 Bases and Charge/Immortal/Archon tech path.

Detected if a Stargate is built before 6:30.

Catch-all for unclassified Protoss games.

PvP standard 1-gate expand: exactly 1 Gateway started before the natural Nexus (which goes down before 5:00), the first warp-in is a Stalker / Adept / Zealot, and no Stargate / Robotics Facility / Twilight Council was started before the natural. Tech before the natural makes it a tech-first opener (Standard Stargate Opener, Robo Opener, Rail's Blink Stalker, ...); the 1 Gate Expand label is kept only when no tech rule recognises the game.

Detected if exactly 1 Gateway is started before the natural Nexus (which goes down before 5:00), 4+ Gateways exist by 6:00, the first warp-in is a Stalker / Adept / Zealot (NOT Sentry), no tech building (Stargate / Robotics Facility / Twilight Council / Templar Archive / Dark Shrine) is started before the 4th Gateway, and Warp Gate research finishes by 5:30 -- the 1 Gate Nexus into 4 Gate Stalker timing.

PvP safer 2-gate expand: 2 (or more) Gateways are started before the natural Nexus (which goes down before 5:00) AND no tech building (Stargate, Robotics Facility, or Twilight Council) is started before the natural. A Stargate / Robo / Twilight before the natural means it is a tech-first opener (Standard Stargate Opener, Robo Opener, ...); the 2 Gate Expand label is kept only when no tech rule recognises the game. Trades a few seconds of economy for protection vs proxy 2-gate / early aggression.

Detected if a Stargate is built, 3+ Stalkers by 6:30, 1+ Oracle by 7:30, and a Dark Shrine is built by 9:00 -- Stalker / Oracle harass transitioning into Dark Templar.

Detected if the Twilight Council is the FIRST tech building (built before any Robotics Facility AND any Stargate -- pure ordering, no time threshold) and the FIRST upgrade researched out of it is Resonating Glaives (Glaives starts BEFORE Blink and BEFORE Charge) -- a pure Gateway Adept Glaive timing. The Glaives-first signal separates it from Blink Stalker Style, where Blink would be researched first.

Detected if a Stargate is built, 4+ Adepts have been produced by 6:00 AND 1+ Oracle is on the field by 6:30 -- the AlphaStar 4-Adept / Oracle pressure opener. Oracles without a Stargate are treated as hallucinations.

Detected if Blink is researched by 9:00, the player has expanded (2+ Nexuses), and they have between 2 and 4 Gateways by 9:00 -- a macro Blink Stalker game.

Detected if a Stargate is built and 3+ Phoenix have been produced by 8:30 -- an air-control / Phoenix-heavy PvP style. Hallucinated Phoenix from Sentries do not count.

Detected if a Gateway is started by 1:45 more than 50 units from the player's own main (a proxy) and no natural Nexus is started before 4:30 -- a proxied 2-Gate / 3-Gate aggression. Timing is what separates it from the other forward builds: a true proxy 2-Gate's Gateways go down between ~0:30 and ~1:15 (1:45 leaves a margin), while a proxy Robo proxies at ~2:00-3:00 and a 3-4 Gate (Warp Gate) build with a forward Gateway places it in that same band -- neither counts.

Detected if a Robotics Facility is started before 6:30 more than 50 units from the player's own main (a proxy) -- a proxied Robo (Immortal / Warp Prism) opener. The forward Gateway dropped beside the Robo (~2:00-3:00) is far later than a proxy 2-Gate's Gateways (~0:30-1:15), so it no longer tags the game as Proxy 2 Gate.

Detected if a Stargate is started before 6:30 more than 50 units from the player's own main (a proxy) -- a proxied Stargate (Void Ray / Oracle) PvP opener, the PvP counterpart of PvT - Proxy Void Ray/Stargate.

Detected if Robotics Facility goes down BEFORE Twilight Council, BOTH go down before the natural Nexus, and Blink is researched by 9:00 -- a Robo-first Blink Stalker style. A Robo-first build whose FIRST Twilight upgrade is Glaives tags as PvP - Robo into Glaives instead; a Robo-first build without Blink is the PvP - Robo Opener.

Detected if a Robotics Facility in the player's own base is the FIRST tech building (before any Stargate and Twilight Council -- pure ordering, no time threshold) and no more specific Robo label applies (Proxy Robo Opener, Robo into Glaives, Rail's Blink Stalker) -- the standard Robo-first (Immortal / Observer) PvP opener.

Detected if a Robotics Facility is built BEFORE the Twilight Council and the FIRST upgrade researched out of that Twilight Council is Resonating Glaives (Glaives starts BEFORE Blink and BEFORE Charge) -- the common PvP Robo (Immortal / Observer) opening into a Glaive Adept timing. Classification is purely order-based: the Glaives-first signal is what separates this from Rail's Blink Stalker (Robo 1st), where Blink would be the upgrade instead.

Detected if a Stargate is built before 6:30 in the player's own base (not proxied) and is the FIRST tech building (before any Robotics Facility / Twilight Council) -- the standard Stargate (Oracle / Phoenix) PvP opener.

PvP 1-gate expand variant where exactly 1 Gateway is started before the natural Nexus (which goes down before 5:00), the first warp-in is a Sentry, and no Stargate / Robotics Facility / Twilight Council was started before the natural (tech before the natural is a tech-first opener; this label is kept only when no tech rule recognises the game).

Catch-all bucket for PvP replays that ended in under 45 seconds (no build order developed). Both the player and the opponent get this label so the data view stays consistent. Filterable via the analyzer's 'Exclude too-short games' toggle.

PvP catch-all: the game reached the macro phase but did not match a more specific PvP pattern.

Detected if Twilight Council is the FIRST tech building (before any Robotics Facility AND before any Stargate), a Templar Archives is started by 9:00 and BEFORE the third Nexus, the third Nexus (if any) is delayed to 6:00 or later, the player has 4-6 Gateways by 7:30, AND Blink was not the first Twilight upgrade researched before the Archives (that is a Blink build with a Storm follow-up) -- a reactive 2-base High Templar / Storm timing with a delayed 3rd. The Twilight-first ordering guard keeps Robo-first openers that add a late TA for Storm support off this label (those fall through to Robo First). A hallucinated High Templar is NOT enough; the Templar Archives must actually exist.

Detected if Twilight Council is the FIRST tech building (before Robo AND Stargate), Blink is the first completed Twilight upgrade and finishes by 8:00, the player has taken 3+ Nexuses, AND exactly 2 Gateways were STARTED before the 3rd Nexus -- a fast-3rd 2-Gate Blink style, with or without a Robotics Facility follow-up for Observer / Immortal support. The Twilight-first ordering keeps Robo-first openers with a midgame Blink tech-switch off this label. The gate count is measured against the 3rd Nexus's start time, not a fixed 7:30 cutoff, so a player can add more Gateways after taking the 3rd Nexus without flipping the label to 3 or 4 Gate Blink.

Detected if Twilight Council goes BEFORE Robo and Stargate, Blink is the first completed Twilight upgrade and finishes by 9:00, AND exactly 3 Gateways were STARTED before the 3rd Nexus -- a macro 3-Gate Blink style. Counting gates before the 3rd Nexus (not a fixed 7:30 cutoff) means a player who takes the 3rd Nexus fast and then adds more Gateways still classifies as 3 Gate Blink, while a player who delays the 3rd Nexus to push out 4+ Gateways gets labelled 4 Gate Blink.

Detected if Charge is researched by 9:00 AND Twilight Council was built BEFORE Robotics Facility AND BEFORE Stargate -- a Twilight-first 3-Gate Charge opener. A Dark Shrine started after Twilight and by 5:00 excludes this Charge-first opening, even without proof of a real DT rush.

Detected if Twilight Council goes BEFORE Robo and Stargate, Blink is the first completed Twilight upgrade and finishes by 9:00, AND 4+ Gateways were STARTED before the 3rd Nexus -- a 4-Gate Blink Stalker timing. The gate count is measured against the 3rd Nexus's start time, so a player who delays the 3rd Nexus while adding Gateways gets this label, while a player who takes the 3rd Nexus fast and then adds Gateways gets the lower-count Blink label that matches what was committed pre-expansion.

Detected if Twilight Council is the FIRST tech building (before Robo AND Stargate), Blink is the first completed Twilight upgrade and finishes by 9:00, 6+ Gateways exist by 9:00, the 5th Gateway was STARTED before the 3rd Nexus was STARTED, AND no 3rd Nexus was STARTED before 6:00 -- a heavy Twilight-first multi-Gate Blink all-in. The Twilight-first guard keeps Robo-first openers with 6+ Gateways + late Blink off this label (those fall through to Robo First). "Taken" the 3rd Nexus means construction was initiated, not finished: a player can drop a LATE 3rd Nexus (6:00 or later) and add Gateways while it is still building and those Gateways are still macro reinforcement, not all-in production. The build is excluded if the 3rd Nexus broke ground before the 5th Gateway, OR if any 3rd Nexus was taken before 6:00 (a fast 3rd Nexus is a macro commitment, so those builds fall through to the 3/4 Gate Blink (Macro) labels). A DT Drop opener that later macros into a multi-Gate Blink composition is also excluded -- the DT Drop signature is checked first.

Detected if Twilight Council is the FIRST tech building (before Robo AND Stargate), Charge is researched by 9:00, 7+ Gateways exist by 7:30, AND fewer than 3 Nexuses have been taken -- a 2-base Twilight-first mass-Gate Chargelot all-in. The Twilight-first guard keeps Robo-first openers with 7+ Gateways + late Charge off this label (those fall through to Robo First). A Dark Shrine started after Twilight and by 5:00 excludes this Charge-first opening even if no real DT rush is proven.

Detected if Stargate is the first tech building and Oracle is its first real unit, produced before Robo and the third Nexus. The second Gateway starts after Stargate, exactly two Gateways start before the third Nexus, the third starts before 6:00, and Robo starts by 5:30, at most 30 seconds before the third. Both the third and Robo precede Twilight, which starts by 8:00. This identifies the two-Gate Oracle / fast-third / Robo-then-Twilight macro opening, including near-simultaneous Robo and third placement. Later Phoenix do not change the opener.

Detected if Twilight Council is the FIRST tech building (started before any Robotics Facility AND before any Stargate), Charge is the first completed Twilight upgrade and finishes by 9:00, AND the third Nexus is STARTED before 6:00 -- a Charge-first fast-third macro opener. Nexus timing measures the start of construction, not completion. A Dark Shrine started after Twilight and by 5:00 excludes this Charge-first opening, even without proof of a real DT rush. Later Blink, Robo support, Stargate or late Dark Shrine transitions do not change the opening label. More-specific proxy, DT, all-in, and Templar rules take precedence.

Detected if a Dark Shrine is started by 4:15 AND a Robotics Facility is up by 4:30 AND at least one real (non-hallucinated) Dark Templar exists on the field by 5:00 AND a real Warp Prism is on the field by 5:15 -- a fast tactical PvT DT drop. The cutoffs are calibrated against a real PvT DT Drop replay (Peruano, Taito Citadel LE 2026-05-11: Shrine 3:13, Robo 3:32, DT 3:51, Prism 4:11) with ~60 seconds of buffer per signal so slower variants still classify. An early Twilight/Shrine commitment with a real DT by 6:00 can still be DT Rush when the drop proof is missing or late; later DT support does not prove a rush.

Detected if Twilight Council is the first tech building (before Robotics Facility and Stargate), Dark Shrine starts after Twilight and by 5:00, and at least one real, non-hallucinated Dark Templar is on the field by 6:00. This early DT opening takes precedence over later Charge, Blink and fast-third macro signals. The tighter DT Drop signature with a real early Warp Prism takes precedence. Shrine-only tech, hallucinations and late DT support do not prove a rush; building timestamps are construction starts, not invented completion times.

Detected if Stargate is the first tech building and Oracle is its first real unit, on the field by 7:00, without matching the more specific AlphaStar or Stargate-into-Twilight-upgrade rules. Flagged hallucinations and units missing tech prerequisites do not count. Later Phoenix do not change an Oracle-first opener into Phoenix play.

Detected if Stargate is the first tech building, Phoenix is its first real unit and is on the field by 7:00, and the second Gateway starts before Robotics Facility. Earlier Oracle, Void Ray, Carrier or Tempest production prevents later Phoenix from changing the opener. Flagged hallucinations and units missing tech prerequisites do not count.

Detected if Stargate is the first tech building, Phoenix is its first real unit and is on the field by 7:00, and a Robotics Facility starts by 8:00. Earlier Oracle, Void Ray, Carrier or Tempest production prevents later Phoenix from changing the opener. Flagged hallucinations and units missing tech prerequisites do not count.

Detected if a Gateway is started by 1:45 more than 50 units from the player's own main (a proxy) and no natural Nexus is started before 4:30 -- a proxied 2-Gate / 3-Gate aggression vs Terran. Same timing rule as PvP - Proxy 2 Gate: a true proxy 2-Gate's Gateways go down between ~0:30 and ~1:15; a forward Gateway in the 2:00-3:00 band (proxy Stargate, 3-4 Gate with a proxy Gateway) is not one.

Detected if a Stargate is started more than 50 units from the player's own main (a proxy) before the natural Nexus, or before 4:30 when the natural came first -- a proxied Stargate (Void Ray) timing.

Detected if a Robotics Facility is built before 6:30 AND it is the FIRST tech building (before any Stargate or Twilight Council). The label describes the OPENER, not the entire composition: a Robo opener that transitions into Stargate tech later in the midgame (Skytoss tech-switch, end-game Tempests) still classifies as Robo First because the opening was Robo. Stargate-led openers are caught earlier by Phoenix into Robo / Phoenix Opener / Stargate Opener so they don't fall into this bucket.

Detected if Charge is the first completed Twilight upgrade and finishes by 9:00, the player has taken 3+ Nexuses, the third Nexus is started at 6:00 or later, AND Twilight Council is the FIRST tech building -- Twilight goes down before any Robotics Facility AND before any Stargate. A Dark Shrine started after Twilight and by 5:00 excludes this Charge-first opening, even without proof of a real DT rush. The label describes the OPENER, not the entire composition: a Twilight-first Charge macro that later adds Robo (Observer / Immortal support) or transitions into Stargate tech in the midgame (Skytoss tech-switch, end-game Tempests, late Phoenix harass) still classifies as Standard Charge Macro because the opening was Twilight + Charge. A third Nexus started before 6:00 uses Charge First (Fast 3rd Nexus); later Blink does not turn either Charge-first opening into a Blink build. Robo-first openers (Robo before Twilight) are caught by Robo First instead; Stargate-led openers are caught earlier by Stargate into Charge / Phoenix into Robo.

Catch-all: detected when a Stargate is the FIRST tech building after the Cybernetics Core (before Twilight Council and before Robotics Facility) AND the build did NOT match any more specific Stargate-prefixed PvT rule (Proxy Void Ray / Stargate into Charge / Glaives / Blink / AlphaStar Style / Oracle Opener / Phoenix into Robo / Phoenix Opener). A custom build rule can refine this further.

Detected if a Stargate is built before any Twilight Council (the Stargate unit produced does NOT matter), a Twilight Council is built AFTER the Stargate, AND the FIRST upgrade researched out of the Twilight Council is Blink (i.e. Blink starts before Resonating Glaives and before Charge). Stargate harass into Blink Stalker macro/midgame. Disqualified if a Robotics Facility (or an Immortal / Robotics Bay) lands BEFORE the Twilight Council — those replays are Phoenix into Robo, not Twilight-led.

Detected if a Stargate is built before any Twilight Council (the Stargate unit produced — Phoenix / Oracle / Void Ray — does NOT matter), a Twilight Council is built AFTER the Stargate, AND the FIRST upgrade researched out of the Twilight Council is Charge (i.e. Charge starts before Resonating Glaives and before Blink). The build can resolve as a 2-base Chargelot timing OR transition into a 3-base Charge macro game — the rule keys on the Stargate-then-Charge opening only and does NOT require an all-in commitment. Disqualified if a Robotics Facility (or an Immortal / Robotics Bay) lands BEFORE the Twilight Council — those replays are Phoenix into Robo / Robo First, not Twilight-led.

Detected if a Stargate is built before any Twilight Council (typically with Phoenix harass, but the Stargate unit does NOT matter), a Twilight Council is built AFTER the Stargate, AND the FIRST upgrade researched out of the Twilight Council is Resonating Glaives (Glaives starts before Blink and before Charge). The old-school Stargate-Phoenix into Glaive Adept midgame timing. Disqualified if a Robotics Facility (or an Immortal / Robotics Bay) lands BEFORE the Twilight Council — those replays are Phoenix into Robo, not Twilight-led.

Catch-all bucket for PvT replays that ended in under 45 seconds (no build order developed). Both the player and the opponent get this label so the data view stays consistent. Filterable via the analyzer's 'Exclude too-short games' toggle.

PvT catch-all: the game reached the macro phase but did not match a more specific PvT pattern.

Stargate-first opening with exactly 2 Stargates, 2+ Nexuses and 4+ real Phoenix by 7:00 or the first capital ship, whichever comes first. Later Carrier/Tempest transitions preserve the Phoenix label. Glaives-first Twilight or Robotics Facility by 10:00 reroutes to the matching transition.

Stargate-first opening with 2+ Stargates, 2+ Nexuses and 4+ real Void Rays by 7:00 or the first capital ship, whichever comes first. Later Carrier/Tempest transitions preserve the Void Ray label. Glaives-first Twilight or Robotics Facility by 6:00 reroutes to the matching transition; a later Robo is support.

Stargate-first opening with 3+ Stargates, 2+ Nexuses and 4+ real Phoenix by 7:00 or the first capital ship, whichever comes first. Later Carrier/Tempest transitions preserve the Phoenix label. Glaives-first Twilight or Robotics Facility by 10:00 reroutes to the matching transition.

Detected if a Robotics Facility is built, Glaives is researched by 8:30, 2+ Sentries and 1+ Immortal produced by 8:30, and 6+ Gateways exist by 9:00 -- a heavy Glaive Adept / Immortal all-in.

Detected if the Twilight Council is the FIRST tech building after the Cybernetics Core (no Stargate, Robotics Facility, or Dark Shrine is started before Twilight -- pure ordering, no time threshold), the FIRST upgrade researched out of the Twilight Council is Resonating Glaives (Glaives starts BEFORE Blink and BEFORE Charge), AND no Robotics Facility is built by 10:00 -- a pure Gateway Adept Glaive Timing without Robo support. Order-based with no Gateway-count window, like Stargate into Glaives.

Detected if the Twilight Council is the FIRST tech building after the Cybernetics Core (no Stargate, Robotics Facility, or Dark Shrine is started before Twilight -- pure ordering, no time threshold), the FIRST upgrade researched out of the Twilight Council is Resonating Glaives (Glaives starts BEFORE Blink and BEFORE Charge), AND a Robotics Facility is built by 10:00 (after Twilight, as Observer / Immortal support) -- the Robo variant of Adept Glaive Timing. Order-based with no Gateway-count window, like Stargate into Glaives.

Detected if the Stargate is the FIRST tech building, followed by the third Nexus and then a Robotics Facility that begins by 5:30 and before any Twilight Council, with 2+ Oracles plus a Forge present by 8:30 -- the AlphaStar Oracle / fast-third / fast-Robo composition. A missing or later Robo is not AlphaStar and falls to the matching Blink-, Charge-, or Resonating-Glaives-first transition.

Detected if Stargate is the first tech building, a real Warp Prism completes by 6:00, Templar Archives starts by 9:00, and 2+ real Archons are produced by 9:00. The Prism requires a Robotics Facility; absent, hallucinated or later Prisms do not count. Unit deadlines use recorded completion times, not estimated training-start times. Checked before Stargate into Robo.

Detected if Blink is researched by 8:00, 5+ Gateways exist by 8:00, the player has at most 2 Nexuses by 8:00, and has NOT built a Stargate or Dark Shrine by 8:00 -- a 2-base Blink all-in. A third Nexus by 8:00 is a Twilight-first Blink macro game, not the all-in.

Detected if a Photon Cannon is started before 4:30 more than 50 units from the player's own main (a proxy) -- a cannon rush vs Zerg.

Stargate-first opening with Fleet Beacon before Twilight/Robo/Dark Shrine and the first real capital ship a Carrier by 10:00. An established 2+ Stargate / 2+ Nexus force of 4+ Void Rays or Phoenix by 7:00 or the first capital ship, whichever comes first, keeps its opening label. Hallucinated units do not count.

Detected if a Dark Shrine is the player's primary alternative-tech path -- built BEFORE any Stargate / Robotics Facility -- with at least 1 real Dark Templar on the field by 9:00. Pure ordering, no time threshold: a slow Shrine with no earlier Stargate / Robo still counts. (Twilight Council is required as Dark Shrine's prereq, so a Twilight-first ordering is implicit and isn't checked separately.) Catches DT openers that transition to mid- or late-game tech (Skytoss / Mothership / Templar) -- without this rule a DT build that later picked up a Stargate + Carrier used to mis-fire as PvZ - Carrier Rush.

Detected if Twilight Council starts before Dark Shrine, Dark Shrine and Robotics Facility start by 9:00, a real Warp Prism completes by 6:00, 3+ real Dark Templar are produced by 9:00, and at least one real Archon is produced by 9:00. DTs without an observed Archon do not prove this follow-up. Unit deadlines use recorded completion times, not estimated training-start times; hallucinations do not count.

Detected if a Gateway is started by 1:45 more than 50 units from the player's own main (a proxy) and no natural Nexus is started before 4:30 -- a proxied 2-Gate / 3-Gate aggression vs Zerg. Same timing rule as PvP - Proxy 2 Gate: a true proxy 2-Gate's Gateways go down between ~0:30 and ~1:15; a forward Gateway in the 2:00-3:00 band (proxy Stargate, 3-4 Gate with a proxy Gateway) is not one.

Detected if a Stargate is started before 6:30 more than 50 units from the player's own main (a proxy) -- a proxied Stargate (Void Ray / Oracle) opener vs Zerg, the counterpart of PvT - Proxy Void Ray/Stargate.

Detected if a Robotics Facility AND a Robotics Bay are built and at least 1 Disruptor and 1 Warp Prism are produced by 8:00 -- an early Disruptor drop harass build.

Detected if a Robotics Facility is the FIRST tech building -- built BEFORE any Stargate / Twilight Council / Dark Shrine. Pure ordering, no time threshold: a slow Robo opener with no other tech first still counts.

Detected if a Stargate opener is followed by a third Nexus by 9:00 (the third starts before Twilight or within four minutes after it), Blink is the first Twilight upgrade and completes by 10:00, and any Robotics Facility follows the Twilight -- standard 3-base Blink macro rather than AlphaStar.

Detected if a Stargate opener is followed by a third Nexus by 9:00 (the third starts before Twilight or within four minutes after it), Charge is the first Twilight upgrade and completes by 10:00, and any Robotics Facility follows the Twilight -- standard 3-base Chargelot macro rather than AlphaStar.

Catch-all for any Stargate-first opener (Stargate built BEFORE any Twilight Council / Dark Shrine / Robotics Facility) that didn't match a more specific Stargate-prefixed PvZ rule -- Carrier Rush, Tempest Rush, 2/3 Stargate Phoenix, 2 Stargate Void Ray, AlphaStar Style, Stargate into Robo, Stargate into Glaives, Standard Blink Macro, Standard charge Macro, Archon Drop. Examples that land here: a Stargate that got harassed off before producing a real unit, a Stargate-into-Templar build without 2 Archons by 9:00, or any Stargate opener with an unusual midgame composition the analyzer doesn't have a named bucket for. Mirror of PvT - Stargate Opener.

Detected if a Stargate is the FIRST tech building, Twilight Council is added before any Robotics Facility, and the FIRST Twilight upgrade is Resonating Glaives (completed BEFORE Blink and Charge) -- a Stargate opener into Glaive Adepts. Classification is order-based with no Gateway-count window: a Robo added after Twilight is support and cannot steal the Glaives label, while Robo-before-Twilight remains AlphaStar or Stargate into Robo.

Detected if the Stargate is the FIRST tech building, at least 1 real Phoenix / Oracle / Void Ray is on the field by 10:00, and a Robotics Facility is built by 10:00. This is the generic Stargate-into-Robo transition only when a clearer three-base Twilight path is absent: Twilight-then-Glaives before the Robo uses PvZ - Stargate into Glaives, while a three-base Twilight build whose first upgrade is Blink or Charge keeps its Standard Blink / Charge Macro label even if a support Robo is added later. Twilight may precede the third only when that Nexus follows within four minutes.

Stargate-first opening with Fleet Beacon before Twilight/Robo/Dark Shrine and the first real capital ship a Tempest by 10:00. Later Carriers do not overwrite it, and an established 2+ Stargate / 2+ Nexus force of 4+ Void Rays or Phoenix by 7:00 or the first capital ship, whichever comes first, keeps its opening label. Hallucinated units do not count.

Catch-all bucket for PvZ replays that ended in under 45 seconds (no build order developed). Both the player and the opponent get this label so the data view stays consistent. Filterable via the analyzer's 'Exclude too-short games' toggle.

PvZ catch-all: the game reached the macro phase but did not match a more specific PvZ pattern.

Detected if a Factory (before 6:30) and Starport (before 8:10) are both built BEFORE the second Command Center -- a 1-base 1-Rax / 1-Fact / 1-Port pressure build, not the standard expanding 1-1-1.

Detected if Factory (before 6:30) and Starport (before 8:10) are built and they are after the second CC.

Detected if 2 Gas, 3 Reapers, and 2 Hellions before 5:30.

Detected if 3+ Barracks exist before 6:30 off a single Command Center, no Refineries, and 2+ Reapers have been produced before 6:30 -- early Reaper-heavy aggression.

Detected if 3 Barracks are built after second CC but before any other tech buildings.

Detected if 3+ Barracks exist before 6:30 off a single Command Center with NO Refineries -- a gas-less, Marine-only mass-Rax all-in.

Detected if a Fusion Core is built before 5:30 AND at least one Battlecruiser is on the field by 7:30 -- a Starport-into-FC BC commitment. A Fusion Core alone is not enough; mech-into-late-game-BC macro games build FC for end-game composition and are excluded by the unit-presence requirement.

Detected if a Banshee and Cloak or Hyper Flight Rotors exists before 7:30.

Mid/Late game composition fallback based on heavy Barracks production.

Detected if Factory with Tech Lab and Cyclones are built early (< 5:30).

Detected if 3 Command Centers exist before 7:00 (Counting only construction, ignoring Orbitals).

Detected if Ghost Academy is built within first 5:30 of the game -- a true 1-2 base Ghost commitment. Standard Bio macro builds usually add the Academy after 6:00 for mid-game snipes / EMPs and are excluded.

Detected if Armory is built early (< 5:00) with high Hellion/Hellbat count.

Mid/Late game composition fallback based on heavy Factory production.

Detected if Factory (before 6:30) and Starport (before 8:10) and are built away from their base.

Detected if Barracks are built far from the main base before 4:30.

Detected if a Factory and Starport are built away from the main base, the player has expanded (2nd Command Center started), 2+ Hellions are produced by 6:00, and the FIRST unit produced from the Starport is a Medivac -- an expanding proxy Starport build that uses a Medivac to ferry Hellions into the opponent's mineral line (Yoon-style Hellion drop). Differs from Proxy 1-1-1 by the 2nd CC and the Medivac-first opener.

Mid/Late game composition fallback based on heavy Starport production.

Detected if 3 CCs, Engineering Bays, and Tanks/Medivacs are present.

Detected if Medivac and multiple widow mines are built after second CC within the first 6:30. Against Protoss, Medivac must be the first or co-first real Starport unit; earlier Vikings or other Starport units prevent this opening label.

Detected if a Medivac and 2+ Widow Mines are built AFTER the second Command Center (within ~6:30), and a Thor has been produced before ~8:10 -- a Mine drop transitioning into Thor pressure. Against Protoss, Medivac must be the first or co-first real Starport unit; earlier Vikings or other Starport units prevent this opening label.

Detected if a Medivac and 2+ Widow Mines are built BEFORE the second Command Center -- a 1-base Widow Mine drop cheese. Against Protoss, Medivac must be the first or co-first real Starport unit; earlier Vikings or other Starport units prevent this opening label.

Catch-all for unclassified Terran games.

Detected when a Factory and Starport are built before any expansion and a Banshee reaches the field on one base -- the 1-base cloak-Banshee harass vs Protoss.

Terran user-side label: Barracks + Factory + Starport all built BEFORE the 2nd Command Center, none of the three proxied -- the classic 1-base 1-1-1 all-in vs Protoss (Cloak Banshee / Marine-Tank / Marine-Medivac-Tank pressure off a single base).

Detected when a Starport build fields Siege Tanks behind a Marine ball off two bases -- the classic tank-push timing vs Protoss.

Detected when a Reaper-first scout takes a single expansion (no fast 3rd CC) and adds a Factory + Starport for the Medivac-drop / Stim bio timing off two bases vs Protoss.

Detected when 3+ Barracks off one base flood Marines with no Factory -- a gas-light Marine all-in vs Protoss.

Detected when a fast Fusion Core lands Battlecruisers -- the Battlecruiser rush vs Protoss.

Detected when an early Factory produces Cyclones off two or fewer bases -- the lock-on Cyclone pressure vs Protoss.

Detected when three Command Centers are taken by 6:00 behind 3+ Barracks of Marine/Marauder with no mech tech -- the greedy macro bio opening vs Protoss.

Detected when four Barracks (at least one proxied near the enemy) flood Reapers -- the all-in proxy reaper rush vs Protoss.

Detected when a proxied Barracks pumps Marauders into the Protoss wall -- the proxy Marauder rush vs Protoss.

Detected when an Armory backs Thors and Siege Tanks -- the positional mech composition vs Protoss.

Detected if 2+ real Widow Mines and a real Medivac are produced by 6:30, Medivac is the first or co-first real Starport unit (no later than Viking, Liberator, Banshee, Raven or Battlecruiser), and 8+ Marines are produced by 8:00. Later support mines or a Medivac added after a Viking opener do not classify as a mine-drop opening.

Catch-all bucket for TvP replays that ended in under 45 seconds (no build order developed). Both the player and the opponent get this label so the data view stays consistent. Filterable via the analyzer's 'Exclude too-short games' toggle.

Detected when a Factory and Starport are built before any expansion and a Banshee reaches the field on one base -- the classic 1-1-1 cloak-Banshee harass.

Detected when a Starport build fields Siege Tanks and Marines off two bases (no Viking) -- the TvT bio-tank timing.

Detected when 3+ Barracks off one base flood Marines with no Factory -- a gas-light TvT Marine all-in.

Detected when cloak Banshees are backed by a Raven for detection and anti-air -- the TvT Banshee/Raven harass.

Detected when a fast Fusion Core lands Battlecruisers -- the TvT Battlecruiser rush.

Detected when an early Factory produces Cyclones off two or fewer bases -- the TvT Cyclone push.

Detected when a Viking-heavy air composition dominates the skies -- the TvT mass-Viking late game.

Detected when four Barracks (at least one proxied near the enemy) flood Reapers -- the all-in proxy reaper rush in TvT.

Detected when a proxied Barracks pumps Marauders into the enemy base -- the TvT proxy Marauder rush.

Detected when a Reaper-first scout is followed by a single expansion and then Siege Tanks behind Vikings -- the standard TvT positional macro opener that masses tanks for the air-controlled contain.

Detected when an Armory backs Thors and Siege Tanks -- the positional TvT mech composition.

Catch-all bucket for TvT replays that ended in under 45 seconds (no build order developed). Both the player and the opponent get this label so the data view stays consistent. Filterable via the analyzer's 'Exclude too-short games' toggle.

Detected when a Factory and Starport are built before any expansion and a Banshee reaches the field on one base -- the 1-base cloak-Banshee harass vs Zerg.

Detected when an Armory and two Factories produce Thors behind a wall of Hellions/Hellbats off two bases -- the 2-base mech timing vs Zerg.

Detected when a Starport Medivac drop carries Marines off two bases -- the committed 2-base drop timing (not 3-CC macro).

Detected when Armory-backed Hellbats and Marines push off two bases without a Thor -- the 2-1-1 marine/hellbat timing attack.

Detected when three Command Centers are taken by 6:00 behind 3+ Barracks of Marine/Marauder with no mech tech (Armory / Fusion Core) -- the standard macro bio opening vs Zerg.

Detected when 3+ Barracks off a single base produce a Marine flood with no Factory -- a gas-light Marine all-in vs Zerg.

Detected when a Fusion Core produces Battlecruisers as the late-game mech finisher vs Zerg.

Detected when early Hellions plus a Liberator zone the Zerg's bases off two CCs -- the Hellion/Liberator harass opener.

Detected when four Barracks (at least one proxied near the enemy) flood Reapers -- the all-in proxy reaper rush vs Zerg.

Detected when a Reaper-first scout and early Hellions back a fast expansion before any air or mech-upgrade tech -- the standard economic Reaper/Hellion opener vs Zerg.

Detected when a Marine ball with 2+ Widow Mines and a Medivac runs mobile mine drops vs Zerg.

Catch-all bucket for TvZ replays that ended in under 45 seconds (no build order developed). Both the player and the opponent get this label so the data view stays consistent. Filterable via the analyzer's 'Exclude too-short games' toggle.

Detected if a Roach Warren is built off 1 base very early (< 3:40).

Detected if Spawning Pool starts < 50s and NO new drones were built (Strict 12 Supply).

On patch 5.0.16 (8 workers) this is labelled Zerg - 8 Pool.

Early pool and early gas (<70s) leading into Baneling Nest before 3:20.

Early pool and early gas (<70s) for aggressive speedlings.

Standard modern Zerg macro opener (Hatch < 85s, Gas < 95s, Pool < 105s).

Detected if a Spire is started before 7:00 with low drone count.

Detected if a Nydus Network is built before 7:00.

Detected if Roach Warren exists, Lair exists, high Roaches/Ravagers count, low drone count (< 40) off 2 bases.

Standard safe Zerg macro reaching 3 bases by 6:30 off a Hatch First.

Standard safe Zerg macro reaching 3 bases by 6:30 off a Pool First.

Detected if a 3rd Hatchery is started before the Spawning Pool.

Detected 3 bases but >20 lings and <30 drones by 5:00.

Detected if Spawning Pool starts < 1:10 but drones were built.

Hatch First opener: the natural Hatchery starts before the Spawning Pool, without the 17 Hatch / 18 Gas / 17 Pool gas timing.

Mid/Late game composition fallback featuring Hydralisks.

Mid/Late game composition fallback based on Mutalisks and Banelings.

Generic Pool first opener that transitions into standard macro.

Detected if a hatchery being built on the opponents side of the map within the first 4:30.

Mid/Late game composition fallback heavily focused on Roaches and Ravagers.

Catch-all for unclassified Zerg games.

Detected when the Spawning Pool starts before 0:55 into a wall of Zerglings on one base -- the cheese rush vs Protoss.

On patch 5.0.16 (8 workers) this is labelled ZvP - 8 Pool Rush.

Detected when a Nydus Network goes down off two bases for a worm into the Protoss main -- the ZvP Nydus all-in.

Detected when a Roach Warren produces a wall of Roaches and Ravagers off two bases on a low drone count -- the ZvP roach/ravager all-in.

Detected when a greedy three-base economy (40+ Drones) opens hatch-first vs Protoss.

Detected when a Hydralisk Den fields a hydra wave off three bases -- the standard ZvP answer to Stargate openers.

Detected when an early Pool and Baneling Nest flood Banelings and Zerglings off two or fewer bases -- the bust through the Protoss wall.

Detected when a Baneling Nest and Spire support Banelings and a wall of Zerglings -- the muta/ling/bane harass style vs Protoss.

Detected when a Lurker Den enables a positional Lurker contain vs Protoss.

Detected when a Spire into 6+ Mutalisks (no Baneling Nest) runs pure muta harass into the Protoss mineral lines.

Detected when three bases pump 20+ Zerglings on a low drone count -- the ZvP ling-flood timing against a greedy third.

Catch-all bucket for ZvP replays that ended in under 45 seconds (no build order developed). Both the player and the opponent get this label so the data view stays consistent. Filterable via the analyzer's 'Exclude too-short games' toggle.

Detected when a Nydus Network goes down off two bases for a drop into the Terran main -- the ZvT Nydus all-in.

Detected when a Roach Warren produces a wall of Roaches and Ravagers off two bases on a low drone count -- the ZvT roach/ravager pressure timing.

Detected when three bases pump 20+ Zerglings on a low drone count -- the ZvT ling-flood timing.

Detected when three bases go down with a Baneling Nest and Spire, defending bio with Banelings and Zerglings while teching to Mutalisks -- the textbook ZvT macro style.

Detected when a greedy three-base economy (40+ Drones) opens hatch-first vs Terran.

Detected when an early Pool and Baneling Nest flood Banelings and Zerglings off two or fewer bases -- the ZvT ling/bane bust.

Detected when a Lurker Den enables a positional Lurker contain vs Terran.

Detected when a Spire into 6+ Mutalisks (no Baneling Nest) runs pure muta harass vs Terran.

Detected when a queen-heavy defence (6+ Queens) holds with no Roach/Baneling/Spire aggression -- the ZvT queen-walk / defensive style.

Detected when a Roach Warren and Hydralisk Den field a roach/hydra ground army vs Terran.

Catch-all bucket for ZvT replays that ended in under 45 seconds (no build order developed). Both the player and the opponent get this label so the data view stays consistent. Filterable via the analyzer's 'Exclude too-short games' toggle.

Detected when the Spawning Pool starts before 0:55 into a wall of Zerglings on one base -- the aggressive ZvZ speedling opener.

On patch 5.0.16 (8 workers) this is labelled ZvZ - 8 Pool Speedling.

Detected when a sub-55s Pool goes straight into a Baneling Nest and Banelings -- the early ZvZ baneling all-in.

On patch 5.0.16 (8 workers) this is labelled ZvZ - 8 Pool into Baneling.

Detected when a Nydus Network goes down off two bases -- the ZvZ Nydus all-in.

Detected when a greedy hatch-first economy (30+ Drones, slow Pool) drones up in ZvZ.

Detected when a hatch-first economy (slow Pool) teches to a Spire -- the ZvZ hatch-first muta.

Detected when a Baneling Nest floods Banelings and Zerglings off two or fewer bases -- the ZvZ ling/bane all-in.

Detected when a Spire into 6+ Mutalisks creates the classic ZvZ muta war.

Detected when a Roach Warren produces a wall of Roaches off two bases -- the standard ZvZ roach pressure / all-in.

Detected when a Roach Warren fields Roaches and Ravagers -- the ZvZ roach/ravager style.

Detected when 20+ Zerglings flood on a low drone count -- the ZvZ ling flood.

Catch-all bucket for ZvZ replays that ended in under 45 seconds (no build order developed). Both the player and the opponent get this label so the data view stays consistent. Filterable via the analyzer's 'Exclude too-short games' toggle.