Build & Strategy Definitions

The detection rules used by the analyzer to label opponent strategies and your own builds. Use these to interpret labels in the rest of the app.

Search builds and strategies

AllProtossTerranZerg

185 of 185 entries

• Protoss

  Protoss - 4 Gate Rush

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

• Protoss

  Protoss - Blink All-In

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

• Protoss

  Protoss - Cannon Rush

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

• Protoss

  Protoss - Chargelot All-in

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

• Protoss

  Protoss - Chargelot/Archon Comp

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

• Protoss

  Protoss - DT Rush

  Detected if a Dark Shrine is built before 7:30.

• Protoss

  Protoss - Glaive Adept Timing

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

• Protoss

  Protoss - Proxy 4 Gate

  Detected if 3+ Gateways are built far from the main base before 4:30.

• Protoss

  Protoss - Proxy Robo Opener

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

• Protoss

  Protoss - Proxy Stargate Opener

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

• Protoss

  Protoss - Robo Comp

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

• Protoss

  Protoss - Robo Opener

  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).

• Protoss

  Protoss - Skytoss Transition

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

• Protoss

  Protoss - Standard Expand

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

• Protoss

  Protoss - Standard Macro (CIA)

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

• Protoss

  Protoss - Standard Play (Unclassified)

  Catch-all for unclassified Protoss games.

• Protoss

  Protoss - Stargate Opener

  Detected if a Stargate is built before 6:30.

• ProtossPvP

  PvP - 1 Gate Expand

  PvP standard 1-gate expand: exactly 1 Gateway finished before the natural Nexus (which goes down before 5:00) and the first warp-in is a Stalker / Adept / Zealot.

• ProtossPvP

  PvP - 1 Gate Nexus into 4 Gate

  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 begins by 5:30 -- the 1 Gate Nexus into 4 Gate Stalker timing.

• ProtossPvP

  PvP - 2 Gate Expand

  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, not a pure 2-gate expand. Trades a few seconds of economy for protection vs proxy 2-gate / early aggression.

• ProtossPvP

  PvP - 4 Stalker Oracle into DT

  Detected if 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.

• ProtossPvP

  PvP - AlphaStar (4 Adept/Oracle)

  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. Hallucinated Oracles from a Sentry do not count.

• ProtossPvP

  PvP - Blink Stalker Style

  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.

• ProtossPvP

  PvP - Macro Transition (Unclassified)

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

• ProtossPvP

  PvP - Phoenix Style

  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.

• ProtossPvP

  PvP - Proxy 2 Gate

  Detected if a Gateway is built before 4:30 within 50 units of the OPPONENT's main base -- a proxied 2-Gate aggression.

• ProtossPvP

  PvP - Proxy Robo Opener

  Detected if a Robotics Facility is built before 6:30 within 50 units of the OPPONENT's main base -- a proxied Robo (Immortal / Warp Prism) opener.

• ProtossPvP

  PvP - Robo into Glaives

  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.

• ProtossPvP

  PvP - Adept Glaives

  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.

• ProtossPvP

  PvP - Rail's Blink Stalker (Robo 1st)

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

• ProtossPvP

  PvP - Standard Stargate Opener

  Detected if a Stargate is built before 6:30 in the player's own base (not proxied) -- the standard Stargate (Oracle / Phoenix) PvP opener.

• ProtossPvP

  PvP - Strange's 1 Gate Expand

  PvP 1-gate expand variant where exactly 1 Gateway is built before the natural Nexus and the first warp-in is a Sentry.

• ProtossPvT

  PvT - 2 Base Templar (Reactive/Delayed 3rd)

  Detected if Twilight Council is the FIRST tech building (before any Robotics Facility AND before any Stargate), a Templar Archives finishes BEFORE the third Nexus is taken, AND the player has 4-6 Gateways by 7:30 -- 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.

