Follow us on Twitter @LiquipediaSC2 if you'd like to be kept up to date on all things StarCraft II!
Download the Liquipedia app here!Download the Liquipedia app to follow StarCraft II!Want personalized updates on StarCraft II esports? Download the Liquipedia app on iOS or Android to never miss your favorite tournaments and matches!

Forge Fast Expansion (vs. Zerg)

From Liquipedia StarCraft 2 Wiki
This strategy is for a previous expansion of the game.
[e][h]ProtossForge Fast Expansion
"Forge fast expand or die trying!" - NaNiwa
Strategy Information
Matchups:
PvZ
Type:
Opening

Overview[edit]

This opening relies on Photon Cannon(s) and a wall-in to hold off any Zergling pokes that the Zerg opponent might attempt. This prevents the Zerg from being able to pressure the early expansion timing, allowing the Protoss player to Tech up and boost their economy at the same time. The strength of this build is the sheer number of transitions that are possible. As Stargate transitions, Robotics Facility transitions and fast Forge/Twilight Council upgraded Gateway pushes are all possibilities, it can be very hard for Zerg to correctly respond.

Build Order[edit]

Forge Nexus
Nexus First

Notes[edit]

  • Work out the placements to complete the natural wall-in in three buildings beforehand.
  • The Photon Cannon is either built immediately once the Forge finishes or delayed until after the Gateway.
  • Forge builds can go up to three Photon Cannons before it starts biting too hard into Gateway unit production, however the standard is to build only one Cannon as long as you haven't scouted any signs of aggression.

Scouting[edit]

  • Scout with the Probe that builds your first Pylon.
  • If you're going for a Forge first build, you can block a Hatchery First opening from your opponent with a Pylon. If you let the Pylon finish then you'll either force the Zerg player to expand at another location (which will be less safe), force them to wait until Zerglings are out to expand, or force them to pull Drones to kill the Pylon. All of these things slow the Zerg down, which is what you need to do if they are planning to go Hatchery First. It is also possible to Cannon Rush a Hatchery First build if you went for the Forge first opening.
  • Do not block a Hatchery First opening if you're trying to go Nexus first. You have no need to delay their economy since your Nexus will be going down early, and you also have no option to Cannon Rush the opponent.
  • If the Zerg opponent takes gas before expanding then this can be indicative of an all-in. However, it could also indicate a Speedling Expand. If the Zerg mines more than 100 gas from their geyser (the amount of gas required for Metabolic Boost), or if the Zerg does not take a third base by the 5 minute mark, they might be trying to all-in you. In this case, add one or two additional Cannons and Chrono Boost Sentries from your Gateway ready for the attack. If no attack comes, use Hallucinations to scout what the Zerg is doing and consider looking around the map for "ninja" expansions.

Transitions[edit]

Gateway Timing-Attacks[edit]

  • One option is to go for a 4 Gate +1 timing-attack that hits as soon as Warpgate Research is completed. A guide for this type of pressure can be found here.
  • Another option is to go for a Gateway all-in. This may or may not include Forge upgrades dependent on the timing you're trying to hit, and can have anywhere from 6-8 Gateways involved. One example would be MC's 7 Gate 1 Gas All-In.
  • A third option is to involve Twilight Council upgrades, with Blink being the most commonly favored option. Examples of this include the 7 Gate +2 Blink Stalker All-In.

Stargate Transitions[edit]

  • You can use either one or two Stargates depending on the transition you want to make later in the game.
  • One example of a Stargate transition would be the Voidray/Chargelot/Templar style popularised by sOs and NaNiwa.
  • It is also possible to play a "Sky Protoss" style after a FFE, although this is very rarely seen at the highest level. A guide to this style can be found here.

Robotics Facility Transitions[edit]

Further Strategies[edit]