Bisu Build

From Liquipedia Starcraft Wiki

Jump to: navigation, search
Image:Picon.pngBisu Build
Dark Protoss
Matchups: PvZ
Type: Opening
Creator: Image:Picon_small.pngDaezanG
Popularized By: Image:Picon_small.pngBisu



The talk about 'The Bisu Build' began after the finals of GOMTV S1 MSL in which Bisu defeated Savior 3-0 in one of the most influential series in all of Starcraft. Savior entered the fight as the reigning Bonjwa and scourge of all Protoss, and left humiliated and broken. This article tries to model the specimens of this build. Occasionally it is also referred to as the "Beesuit".

Contents

[edit] Previous Build Order

The Bisu Build uses the Protoss Fast Expansion into Stargate, described in the PvZ Guide. Other branches include Sair/Reaver and +1 Zealot/Archon push. When starting into this branch, you should have:

  • Two Nexuses pumping Probes
  • One Gateway + One Forge blocking the entrance to your Natural Expansion.
  • Assimilator at your main base
  • Cybernetics Core
  • Assimilator at Expansion. - Since this is a very gas heavy strat, you need to incorporate this into your Initial Build Order.
  • Stargate

An exemplary Build Order if the Zerg plays 12 Hatch (compiled from Bisu vs. Savior on Blitz X)

  • 8 - Pylon (send this Probe to scout)
  • 12 - Nexus
  • 13 - Forge
  • 15 - Pylon
  • 17 - Gateway
  • 18 - Cannon
  • 20 - Assimilator
  • 23 - Cybernetics Core

(add Pylons as needed)

  • ~31 - Assimilator at Natural
  • ~31 - Stargate (build two Corsairs when it finishes)

[edit] Transition

Your next move is:

  • Build 1st Corsair.
  • First 100 gas - Citadel of Adun.
  • Build 2nd Corsair
  • Gateway
  • When Citadel finishes, get Templar Archives.
  • When Archives finish, build two Dark Templar
  • At least two more Gateways

Once your DT are out, use them in the same manner as the Corsairs. They are not intended to kill the Zerg. They scout and control the map. Look for openings and slip them through. You have to use all this reconnaissance you get to find points to harass and to identify vulnerable phases in the Zerg's build, e.g. when he is overextending his macro.

[edit] Gameplay

  • Corsairs have three uses (ordered from most to least important). This order means, you should almost never sacrifice a Corsair in order to kill an Overlord.
  1. Scout
  2. Fend off Mutalisks in combination with cannons. Place your corsairs above your Nexus, close to the Cannons. Dodge Scourge. 3-4 Corsairs with Cannons can hold off most early Mutalisk attacks.
  3. Hunt Overlords.
  • Immediately get Speedzeal Tech
  • You want to harass a Zerg that took 2-3 bases and is not all-inning you. Send out small groups of units to do damage, similar to a speedzeal rush, only that you are forcing the Zerg to be attentive of all the locations where you harass (DT + Corsair + Speedzeals)
  • When you have done sufficient damage, take a third. Keep harassing and gather for the final strike, to overrun the Zerg. Keep exploiting holes that your Corsairs cut by sending in DTs. Incorporate Shuttles.
  • Due to these many objectives, multitasking skill is very necessary.

[edit] Adaptation:

[edit] Mutalisk

Continue to make Corsairs, upgrade +1 Air Attack, use your Templar Tech to get Archons. Keep your units, especially unmorphed Templars, together and near defenses. Do not let roaming mutas pick-off stray units when possible.

[edit] 5 Hatch Hydra

Limit Corsair production to 1-2 with the sole intent of using them as scouts. Dedicate building Photon Cannons at your natural expansion and prohibit building any at your main until you notice your opponent is transitioning to a Spire. Prioritize warping a Templar Archives over Zealot Speed (but obtain them both eventually) and train 1 High Templar, research Psi Storm, then 1-2 additional HTs. Simulataneously, spend minerals on 3-5 Cannnons (ideally positioned behind a single wall of Pylons) and then on Zealots. Also research +50 energy for the HTs as a supplement to their Psi Storm capacity. The overall premise of this variant is to focus on front door defense while buying time to charge your HTs and train a dominant Speedlot/Archon force. You'll want to delay getting the Robotics Facility until your opponent introduces Lurkers.

Typically (but not always) a 5-Hatch Hydra break will occur at 2 time frames:

1) 18-24 Hydras with Speed Upgraded Overlords (with possible +1 attack). By that time you should have HT's with ample energy to blanket the battlefield with Storms. It's imperative to keep your HTs positioned near Cannons to prevent Zergling surrounds and to hide their energy count from your opponent.

2) 12-16 Speed+Ranged Hydras without overlord speed. If you scout effectively and determine the opponent is attempting to the break without mobile detection then capitalize by training 2-3 Dark Templars and regain map control (temporarily) buying time for your HT's to charge. Prior to this break, it is essential to clear any stray Slow Overlords within the immediate proximity of your base.

Some important refining micro concepts for utilizing Psi Storm are Storm Accuracy and Storm Prediction.

Storm Accuracy = 2 x # of Hydras targeted - # of Zealots targeted. Ideally you want your Storm Accuracy to be as positive as possible. Mathematically, Zealots and Hydras require the same resource quantity to train while Zealots have double the HP of Hydras. Therefore, it is statistically twice as more benefical to target an enemy Hydra than it is detrimental to target a friendly Zealot. In this variant, Hydras and Zealots are by far the two most common receipients of Storm.

Storm Prediction = Your ability to predict where your opponent will move the Hydras to dodge active Psi Storm(s) while proactively Storming their new destination. Please note that Storm does not stack (meaning 3 Psi Storms in the same area does not cause triple damage) and therefore the optimal use involves releasing it in volleys to ensure maximum damage is being inflicted.

[edit] Lurker Contain

See Lurker Contain

[edit] Notable Maps

This build order only works on maps where you can shut off your main and natural with a single wall. It is favorable to use it on 2 player maps, as you need to know the Zerg's build in order to have the optimal timing.

[edit] Counters to expect

[edit] Notable Games

[edit] Replays

[edit] VODs

Retrieved from "http://wiki.teamliquid.net/starcraft/Bisu_Build"
Personal tools