• ProtossPvT

  PvT - 2 Gate Blink (Fast 3rd Nexus)

  Detected if Twilight Council is the FIRST tech building (before Robo AND Stargate), Blink is researched by 8:00, the player has taken 3+ Nexuses, exactly 2 Gateways were STARTED before the 3rd Nexus, AND a Robotics Facility is up by 8:00 -- a fast-3rd 2-Gate Blink style with Robo 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.

• ProtossPvT

  PvT - 3 Gate Blink (Macro)

  Detected if Twilight Council goes BEFORE Robo and Stargate, Blink is researched 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.

• ProtossPvT

  PvT - 3 Gate Charge Opener

  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.

• ProtossPvT

  PvT - 4 Gate Blink

  Detected if Twilight Council goes BEFORE Robo and Stargate, Blink is researched 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.

• ProtossPvT

  PvT - 7 Gate Blink All-in

  Detected if Twilight Council is the FIRST tech building (before Robo AND Stargate), Blink is researched 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.

• ProtossPvT

  PvT - 8 Gate Charge All-in

  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).

• ProtossPvT

  PvT - DT Drop

  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 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. Slower openers that miss these windows are Robo First or late-tech DT support builds, not drop openers.

• ProtossPvT

  PvT - Macro Transition (Unclassified)

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

• ProtossPvT

  PvT - Phoenix Opener

  Detected if Stargate is the FIRST tech building (before Robo AND Twilight), 1+ real (non-hallucinated) Phoenix is on the field by 7:00, AND the player's second Gateway was built BEFORE the Robotics Facility -- a pure Stargate-first Phoenix opener. The Stargate-first ordering keeps Robo-first openers with a midgame Stargate + Phoenix harass off this label (those fall through to Robo First). Hallucinated Phoenix from Sentries do NOT count.

• ProtossPvT

  PvT - Phoenix into Robo

  Detected if Stargate is the FIRST tech building (before Robo AND Twilight), 1+ real (non-hallucinated) Phoenix is on the field by 7:00, AND a Robotics Facility is up by 8:00 -- a Stargate-first Phoenix opener that transitions into Robo tech. The Stargate-first ordering keeps Robo-first openers that ADD a midgame Stargate + real Phoenix off this label (those fall through to Robo First, since the OPENER was Robo). A Sentry's hallucinated Phoenix does NOT trigger this build.

• ProtossPvT

  PvT - Proxy Void Ray/Stargate

  Detected if a Stargate is built before the natural Nexus within 50 units of the OPPONENT's main -- a proxied Stargate (Void Ray) timing.

• ProtossPvT

  PvT - Stargate into Charge

  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.

• ProtossPvT

  PvT - Stargate into Glaives

  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.

• ProtossPvT

  PvT - Stargate into Blink

  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.

• ProtossPvT

  PvT - Stargate Opener

  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 / Phoenix into Robo / Phoenix Opener). A custom build rule can refine this further.

• ProtossPvT

  PvT - Robo First

  Detected if a Robotics Facility is built before 6:30 AND it is the FIRST tech building — Robo lands before any Twilight Council AND before any Stargate. 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.

• ProtossPvT

  PvT - Standard Charge Macro

  Detected if Charge is researched by 9:00, the player has taken 3+ Nexuses, AND Twilight Council is the FIRST tech building — Twilight goes down before any Robotics Facility AND before any Stargate. 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. 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.

• ProtossPvZ

  PvZ - 2 Stargate Phoenix

  Detected if the Stargate is the FIRST tech building (built before any Twilight Council / Dark Shrine / Robotics Facility), EXACTLY 2 Stargates and 2+ Nexuses are up by 10:00, 4+ Phoenix have been produced by 10:00 (Phoenix without a Stargate are ignored as hallucinations), AND the build did NOT commit to a tech-switch -- Glaives was NOT the first Twilight upgrade AND no Robotics Facility was built by 10:00. 3+ Stargates falls under PvZ - 3 Stargate Phoenix instead. A Stargate-into-Glaives hybrid (Phoenix as Glaive Adept support) tags as PvZ - Stargate into Glaives; a Stargate-into-Robo hybrid (Phoenix + Robo for Immortal / Observer / Disruptor) tags as PvZ - Stargate into Robo. The Glaives-first signal and the Robo presence are both strong intent markers -- the Phoenix count alone isn't enough to claim the pure 2 SG Phoenix label.

• ProtossPvZ

  PvZ - 2 Stargate Void Ray

  Detected if the Stargate is the FIRST tech building (built before any Twilight Council / Dark Shrine / Robotics Facility), 2+ Stargates and 2+ Nexuses are up by 10:00, 4+ Void Rays have been produced by 10:00 (Void Rays without a Stargate are ignored as hallucinations), AND the build did NOT commit to a tech-switch -- Glaives was NOT the first Twilight upgrade AND no Robotics Facility was built by 10:00. A Stargate-into-Glaives hybrid tags as PvZ - Stargate into Glaives; a Stargate-into-Robo hybrid tags as PvZ - Stargate into Robo.

• ProtossPvZ

  PvZ - 3 Stargate Phoenix

  Detected if the Stargate is the FIRST tech building (built before any Twilight Council / Dark Shrine / Robotics Facility), 3+ Stargates and 2+ Nexuses are up by 10:00, 4+ Phoenix have been produced by 10:00 (Phoenix without a Stargate are ignored as hallucinations), AND the build did NOT commit to a tech-switch -- Glaives was NOT the first Twilight upgrade AND no Robotics Facility was built by 10:00. A Stargate-into-Glaives hybrid tags as PvZ - Stargate into Glaives; a Stargate-into-Robo hybrid tags as PvZ - Stargate into Robo.

• ProtossPvZ

  PvZ - 7 Gate Glaive/Immortal All-in

  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.

• ProtossPvZ

  PvZ - AlphaStar Style (Oracle/Robo)

  Detected if the Stargate is the FIRST tech building (built before any Twilight Council / Dark Shrine / Robotics Facility), 2+ Oracles plus a Robotics Facility plus a Forge are all in place by 8:30, with 3+ Nexuses by 8:30 -- the AlphaStar Oracle / Robo / fast 3rd composition.

• ProtossPvZ

  PvZ - Archon Drop

  Detected if Stargate goes down before Twilight Council, a Templar Archives is up by 9:00, and 2+ Archons have been produced by 9:00 -- Stargate opener transitioning into Archon drops. Requires Templar Archives (or Dark Shrine for DT-Archon morph).

• ProtossPvZ

  PvZ - Blink Stalker All-in (2 Base)

  Detected if Blink is researched by 8:00, 5+ Gateways exist by 8:00, and the player has NOT built a Stargate or Dark Shrine by 8:00 -- a 2-base Blink all-in.

• ProtossPvZ

  PvZ - Carrier Rush

  Detected if the Stargate is the FIRST tech building (built before any Twilight Council / Dark Shrine / Robotics Facility), a Fleet Beacon is up by 10:00, and at least 1 Carrier has been produced by 10:00 -- a true Stargate-opener Carrier rush. A DT or Glaives opener that adds a Stargate / Fleet Beacon / Carrier late tags as PvZ - DT Opener or PvZ - Adept Glaives instead. Carriers without a Stargate + Fleet Beacon are treated as hallucinations.

• ProtossPvZ

  PvZ - DT drop into Archon Drop

  Detected if Twilight Council goes down before Dark Shrine, a Dark Shrine AND a Robotics Facility are up by 9:00, 3+ Dark Templar are produced by 9:00, and a Warp Prism is on the field by 9:00.

• ProtossPvZ

  PvZ - Macro Transition (Unclassified)

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

• ProtossPvZ

  PvZ - Rail's Disruptor Drop

  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.

• ProtossPvZ

  PvZ - Robo Opener

  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.

• ProtossPvZ

  PvZ - Standard Blink Macro

  Detected if Stargate goes down before Twilight Council, Blink is researched by 10:00, and 3+ Nexuses are taken by 9:00 -- Stargate opener into 3-base Blink macro.

• ProtossPvZ

  PvZ - Standard charge Macro

  Detected if Stargate goes down before Twilight Council, Charge is researched by 9:00, and 3+ Nexuses are taken by 9:00 -- Stargate opener into 3-base Chargelot macro.

• ProtossPvZ

  PvZ - Stargate into Glaives

  Detected if a Stargate is built BEFORE any Twilight Council (pure ordering, no time threshold -- a slow Stargate opener that transitioned to Glaives still counts) and the FIRST upgrade researched out of the Twilight Council is Resonating Glaives (Glaives starts BEFORE Blink and BEFORE Charge) -- a Phoenix or Oracle into Glaive Adept timing. Classification is purely order-based with no Gateway-count window: the Glaives-first signal IS the build, whether the player backs it with a handful of Gateways or warps a heavy 9+ Gateway mass-Adept timing. That Glaives-first ordering is what separates this from Stargate into Blink (Blink researched first) and is what keeps a Glaives-then-Blink build from being demoted to Standard Blink Macro.

• ProtossPvZ

  PvZ - Adept Glaives (No Robo)

  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, so a slow Twilight with nothing else committed first still qualifies), the FIRST upgrade researched out of the Twilight Council is Resonating Glaives (Glaives starts BEFORE Blink and BEFORE Charge), 4-8 Gateways exist by 6:00, AND no Robotics Facility is built -- a pure Gateway Adept Glaive Timing without Robo support.

• ProtossPvZ

  PvZ - Adept Glaives (Robo)

  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), 4-8 Gateways exist by 6:00, AND a Robotics Facility is built (after Twilight, as Observer / Immortal support) -- the Robo variant of Adept Glaive Timing.

• ProtossPvZ

  PvZ - Tempest Rush

  Detected if the Stargate is the FIRST tech building (built before any Twilight Council / Dark Shrine / Robotics Facility), a Fleet Beacon is up by 10:00, and at least 1 Tempest has been produced by 10:00 -- long-range Tempest harass / siege opened off a Stargate.

• ProtossPvZ

  PvZ - DT Opener

  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.

• ProtossPvZ

  PvZ - Stargate into Robo

  Detected if the Stargate is the FIRST tech building (built BEFORE any Twilight Council / Dark Shrine / Robotics Facility), at least 1 real Phoenix / Oracle / Void Ray is on the field by 10:00 (confirms the player actually used the Stargate, not just dropped one), AND a Robotics Facility is built by 10:00. The classic Stargate-into-Robo transition: Phoenix / Oracle harass off the opener, Robo follow-up for Immortal / Observer / Disruptor support. Sits between the pure 2/3 SG Phoenix rules (no Robo allowed) and the catch-all PvZ - Stargate Opener -- if you opened Stargate and added Robo, this is your label. PvZ counterpart of the PvT - Phoenix into Robo rule (renamed in PvZ to use the generic 'Stargate into' phrasing because the rule accepts any Stargate unit -- Phoenix / Oracle / Void Ray -- not just Phoenix specifically).

• ProtossPvZ

  PvZ - Stargate Opener

  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.

• Terran

  Terran - 1-1-1 One Base

  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.

• Terran

  Terran - 1-1-1 Standard

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

• Terran

  Terran - 2 Gas 3 Reaper 2 Hellion

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

• Terran

  Terran - 2-3 Rax Reaper rush

  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.

• Terran

  Terran - 3 Rax

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

• Terran

  Terran - 3-4 Rax Marine rush

  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.

• Terran

  Terran - BC Rush

  Detected if a Fusion Core is built before 6:30.

• Terran

  Terran - Banshee Rush

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

• Terran

  Terran - Bio Comp

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

• Terran

  Terran - Cyclone Rush

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

• Terran

  Terran - Fast 3 CC

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

• Terran

  Terran - Ghost Rush

  Detected if Ghost Academy is built within first 6:30 of the game.

• Terran

  Terran - Hellbat All-in

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

• Terran

  Terran - Mech Comp

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

• Terran

  Terran - Proxy 1-1-1

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

• Terran

  Terran - Proxy Starport Hellion Drop

  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.

• Terran

  Terran - Proxy Rax

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

• Terran

  Terran - SkyTerran

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

• Terran

  Terran - Standard Bio Tank

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

• Terran

  Terran - Standard Play (Unclassified)

  Catch-all for unclassified Terran games.

• Terran

  Terran - Widow Mine Drop

  Detected if Medivac and multiple widow mines are built after second CC within the first 6:30.

• Terran

  Terran - Widow Mine Drop into Thor Rush

  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.

• Terran

  Terran - Widow Upgraded Mine Cheese

  Detected if a Medivac and 2+ Widow Mines are built BEFORE the second Command Center -- a 1-base Widow Mine drop cheese.

• TerranTvP

  TvP - Proxy 4 Rax Reaper

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

• TerranTvP

  TvP - Proxy Marauder

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

• TerranTvP

  TvP - Cyclone Push

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

• TerranTvP

  TvP - 1-1-1 Cloak Banshee

  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.

• TerranTvP

  TvP - 3 Rax Marine

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

• TerranTvP

  TvP - Battlecruiser Rush

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

• TerranTvP

  TvP - Tank/Thor Mech

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

• TerranTvP

  TvP - Widow Mine Drop

  Detected when a Marine ball with 2+ Widow Mines and a Medivac runs mobile mine drops into the Protoss mineral lines.

• TerranTvP

  TvP - 2-1-1 Reaper Expand

  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.

• TerranTvP

  TvP - 2 Base Tank Push

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

• TerranTvP

  TvP - Fast 3 CC Bio

  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.

• TerranTvT

  TvT - Proxy 4 Rax Reaper

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

• TerranTvT

  TvT - Proxy Marauder

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

• TerranTvT

  TvT - Cyclone Push

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

• TerranTvT

  TvT - 1-1-1 Cloak Banshee

  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.

• TerranTvT

  TvT - Banshee into Raven

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

• TerranTvT

  TvT - Battlecruiser Rush

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

• TerranTvT

  TvT - Tank/Thor Mech

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

• TerranTvT

  TvT - Reaper Expand into Tank/Viking

  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.

• TerranTvT

  TvT - 2-1-1 Marine Tank

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

• TerranTvT

  TvT - 3 Rax Marine

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

• TerranTvT

  TvT - Mass Viking Air

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

• TerranTvZ

  TvZ - Proxy 4 Rax Reaper

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

• TerranTvZ

  TvZ - 1-1-1 Banshee

  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.

• TerranTvZ

  TvZ - 3 Rax Marine

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

• TerranTvZ

  TvZ - Reaper Hellion Expand

  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.

• TerranTvZ

  TvZ - 2 Base Hellbat Thor

  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.

• TerranTvZ

  TvZ - 2-1-1 Marine Hellbat Timing

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

• TerranTvZ

  TvZ - Battlecruiser Mech

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

• TerranTvZ

  TvZ - Hellion Liberator

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

• TerranTvZ

  TvZ - 2-1-1 Marine Drop

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

• TerranTvZ

  TvZ - Widow Mine Marine

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

• TerranTvZ

  TvZ - 3 CC Bio

  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.

• Zerg

  Zerg - 1 Base Roach Rush

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

• Zerg

  Zerg - 12 Pool

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

• Zerg

  Zerg - 13/12 Baneling Bust

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

• Zerg

  Zerg - 13/12 Speedling Aggression

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

• Zerg

  Zerg - 17 Hatch 18 Gas 17 Pool

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

• Zerg

  Zerg - 2 Base Muta Rush

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

• Zerg

  Zerg - 2 Base Nydus

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

• Zerg

  Zerg - 2 Base Roach/Ravager All-in

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

• Zerg

  Zerg - 3 Base Macro (Hatch First)

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

• Zerg

  Zerg - 3 Base Macro (Pool First)

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

• Zerg

  Zerg - 3 Hatch Before Pool

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

• Zerg

  Zerg - 3 Hatch Ling Flood

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

• Zerg

  Zerg - Early Pool (14/14 or 15 Pool)

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

• Zerg

  Zerg - Hydra Comp

  Mid/Late game composition fallback featuring Hydralisks.

• Zerg

  Zerg - Muta/Ling/Bane Comp

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

• Zerg

  Zerg - Pool First Opener

  Generic Pool first opener that transitions into standard macro.

• Zerg

  Zerg - Proxy Hatch

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

• Zerg

  Zerg - Roach/Ravager Comp

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

• Zerg

  Zerg - Standard Play (Unclassified)

  Catch-all for unclassified Zerg games.

• ZergZvP

  ZvP - 12 Pool Rush

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

• ZergZvP

  ZvP - Ling Bane Bust

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

• ZergZvP

  ZvP - 2 Base Roach Ravager 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.

• ZergZvP

  ZvP - 2 Base Nydus

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

• ZergZvP

  ZvP - Hydra Timing (3 Base)

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

• ZergZvP

  ZvP - Lurker Contain

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

• ZergZvP

  ZvP - Ling Bane Muta

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

• ZergZvP

  ZvP - Mutalisk Harass

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

• ZergZvP

  ZvP - Speedling Flood

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

• ZergZvP

  ZvP - Hatch First Macro

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

• ZergZvT

  ZvT - Ling Bane Bust

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

• ZergZvT

  ZvT - 2 Base Roach Ravager Timing

  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.

• ZergZvT

  ZvT - 2 Base Nydus

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

• ZergZvT

  ZvT - Mass Queen Defensive

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

• ZergZvT

  ZvT - Lurker Contain

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

• ZergZvT

  ZvT - 3 Hatch Ling Bane Muta

  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.

• ZergZvT

  ZvT - Mass Muta Harass

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

• ZergZvT

  ZvT - Roach Hydra

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

• ZergZvT

  ZvT - 3 Base Ling Flood

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

• ZergZvT

  ZvT - Hatch First Macro

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

• ZergZvZ

  ZvZ - 12 Pool into Baneling

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

• ZergZvZ

  ZvZ - 12 Pool Speedling

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

• ZergZvZ

  ZvZ - Ling Bane All-in

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

• ZergZvZ

  ZvZ - Roach Ravager

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

• ZergZvZ

  ZvZ - Roach Aggression

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

• ZergZvZ

  ZvZ - 2 Base Nydus

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

• ZergZvZ

  ZvZ - Mutalisk vs Mutalisk

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

• ZergZvZ

  ZvZ - Hatch First Muta

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

• ZergZvZ

  ZvZ - Zergling Flood

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

• ZergZvZ

  ZvZ - Drone Macro (Hatch First)

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

• ProtossPvP

  PvP - Game Too Short

  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.

• ProtossPvT

  PvT - Game Too Short

  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.

• ProtossPvZ

  PvZ - Game Too Short

  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.

• TerranTvP

  TvP - Game Too Short

  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.

• TerranTvT

  TvT - Game Too Short

  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.

• TerranTvZ

  TvZ - Game Too Short

  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.

• ZergZvP

  ZvP - Game Too Short

  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.

• ZergZvT

  ZvT - Game Too Short

  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.

• ZergZvZ

  ZvZ - Game Too Short

  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.