| Hello! Last weekend me and a friend decided to work on a micro bot to push the potential of the in-game units to the limits. As of today, we've implemented two common scenarios: bum rushing siege tanks with zerglings, and splitting Marines. Our bot is now capable of : 40 speed banelings vs. 20 marines (no marines lost) 20 spread siege tanks vs. 100 zerglings (all tanks dead, 19 zergling survivors) To liven things up we made videos with footage using the bot, combined with some decent music and scenes from GSL. Here's the scenarios: |
Friday, April 15, 2011
Sunday, February 6, 2011
Tuesday, October 19, 2010
Overview
This is a 1 base roach build order
Goal
To bust through a wall and decimate the opponent's mineral line to get ahead economically or even out, considering the heavy early investment into army.
Build Order
Build Order
- 9/10 Overlord
- (scout with 10th)
- 13/18 Spawning Pool
- 15/18 Extractor (+3 Drones asap)
- 16/18 Roach Warren
- 15/18 Queen
- 17/18 2 Overlords (resist the urge to make that one drone; you need all larvae for 8 roaches)
- @100% Queen injects larvae (inject twice, then creep tumor 3rd time around. You don't have the minerals to use larvae while getting hatch and lair)
- @100% Roach Warren: 3 Roaches, send to choke ASAP.
- @Larvae Pop: 5 more Roaches (move out to pressure when finished)
- 33/34 Overlord
- @ 100 : Metabolic Boost
- @Larvae Pop: make 7 pairs of Zerglings and rally to Roaches (this leaves just enough minerals for Lair on 100 gas)
- @ 100 : Lair
- @ ~200 minerals: send out drone to make Hatchery
- pump drones and overlords
- get Extractors depending on your lair tech plan.
Execution
- The way to attack is by moving your 8 roaches up the ramp and sniping a pylon or a supply depot then allowing your lings to run in. If you manage to destroy the garrison of troops behind the wall, leave a few roaches there to prevent any sneaking out and send the rest to the mineral line to kill as many drones as possible. But it is important to keep in mind macroing and making a metric buttload of drones is more important than controlling your units at this point, since the units have paid for themselves already. Your economic advantage is what wins you the game usually.
Note: This build does cut quite a few drones early on, so if you don't think you can break the ramp, preserve your units, and retreat to set up to defense at your natural. If you commit to the attack and it fails you will be hard-pressed to make enough units to defend and still have an economy.
Adaptation
You can opt to skip zergling speed and instead get a faster lair, but any follow ups with speedlings will not be so "speedy"
]Maps
Pro features
When to do this build:
- 2 player maps
- Steppes of War
- Blistering sands (you can knock at the back door)
- Xel-Naga Caverns
- Your opponent is walling in and teching (this includes a fast 4-gate that cuts sentries and stalkers early on)
- Your opponent is 2-gateing (see above) on close positions (also see above)
Con features
When not to do this build :
- Your opponent is getting sizable army early on of sentries and stalkers or 3-raxing (You can sometimes do it vs a marine heavy 3 rax)
- If your opponent is 2-gating defend first then counter (This build is very 2-gate safe)
- You are on Scrap Station, Desert Oasis (Seriously, who hasn't thumbed down this one?), Kulas Ravine, or Delta Quadrant vs T (At least I have had little luck with it)
- They are going Speed Reaper
Thursday, October 14, 2010
Tree tag
Hello everyone. I will be writing about my custom map in SC2, Tree tag. Its almost a clone of the Warcraft 3 map of the same name. I wanted to port it because it was such a great map.
Description:
Terrans are coming to invade your Taldarim homeworld. You must prepare defences as a probe and hide until your mothership arrives to fend off the attack.
Protoss players start with a Probe which can summon a variety of structures.
Terrans: You start with an Odin/Thor/Loki. Your task is to kill off all the probes so you can claim the Terrazine Gas on the planet.
Captured/Dead probes are placed in the middle of the map. They can be rescued by a team mate.
Terrans can win the game by capturing all probes.
Search Tree tag Alpha in NA or SEA server to play this map.
Feedback is much appreciated.
Description:
Terrans are coming to invade your Taldarim homeworld. You must prepare defences as a probe and hide until your mothership arrives to fend off the attack.
Protoss players start with a Probe which can summon a variety of structures.
Terrans: You start with an Odin/Thor/Loki. Your task is to kill off all the probes so you can claim the Terrazine Gas on the planet.
Captured/Dead probes are placed in the middle of the map. They can be rescued by a team mate.
Terrans can win the game by capturing all probes.
Search Tree tag Alpha in NA or SEA server to play this map.
Feedback is much appreciated.
Sunday, October 10, 2010
Patch 1.2 Coming soon?
Some notes from Justin Bowder, the lead for Starcraft 2.
The balance changes in our next patch will primarily focus on improving the zerg.
Here are a few of the changes we currently have planned:
Here are a few of the changes we currently have planned:
• We're increasing roach range. This will allow roaches to be more effective in large groups, giving the zerg more options in the mid to end game.
• Fungal Growth will now prevent Blink, which will give zerg a way to stop endlessly Blinking stalkers which can be very challenging to deal with in large numbers.
• The Barracks are going to require a Supply Depot, which will impact a lot of early terran reaper pushes.
• The reaper speed upgrade will require the Factory, which is meant to weaken a lot of the early terran reaper attacks that dominate so many matches, especially in team games.
• We're making a number of increases to the health of zerg buildings, which will make the very vulnerable zerg technology structures more resistant to raids. We don't expect these hit point changes to have a super significant impact on the game, but the current numbers felt way too low.
• Fungal Growth will now prevent Blink, which will give zerg a way to stop endlessly Blinking stalkers which can be very challenging to deal with in large numbers.
• The Barracks are going to require a Supply Depot, which will impact a lot of early terran reaper pushes.
• The reaper speed upgrade will require the Factory, which is meant to weaken a lot of the early terran reaper attacks that dominate so many matches, especially in team games.
• We're making a number of increases to the health of zerg buildings, which will make the very vulnerable zerg technology structures more resistant to raids. We don't expect these hit point changes to have a super significant impact on the game, but the current numbers felt way too low.
From these changes, if they are all implemented, I think reapers would be useless, unless they make another use for them.
Sunday, October 3, 2010
Must Watch GSL final Game
GSL final game NO.2 between FruitDealer (Z) and Hopetorture(T)
Watch the rest of it here http://www.justin.tv/seriouscallersonly/videos
Watch the rest of it here http://www.justin.tv/seriouscallersonly/videos
Friday, October 1, 2010
IdrA vs Boxer
The one and Only IdrA versus the Pro from Broodwar, Boxer on Xel Naga Caverns.
I think Boxer would have done well if he was able to use those minerals that he saved. He definitely needed more banshees earlier. But he is just learning SC2, and i hope he starts playing it professionally.
I think Boxer would have done well if he was able to use those minerals that he saved. He definitely needed more banshees earlier. But he is just learning SC2, and i hope he starts playing it professionally.
Thursday, September 30, 2010
Cool aka Fruit Seller aka FruitDealer
So there's this guy named Cool. He is playing in GSL at the moment and currently in the semi finals against 3 terrans. He is an amazing player because he plays Zerg so well. This is all I could find of his matches in GSL. They are very entertaining to watch, and i hope he becomes GSL champion, although unlikely.
Monday, September 27, 2010
Patch 1.1.1 Live!
StarCraft II: Wings of Liberty – Patch 1.1.1
Bug Fixes
* Fixed an issue where Ultralisk cleave range was being unintentionally extended by larger targets.
* Fixed an issue where the Phoenix's Graviton Beam was automatically canceled if you used it just after the Phoenix reached 50 energy.
* Fixed an issue where queuing Return Cargo on a worker would cause it to ignore the built-in delay after it finished gathering.
* Fixed an issue where players watching older replays or saved games would experience stuttering.
* Fixed an issue where some Mac users were unable to join games properly.
So there is no more mineral boosting, and Ultras Splash bug. Sadface.jpg
Bug Fixes
* Fixed an issue where Ultralisk cleave range was being unintentionally extended by larger targets.
* Fixed an issue where the Phoenix's Graviton Beam was automatically canceled if you used it just after the Phoenix reached 50 energy.
* Fixed an issue where queuing Return Cargo on a worker would cause it to ignore the built-in delay after it finished gathering.
* Fixed an issue where players watching older replays or saved games would experience stuttering.
* Fixed an issue where some Mac users were unable to join games properly.
So there is no more mineral boosting, and Ultras Splash bug. Sadface.jpg
Saturday, September 25, 2010
Muta Magic box
Many Zerg players still see Thors as a hard counter to a Mutalisk build. The Mutalisks' tendency to group up into a tightly packed ball combined with the Thor's aerial splash damage and bonus damage against Light units can make quick work of a pack of Mutas. However, it doesn't have to be that way. A little extra micromanagement with your Mutalisks can give you the edge in these encounters.If you're a Zerg player that has used Mutalisks, you have surely noticed how eager they are to pile on top of one another. When you give them an attack command, they all fly toward the enemy and stop at the same exact point and bunch up. Since they're aerial units, they are capable of stacking up on top of one another. It's easy to create a situation where all of your Mutas are sent to attack a specific unit and they all start attacking from the exact same spot on the map and then slowly drift apart. If your Terran opponent has a mech build with Thors (rather than an infantry MnM build), that piled up formation puts all of your Mutalisks at risk. They take a staggering amount of excess splash damage simply because of how the units move. Once the Mutalisks have finished drifting apart, the splash damage goes down significantly. Careful movement can prevent that initial volley of splash damage from ever happening.
The goal of the magic box is to let your Mutalisks complete the "drift phase" of their movement far away from your opponent. Once they've drifted apart, they will hold that formation as they fly around the map unless you issue a new attack command or tell them to move to a point within their formation.
Select your Mutalisks (which you've placed into a control group, right?) and click in the center of them to force then to clump up. They will clump and then drift apart. Once they've stopped drifting and are in a wide spread formation, this is the formation you want to keep them in. They will hold this formation as you move them around the map, as long as you take care not to issue a move order within their formation give them a specific attack target. To attack with your Mutalisks, do not issue an attack command. Fly your Mutalisks over your target, much like you would aim Zerglings past an enemy army to surround them, and hit Hold Position. The Mutalisks will hold their formation and automatically attack targets beneath them. If those targets are Thors, the Mutalisks will not suffer any splash damage whatsoever. This works best with a group of less than 40 Mutalisks. Between 36 and 40 is where the formation starts to break down, and they start bumping into each other again.
This technique does not turn Mutalisks into a hard counter for Thors, but it does significantly reduce the threat that Thors pose to your Mutalisks. Getting enough Mutas to take down a pack of Thors is still going to be one of the most expensive ways to try and bring down those Thors. The magic box technique could potentially save you from needing to make a full tech switch, however. If the magic box sounds complicated, don't worry, it can sound much more difficult than it actually is. To see the magic box in motion, check out the tutorial video from PsyStarcraft which is embedded below.
Friday, September 24, 2010
Mineral Boosting Patch 1.1
Basically, when your worker finishes gathering minerals, they stand for half a second before turning around to bring it back to your base. sockfolder discovered that if you press the Return Cargo button on the worker, it will immediately turn around, thus giving you minerals faster. So to make this trick work well, you need to queue up the commands for each worker.
Select a worker that is holding minerals and follow below:
Hold Shift
Press C (Return Cargo)
Right click the mineral patch it was gathering from
Repeat steps 2 and 3 quickly
Be sure the last command queued up is the right click
Repeat the whole process for the other workers
According to sockfolder, after 5 minutes of normal mining, a worker would gather 495 minerals. A worker with boosted mining, would gather 530 minerals, which is 7% more! Check out the below video
Select a worker that is holding minerals and follow below:
Hold Shift
Press C (Return Cargo)
Right click the mineral patch it was gathering from
Repeat steps 2 and 3 quickly
Be sure the last command queued up is the right click
Repeat the whole process for the other workers
According to sockfolder, after 5 minutes of normal mining, a worker would gather 495 minerals. A worker with boosted mining, would gather 530 minerals, which is 7% more! Check out the below video
Wednesday, September 22, 2010
Patch 1.1 Zerg Bug
Many of you were saying nothing has happened to Zerg, which is false.
Ultralisk's ram ability has been removed and now does splash damage towards buildings, which has created a bug that increases the range of the Ultralisk to 7 when hitting a Planetary fortress or some other large building.
Ultralisk's ram ability has been removed and now does splash damage towards buildings, which has created a bug that increases the range of the Ultralisk to 7 when hitting a Planetary fortress or some other large building.
Starcraft 2 Patch 1.1 Finally Out!
Looks like Zerg is getting a buff while terran and protoss will be getting nerfs. My prediction is that Terran Bio ball will still own early and mid game as Protoss has had a pretty significant nerf while not much has happened to zerg in the early-mid game. Also the gameclock is pretty cool.
StarCraft II: Wings of Liberty - Patch 1.1.0
To get the latest news and interact with the community, visit our StarCraft II website. Be sure to check out our Game Guide for an in-depth look at StarCraft II gameplay. We wish you all the best on your journeys through the embattled Koprulu Sector!
General
* The Standard (US) and Standard for Lefties (US) hotkey configurations are now available in all regions.
* A new game clock has been added. Players can now instantly see how long they've been in their current mission or match. This feature can be turned on or off in the Gameplay Options menu.
* A new Quick Save option is now available for the single-player campaign. Players can now quickly save their mission progress by pressing Ctrl + Q.
* A new System Panel has been added. Players can now view their local time and FPS while in game by mousing over the Menu (F10) button in the upper-left hand corner of the game screen. Laptop users can also view Wi-Fi signal strength and battery levels.
* Sight granted by death reveal no longer lifts Fog of War. Units revealed in this manner are not targetable.
* (Mac only) Moved StarCraft II data files and settings from the Documents folder into the Application Support folder.
* Support for NVIDIA 3D Vision has been added. To experience StarCraft II: Wings of Liberty in 3D on your desktop or notebook, you will need 3D Vision. For more information, visitwww.nvidia.com/Starcraft3D
Balance Changes
* PROTOSS
o Zealot
+ Build time increased from 33 to 38.
+ Warp Gate cooldown increased from 23 to 28.
* TERRAN
o Battlecruiser
+ Ground damage decreased from 10 to 8.
o Bunker
+ Build time increased from 30 to 35.
o Reaper
+ Build time increased from 40 to 45.
o Siege Tank
+ Siege mode damage changed from 50 to 35 (+15 armored).
+ Upgrade damage changed from +5 to +3 (+2 armored).
* ZERG
o Ultralisk
+ Ram ability removed. Ultralisk will now use normal attack against buildings.
+ Damage decreased from 15 (+25 armored) to 15 (+20 armored).
* Maps
o Desert Oasis
+ Destructible Rocks have been added to make natural expansions easier to protect.
+ Center Xel'Naga Tower area has been narrowed.
StarCraft II Editor Improvements
* Added new requirement types: Odd, Divide, Mod, Multiply.
* Added a chance field to effect data.
* Added support for the Slider dialog control type.
* Added a trigger to deal damage from a unit.
* Added a trigger event response to provide the amount a player or unit property changes.
* Added a trigger event when an effect executes.
* New Trigger Editor functions:
o Save Data Conversation State Value (Action).
o Load Data Conversation State Value (Action).
o Players On Team (returns Player Group associated with teams in game lobby).
o Unit Owner Changes (Event).
o Old Unit Owner (returns player ID in response to Unit Owner Changes).
o New Unit Owner (returns player ID in response to Unit Owner Changes).
* XP, Level, and Bounty unit properties can now be modified by triggers.
* Banks now save/restore XP, learned abilities, and items.
* Message Window now includes a time stamp for each message.
* An actor event is now dispatched when a missile cannot hit its target.
* When loading documents with Battle.net-only dependencies, you will now be prompted to log in and download the dependency data, rather than failing to load.
* Game variants now automatically use the default melee variants for new maps, without requiring manual generation. This will not take effect for maps created prior to this patch.
* The Custom game variant is no longer automatically included when other non-default variants are defined.
* Increased the maximum recharge vital rate for heal effects.
Bug Fixes
* Battle.net
o Chat windows no longer vanish when exiting a multiplayer map or campaign mission.
o Fixed an issue where players would still receive toasts when their status was set to busy.
* Custom Games
o Default race in a game lobby is now properly set to Random.
o Players can now configure the lobby for 1v5 matches.
o The search functionality for map searches has been improved.
o Lobby hosts will now receive a toast when an invited player declines an invitation.
o Custom game lobbies will now remember the game mode chosen under a category.
o Fixed an issue where changing the category to "Custom" would default the teams to 5v3.
o Fixed an issue where custom maps could not be reported from the map preview screen.
* Gameplay
o General
+ If a unit loads into a transport, missiles targeting it will no longer target similar units in the area.
+ Structures damaged during construction will no longer count towards structures lost.
+ Fixed an issue where builders waiting for an area to clear could block units trying to leave the area.
+ Fixed an issue with inventory drop range checks.
+ Fixed an issue that, in certain cases, allowed a command to be issued that did not appear on the command card
o Interface
+ Queue tooltips now display information about what is in progress.
+ Fixed an issue where the back button would not always return players to the score screen properly.
o Terran
+ Marines trained at multiple Barracks will now prefer a Barracks with a Reactor over one with a Tech Lab or no attachment.
+ SCVs will now load into the closest Command Center if multiple are within range.
o Zerg
+ Creep now recedes properly when an AI-controlled Hatchery, Lair, or Hive is destroyed.
* StarCraft II Editor
o The Player Leaves Game event now fires when a player leaves or they are defeated/victorious.
o Loading screen progress bar option now works when using Melee loading screen type.
o Test Document now works properly on maps with Battle.net-only dependencies.
o Publishing a new file using Major revision will now properly set the document version to 1.0.
o Publish dialog now properly remembers the Show Real Name setting from previous publish.
o File preview panel now displays author's real name if that option was set during publishing.
o The Import module will now allow importing an override Assets.txt file.
o Undoing a terrain object modification will now also undo associated terrain changes.
o Editor will display document text from another locale if no text for the active locale exists.
o Copying points with custom models will display the model properly on the pasted point.
o It is no longer possible to have multiple default variants in the Game Variants dialog.
o Removed icon support for attribute and variant definitions, as Battle.net does not display these.
o Fixed issues with invalid map bounds when creating 32x32 maps.
o Fixed issues with poor performance in the Terrain Editor when scroll bars are visible.
o Fixed issues with drag-and-drop in Trigger Editor when tracking is not enabled.
o Fixed an issue that would cause a crash if multiple unit forms had too many abilities.
o Fixed an issue with temporary publish names in the Publish dialog still verifying the original name.
o Fixed an issue with the Unit Manipulates Item trigger.
o Fixed excessive delays on some systems when saving files using the Smaller Files option, and also when publishing Locked files.
o Fixed preview panel display in Terrain Editor palettes.
o Fixed performance issues in Terrain Editor when modifying terrain with many road tiles on the map.
o Fixed initial display of variables in the Trigger Debugging Window.
o Fixed generated script for built-in attribute values, which caused them to not be accessed properly.
o Fixed action list when modifying a Custom Script action without sub-views enabled.
o Fixed loading map dependency data.
o Fixed an issue where loading complex bank files would cause the client to disconnect from Battle.net.
* Technical Issues
o Fixed an issue where unplugging headphones could cause the game to freeze.
o Fixed an issue where XP systems running with Unicode characters enabled could prevent a player from starting a multiplayer game.
StarCraft II: Wings of Liberty - Patch 1.1.0
To get the latest news and interact with the community, visit our StarCraft II website. Be sure to check out our Game Guide for an in-depth look at StarCraft II gameplay. We wish you all the best on your journeys through the embattled Koprulu Sector!
General
* The Standard (US) and Standard for Lefties (US) hotkey configurations are now available in all regions.
* A new game clock has been added. Players can now instantly see how long they've been in their current mission or match. This feature can be turned on or off in the Gameplay Options menu.
* A new Quick Save option is now available for the single-player campaign. Players can now quickly save their mission progress by pressing Ctrl + Q.
* A new System Panel has been added. Players can now view their local time and FPS while in game by mousing over the Menu (F10) button in the upper-left hand corner of the game screen. Laptop users can also view Wi-Fi signal strength and battery levels.
* Sight granted by death reveal no longer lifts Fog of War. Units revealed in this manner are not targetable.
* (Mac only) Moved StarCraft II data files and settings from the Documents folder into the Application Support folder.
* Support for NVIDIA 3D Vision has been added. To experience StarCraft II: Wings of Liberty in 3D on your desktop or notebook, you will need 3D Vision. For more information, visitwww.nvidia.com/Starcraft3D
Balance Changes
* PROTOSS
o Zealot
+ Build time increased from 33 to 38.
+ Warp Gate cooldown increased from 23 to 28.
* TERRAN
o Battlecruiser
+ Ground damage decreased from 10 to 8.
o Bunker
+ Build time increased from 30 to 35.
o Reaper
+ Build time increased from 40 to 45.
o Siege Tank
+ Siege mode damage changed from 50 to 35 (+15 armored).
+ Upgrade damage changed from +5 to +3 (+2 armored).
* ZERG
o Ultralisk
+ Ram ability removed. Ultralisk will now use normal attack against buildings.
+ Damage decreased from 15 (+25 armored) to 15 (+20 armored).
* Maps
o Desert Oasis
+ Destructible Rocks have been added to make natural expansions easier to protect.
+ Center Xel'Naga Tower area has been narrowed.
StarCraft II Editor Improvements
* Added new requirement types: Odd, Divide, Mod, Multiply.
* Added a chance field to effect data.
* Added support for the Slider dialog control type.
* Added a trigger to deal damage from a unit.
* Added a trigger event response to provide the amount a player or unit property changes.
* Added a trigger event when an effect executes.
* New Trigger Editor functions:
o Save Data Conversation State Value (Action).
o Load Data Conversation State Value (Action).
o Players On Team (returns Player Group associated with teams in game lobby).
o Unit Owner Changes (Event).
o Old Unit Owner (returns player ID in response to Unit Owner Changes).
o New Unit Owner (returns player ID in response to Unit Owner Changes).
* XP, Level, and Bounty unit properties can now be modified by triggers.
* Banks now save/restore XP, learned abilities, and items.
* Message Window now includes a time stamp for each message.
* An actor event is now dispatched when a missile cannot hit its target.
* When loading documents with Battle.net-only dependencies, you will now be prompted to log in and download the dependency data, rather than failing to load.
* Game variants now automatically use the default melee variants for new maps, without requiring manual generation. This will not take effect for maps created prior to this patch.
* The Custom game variant is no longer automatically included when other non-default variants are defined.
* Increased the maximum recharge vital rate for heal effects.
Bug Fixes
* Battle.net
o Chat windows no longer vanish when exiting a multiplayer map or campaign mission.
o Fixed an issue where players would still receive toasts when their status was set to busy.
* Custom Games
o Default race in a game lobby is now properly set to Random.
o Players can now configure the lobby for 1v5 matches.
o The search functionality for map searches has been improved.
o Lobby hosts will now receive a toast when an invited player declines an invitation.
o Custom game lobbies will now remember the game mode chosen under a category.
o Fixed an issue where changing the category to "Custom" would default the teams to 5v3.
o Fixed an issue where custom maps could not be reported from the map preview screen.
* Gameplay
o General
+ If a unit loads into a transport, missiles targeting it will no longer target similar units in the area.
+ Structures damaged during construction will no longer count towards structures lost.
+ Fixed an issue where builders waiting for an area to clear could block units trying to leave the area.
+ Fixed an issue with inventory drop range checks.
+ Fixed an issue that, in certain cases, allowed a command to be issued that did not appear on the command card
o Interface
+ Queue tooltips now display information about what is in progress.
+ Fixed an issue where the back button would not always return players to the score screen properly.
o Terran
+ Marines trained at multiple Barracks will now prefer a Barracks with a Reactor over one with a Tech Lab or no attachment.
+ SCVs will now load into the closest Command Center if multiple are within range.
o Zerg
+ Creep now recedes properly when an AI-controlled Hatchery, Lair, or Hive is destroyed.
* StarCraft II Editor
o The Player Leaves Game event now fires when a player leaves or they are defeated/victorious.
o Loading screen progress bar option now works when using Melee loading screen type.
o Test Document now works properly on maps with Battle.net-only dependencies.
o Publishing a new file using Major revision will now properly set the document version to 1.0.
o Publish dialog now properly remembers the Show Real Name setting from previous publish.
o File preview panel now displays author's real name if that option was set during publishing.
o The Import module will now allow importing an override Assets.txt file.
o Undoing a terrain object modification will now also undo associated terrain changes.
o Editor will display document text from another locale if no text for the active locale exists.
o Copying points with custom models will display the model properly on the pasted point.
o It is no longer possible to have multiple default variants in the Game Variants dialog.
o Removed icon support for attribute and variant definitions, as Battle.net does not display these.
o Fixed issues with invalid map bounds when creating 32x32 maps.
o Fixed issues with poor performance in the Terrain Editor when scroll bars are visible.
o Fixed issues with drag-and-drop in Trigger Editor when tracking is not enabled.
o Fixed an issue that would cause a crash if multiple unit forms had too many abilities.
o Fixed an issue with temporary publish names in the Publish dialog still verifying the original name.
o Fixed an issue with the Unit Manipulates Item trigger.
o Fixed excessive delays on some systems when saving files using the Smaller Files option, and also when publishing Locked files.
o Fixed preview panel display in Terrain Editor palettes.
o Fixed performance issues in Terrain Editor when modifying terrain with many road tiles on the map.
o Fixed initial display of variables in the Trigger Debugging Window.
o Fixed generated script for built-in attribute values, which caused them to not be accessed properly.
o Fixed action list when modifying a Custom Script action without sub-views enabled.
o Fixed loading map dependency data.
o Fixed an issue where loading complex bank files would cause the client to disconnect from Battle.net.
* Technical Issues
o Fixed an issue where unplugging headphones could cause the game to freeze.
o Fixed an issue where XP systems running with Unicode characters enabled could prevent a player from starting a multiplayer game.
Monday, September 20, 2010
Photon Cannon Cheese Rush Guide
What You Will Need
A bold and adventurous spirit. A quick and discerning mind. The ability to laugh in the face of convention. And a willingness to sacrifice social validation and embrace your inner wild man.
If you possess these noble qualities, then you, too, can become a cannon cheeser.
Before we get started, my qualifications:
I have none. I am just a guy who plays starcraft. I am not good at the game. I am not bad at it either. When I play, I am a Diamond Zerg.
If people tell you that cheese doesn't work, don’t believe it. Anyone can get got. And if people tell you that cannon rushing is all in, don’t believe it either. Cannon rushing is a crime of opportunity. The key to success is having proper information and knowing when opportunity is knocking.
When to Cannon Rush
Cannon rushing is a crime of opportunity. If you decide, a priori, to cannon rush someone, you have at best a 50/50 shot at it working. You can’t just say, “I’m going to cannon rush.” Instead, you have to scout their base and look for the opportunity. If you see it, you need to act quickly. Otherwise, you need to have a plan to transition to a normal opening.
In order to know whether or not to cannon rush someone, you need to ask a few questions.
Question #1: What race are you facing?
The race you are facing makes a huge difference in your decision to rush. In order of difficulty, the races break down like this:
Zerg - Most Difficult
The Zerg is the hardest race to cannon rush because of three factors: Creep, Units, and Spine Crawlers.
Zerg Problem #1: Creep
When you are cannon rushing, you want to build as few cannons as possible to destroy or cripple their base. Creep makes it difficult to build cannons near the main base. So, you often have to come at them from an angle or from behind. This is often difficult to do and depends greatly on the map.
Zerg Problem #2: Units
The early zerg units can kill the probe quickly. Zerglings are fast, and they can appear early in a game (especially if the zerg is going to rush you). Queens are ranged, and can also kill the probe quickly.
Zerg Problem #3: Spine Crawlers
FIXED -> Spine crawlers cost the same as cannons (100 minerals + drone vs 150) but they do more damage (25 +5 against a cannon vs 20 for the cannon). So, once the zerg gets them built, they can take out your cannon line pretty handily.
Terran - Difficult
Terrans are difficult to rush mainly because of the Marine. Because the Marine is ranged, it can take out the probe quickly. It comes out faster than a zealot. But, it is also weak, so it takes a long time for it to eliminate the pylon. Terrans are also difficult to rush because they can move their buildings. More on this later.
Protoss - Medium
Protoss is the easiest to rush against because you know exactly what they have at any given time. They have the same tools you do, so you have a better sense of their timing and possibilities. The initial unit, the zealot, is slow and can’t catch the probe. Their buildings are immobile and can't move. They have no ranged units early. Because of this, your best chance of winning with a cannon rush is against another toss. But it’s still not a given.
Question #2: What map are you playing?
Once you’ve looked at the race matchups, you have to look at the map. The big question here is scouting. On a 1v1 map, there is no scouting necessary. You know where the guy is going to be, so you can just haul ass over there and see what's up.
On larger maps, however, you have to find them. This rush works better the earlier you get it started. So, if it takes you a long time to find the opponent’s base, it might be too late to rush them. The longer you wait, the further along the opponent will be in development. That means that by the time you get there, your window of opportunity might be gone.
In addition to map size, there are also map specific features that you need to consider. Some maps are easier to cannon rush. Other maps allow for unique cannon rushes. For instance, on desert oasis, you don’t need to build the pylon inside the enemy base to cannon rush. So, it’s a lot easier to try it than on some other maps. These are all things to consider when evaluating the map.
Question #3: What are THEY doing?
The biggest factor that determines if you rush or not is what you do or do not see when you enter their base. No pylons? No Rax? Early pool? They might be rushing you. Did they see your probe and follow it? No more stealth option. Are they building a forge? They might be cannon rushing YOU.
With those things in mind, let’s look at the two main opportunities for cannon rushing.
The Opportunities
In general, there are two opportunities to cannon rush:
One, you slip into the base unnoticed. You are in stealth mode. They don’t know the probe is there. You build cannons, they don't find out about it till it's too late.
Two, they see you, but they are a long ways away from having units (zealots, marines, lings). You are in rush mode. You try to finish your cannons and they try to stop you with workers.
So, with these opportunities in mind, enter the world of the cannon rush.
Step 1: Send an Early Scout
How early? I usually go after building the pylon on 9. It looks normal, and it minimizes impact on my economy. If you get scouted and people don’t see the pylon, it immediately raises suspicion.
On the other hand, some toss wait till 14 to make a gateway, so if they see the early pylon, you can often chase their probe out before you put down the forge, and they will be none the wiser.
Sometimes on 1v1 maps, I send earlier probes. But, usually, 9 is early enough.
Step 2: Build the Forge
When you know where the enemy is, start building your forge at your main.
Step 3: The Enemy Base
You should arrive at the enemy base with your forge under construction.
Now, you have to look for the opportunity. Once you get good, you will just have a feel for it. The main thing to note is if you think they saw you, or if you got in by surprise.
Discovered Entering Base
If you are discovered entering the base, you have to make a choice. Your forge should still be building back home, so you need to decide if you want to rush or not. If you let the forge complete, you are committed. Even if you don’t build a pylon and cannons, you will be behind in teching, so you need to decide quickly.
Against Terran and Toss, it is possible to rush even if they see you doing it. You do NOT have to hide in order to successfully cannon rush someone. But, you do need to be decisive.
When I am deciding to do this, I usually look at how far along they are on their build. If the toss does not have a gateway complete, I usually continue. Same thing for the Terran... if the barracks is just underway, I will usually go ahead. Zerg I usually won’t rush.
If the gateways or rax are too far along, or I don’t feel like the time is right, then I scout like normal, possibly cancel the forge, and transition into something else. You lose a bit of economy, but it is recoverable. You won’t be using any CB during this part, so you can just CB probes if you decide to bail.
If I see no gateways, no pylons, no rax, or an early pool, I think cheese. I transition by letting the forge complete, building two cannons next to my nexus, and cranking probes. This lets you shut down all early rushes, from 2 gate to reaper to 6-pool, and it lets you emerge with a very solid probe count. More on this later.
Step 3: Build the Pylon
If you are not detected or followed, you are still in stealth mode. Congrats, this is prime time for cannon rushing.
If you have been detected, and decide to rush anyway, then it's time to build that pylon in his face! Position it to cause maximum psychological damage and distraction.
The cannon rush starts when you plant the first pylon.
Start the pylon BEFORE the forge finishes, when the forge is 1/2 to 3/4 done. You want them to finish at the same time. If the forge is completed at home, and you haven't placed the pylon yet, you are running late. The longer you wait, the less likely your rush will succeed.
Placement is crucial. I usually don’t target Zerg, but when I do, I target the mineral line. For Toss and Terran, I usually target the CC or Nexus.
I try to place the pylon OUT OF SIGHT and in a position that makes it as hard as possible for his ground troops (zealot or marine) to get to once it is discovered. You want them to have to run as far as possible and pass through the field of fire of your defense cannon in order to get to the pylon. You do NOT want them to be able to snipe the pylon without taking shots from the first cannon.
Step 4: First Cannon
If you are still undetected, put the first cannon right next to the pylon. You will need this cannon to hold off the initial defense. It is not critical that this cannon be able to hit the target. It just needs to protect the pylon. If you are lucky, you will remain undetected as the cannon gets 3/4 complete.
Don’t build too many of these.
The main goal is to build as few cannons as possible. If this cannon completes, you are WAY WAY closer to successfully completing the rush, as a single early cannon can just wreck just about anything that is thrown at it.
If you are building in his face, then position the cannon to cover approaching defensive forces AND hit the CC or nexus. You need to start doing damage asap.
Step 5: Finishing Cannons
When that first cannon is 3/4 done, build two more cannons between the pylon and the nexus or CC. These are the cannons that will do the damage. They should be the first cannons your opponent sees, and they should be covered by the field of fire of the first cannon. You should have 300 minerals saved at this point for this purpoase. If it’s zerg, aim to hit the gas and mineral line.
Usually what happens is that the enemy sees the cannons building and sends some probes to hit them. As they approach, the probes start taking fire from the first cannon. At this point, it’s probably GG. But there are ways to respond, as noted below.
Against terran or zerg, you need to place the finishing cannons so that the marine or queen can’t hit them without taking fire from the first cannon. How to do this depends on the map and how the enemy builds. But carefully look at the field of fire for the cannon before placing it. It can mean the difference between success and failure.
Remember, these are the critical cannons. If they complete, the rush most likely succeeds. But normally it won’t be that simple. They will usually struggle and fight before they rage quit.
Responses
There are many responses to the cannon rush. Most of them are wrong. If you know what the responses are, you can deal with them and make it more difficult for your opponent to defend. Before you get started with the responses of the opponent, however, there are two things you need to know how to do.
Thing #1 - Probe Micro
When they attack your probe, run away. I usually run in a circle around the pylon or cannons that are building. There is no way that they can kill your probe unless your micro fails or they get a marine. Probes are too fast and their shields regenerate. So, as soon as they start to attack you, run the probe in a circle.
Do NOT run home just because they found you. You can do the rush even if they see you. Seeing it isn’t stopping it. Just don’t let your probe take unnecessary shots. Just queue up a big circle and let the probe run on its own while you do production back in your main.
Thing #2 - CANCEL
Do NOT let them destroy any of your pylons or cannons. Cancel your pylons and cannons before they die. If you do this, it only costs you 25% of the building cost, which is either 25 minerals for the pylon or 37.50 for the cannon.
You must learn to cancel buildings quickly before they are destroyed in order to maximize your chances of success, waste as much of their time as possible and minimize the damage of a failed rush.
Enemy Response Fail #1 - Pylon is Building - Send One Worker to Kill Probe
Some people try to solve the problem by sending only one worker to kill or follow your probe. One worker cannot stop anything. Probes are fast. If they send one worker to kill your probe, just queue it up to run a big circle in their base, and build the pylons and cannons as the other worker chases you.
Enemy Response Fail #2 - Pylon is Building - Send One Worker to Kill Pylon
If they send one worker to kill the pylon, laugh at it. It won’t do enough damage in time. They can’t stop you unless they commit more resources to the task.
While their probe is attacking the pylon, use your probe to attack their probe. If they don’t pay attention, you will kill it. If they do, they might try to fight you. In that case, either kill them (if you are ahead on damage) or run around in a circle.
Enemy Response Fail #3 - Pylon is Building - Send All Workers to Kill Pylon
Some people overreact. They send ALL workers. Workers collect minerals at a rate of about 0.8 minerals per second. So, if they have sent 10 workers, that’s 8 minerals per second. If you can waste their time for 3 seconds, you pretty much break even when you cancel the pylon.
If they send all the workers to kill the pylon, start building another pylon. Just watch the first pylon and cancel it before it dies. Usually, I will build this second pylon far away to make sure their probes have to travel and waste maximum time.
If they are killing your pylons, you may have to bail on the strategy eventually. But you can really damage their economy by forcing them to stop mining. More importantly, you damage their mind set and their rhythm. Also note that YOU won’t have to stop mining while this happens, so you can use this time to start building probes and catch up.
Enemy Response Fail #4 - Pylon is Building - Send All Workers to Kill Probe
If they send all of the probes after your probe, just laugh and run their probes around (or even out of) their base. As Borat said, "They will never get this!" There is no greater comedy than watching a comet tail form behind your probe as it trails angry workers around the enemy base.
Enemy Response Fail #5 - Pylon Completes - Send All Workers to Kill Pylon
This is my favorite mistake. When the pylon completes, immediately start building cannons. If they send a ton of probes to kill the pylon, good. The main goal is to get your cannons to complete.
Most people think that if they can take out the pylon, the cannons will power down. This is true. But, once the cannons are completed, it is really easy for me to build a bunch of pylons and get the cannons to power up again.
Anyone who has seen the Korean 4 warp gate knows that you can’t stop ALL the pylons from completing. One of them will finish. And when it does, the cannons will power up again. I have won many games like this.
The moral here is focus on what kills you... a pylon can’t shoot you, but a cannon can. It’s easy to build pylons: they are cheap and they complete quickly. Cannons are more expensive and take more time. Without the cannons there is no rush. So don’t let the cannons complete.
Defending the Rush - Early Detect
So what do you do if someone rushes you? The best way to defend the rush is to know that it is coming. If you find a probe hanging out, keep tabs on it. If it starts to build pylons, use the rush defense outlined below.
Defending the Rush - What to Do
If someone is cannon rushing you, take 4 workers and kill whatever they are building. If the pylon is already up, leave it up. Just kill any new things that get built. Don’t chase the probe. You won’t catch it. Just continue to tech and force the rusher to cancel everything.
At 4 workers, you are only losing 3.2 minerals per second, so every time he cancels, it costs 25. You have 8 seconds per pylon before you go negative, and you can usually stop it faster than that.
*Added for Clarification*
If he builds 2 cannons at once, send two groups of 4 workers, one to each cannon. If he builds 3 cannons at once, and you don't have enough workers, then queue up the first set of workers to hit the 3rd cannon. With all the workers, queue them up to return to mining when they are done so you don't waste time.
He should not be able to build more than 3 cannons at once because the rush happens so early. When I do this rush, it usually goes down before 4 minutes. You will either be firing on their nexus at 3 minutes and something, or you will be canceling and transitioning into something else. The later they try the rush, the better off you will be. Regardless, just keep killing anything he tries to warp in.
Eventually, he will either run out of money or you will have the tech to stop the rush outright (ie, marines, zerglings, zealots). The main thing is DON’T get hypnotized by the probe or the pylon. Just take 4 workers to kill whatever is building.
Defending the Rush - Cannons Up
If the cannons are up and they are hitting your base, that’s very close to a GG. But there are some things you can do.
Protoss
For protoss, it pretty much IS gg. Your only hope is to rush whatever zealots and forces you have to his base, and then hope you can base trade faster. But usually you won’t be able to because he will have cannons there by the time you arrive, and your only recourse will be to nerd rage and call him a noob.
If you have the cash, you can try to expand. But that's usually just delaying the inevitable.
Zerg
Zerg can fight back by getting a spine crawler up. Although you will take a ton of damage, spine crawlers have great range, and they can eventually push the cannons back. Because of creep, cannons can’t really get close to the main hatch anyway, so spine crawlers can help fend it off.
You can also try to use the queen to snipe the pylon if the toss has mis-positioned it. But, that's unlikely. Because of the creep, I rarely rush zerg with cannons unless there is a map like desert oasis that is prone to outside pylon rushes.
Terran
Terran has the best response options for anti-cannon rushing. The first thing you can do is move your base. Take ALL of your scvs and move them to your natural, then fly your command center over there. You can begin production again almost immediately without losing a thing. And since your barracks are already building, you can start cranking rines to go smash his base with.
Because of the placement of ramps, its difficult for a cannon rusher to sneak in between you and your natural. They usually have to go to the far side of your base where they can hide. So this line of retreat is usually open.
If the natural is not open, you can fly the CC to another expansion and just move the workers there. You can even move the CC to the OTHER side of the minerals sometimes, depending on the map and the angle of the rush. The main idea is that you GTFO when the rush starts and move to a new base.
If you can’t move and the cannon placement is bad, you can sometimes get the marine to snipe the pylon without the cannon hitting him. Do that if you can, then reinforce the marine. If you can snipe the probe, do that too. Terrans have the best shot at eliminating the probe because marines are ranged, so take advantage of it. But don’t rely on it. Good cannon placement usually makes this option mute.
Step 6: Responding to Rush Defense
If someone defends your rush, then as a good rusher, you need to be able to respond. These are things you can do if you see them defending.
Build Few Cannons
The most important thing that you need to understand is you want to build as FEW cannons as possible. I usually go for 3. The more cannons you build, the farther behind you will be if and when the strat fails.
If you make him run away, you are not necessarily ahead. He might have more minerals banked and a higher worker count. This is your chance to pull back to even. It's going to take him some time to get productive again. So, use that time to get your economy up. In particular, I like to expand into their base as soon as they run.
Transition into Gateways
If the person runs, they usually can’t run far. By this time you are behind on probe count and tech, but the disruption your harass caused probably evened that out. What you need to do now is get units. You should have a nexus full of chronoboost. So, build gateways and CB some zealots.
I usually build the gateways by the cannons, and then rush down and smash the natural. If they aren’t at the natural, I scout for them. But I usually keep the gateways with the cannons. A lot of times there are left behind buildings in their main. Just destroy those as you start to churn out some zealots.
Expand to their Base
Once I have enough minerals, I take their base as my expansion. You already have static defenses up in the form of the cannons and you already have gateways, so the expansion becomes my main. This is how you get back in the game economically.
It’s effective. Plus, it’s salt in the wound: All your base are belong to us. Literally.
This is also great because people who get rushed usually target your original main. Because of that, I usually just cannon it up a little and treat it as an expansion. I love the surprise when they march into it, fight through the cannons, and realize that there was nothing there.
Step 7: Nerd Rage
If you have followed along diligently, you have learned the ways of the cannon rush and successfully rushed someone. Prepare to receive your reward!
Nerd rage is a confection sweeter than honey, an ambrosia of the gods. Savor it. There are many ways to enjoy it. Be magnanimous in victory. Offer tips. Comfort him. Talk shit. The options are endless. Stockpile witty sayings and pithy remarks that you can use to rejoinder the vitriol that will be heaped upon you.
Some typical quips:
Loser: “You $@#$%#@$ noob! I will kill you! You SUCK!!!!!”
Loser: “I bet you are in the bronze leage you !@$!$##! loser”
Loser: “You @%$#!$ cheeser, that !@#$ will NEVER work again!”
Feel free to respond in the way that amuses you most.
There may come a point when you start to feel bad about cheesing. Don’t. Terrans don’t feel bad about playing their POS overpowered race. So you shouldn’t feel bad about cheesing. It takes a lot more skill to do a cannon rush than it does to do 3rax 1A GG.
And yes, anyone who says cheesing doesn’t take skill obviously isn’t very good at it.
Anyone can cheese a noob. But to cheese platinum and diamond level players, you need a bit of skill. A sliver of luck. And a touch of grace. If you learn to recognize your opportunities, you will have a viable opening that can end games quickly and crush your opponent psychologically. And who doesn’t want to do that?
Think About It
Stealth aside, the reason this rush works is because of two factors. The first is build timing. I can build a pylon and a cannon faster than you can complete a gateway and boost out a zealot. Even if the zealot gets out, he can’t kill the cannon or the pylon alone. It takes a long time. You will have to use workers.
The marine is in the same boat. But, because he is ranged, he is more difficult to handle. But only a little. He can take the probe out. Still, he can’t kill a pylon or a cannon very fast, and it becomes a race. Unfortunately for the defender, it is a race in which I know all the correct decisions, and you probably don’t.
Therefore, you will be analyzing while I am still in book. This gives me an advantage. The chances of you calculating the right response and not making a mistake are slim. On the other hand, I know exactly what to do based on your decisions. So, I can react instantly.
The second reason it works is pressure. Building stuff in someone's base puts them on tilt. If they make a mistake, they lose. If they don’t, I simply cancel my stuff and walk away. Total investment is usually less than 100 minerals on my part for a failed rusher.
I will be behind in probe count, and slightly behind on tech. But not that much. I have a forge and a nexus full of CB, and I can often make that ground back up. On the flip side, the disruption, both economically and psychologically, that it inflicts on my opponent is often be worth it.
There are two ways to win in chess... playing the board, and playing the opponent. This opening is designed for people who like to play the opponent.
Anti-Cheese
One of the positive side effects of this line of thinking is that if someone tries to cheese you before you cheese them, you have a great chance of winning. You will know that the enemy is cheesing when you enter their base. At some point, you will realize they have NOTHING. At that monent, your ears should perk up.
Fortunately, having an early forge lets you defend almost all of the early rushes you will face.
Zerg Ling Rush
Build two cannons by your nexus. You will crush 6 pool or any other zergling rush. Just make sure to use the cannon nexus and forge to block off 3 sides of the main pylon. Or, build another pylon at the base. If they can’t get a surround on the pylon, they are toast. Use probes to attack when they enter the line. I often repel this attack without losing a single probe.
Note: I used this to defend against Zerg rushes in SC1 on Bloodbath. If you haven’t played it, it is a map with a VERY short rush distance. This always worked. Just build a tight base. Don't spread your structures out.
Terran Proxy Rax
Terran proxy rax rush loses to 2 cannons by the nexus or wall off on the choke point. Just cannon up at your base the cannon rush them at theirs and when they run, take it as an expansion.
Terran Early Reaper
If you see the early reaper, just build two cannons - one in your mineral line, one on top of the nexus opposite it. This keeps the reaper from hitting probes or sniping your nexus or buildings.
Positioning is key. The reaper will try to find an area not covered by cannon field of fire, so place carefully. Never build your cannons at the choke point, because the reaper will laugh at you.
Protoss Proxy Rush
You win this match up by building 2 defensive cannons at your home base and an extra pylon, then continuing with the cannon rush at his base. Alternate building cannons at home and away, as the longer it takes, the more zealots he’ll have.
When you enter his base and see NOTHING (no pylon, no gate, no buildings), you know the proxy rush is on. Cannon up at your main, then beat him with cannons at his.
Protoss Cannon Rush
This is all about speed and knowledge. If you see the forge in their base, scout your own base immediately. If he has not built any cannons yet in your base, build a defensive cannon. Don’t build this one near your nexus... build far away it to shut off his angle of approach.
Most cannon rushers have not taken the time to study the opening, so you can beat them the same way you beat someone with an in-your-face rush... with superior knowledge.
If the cannons are already warping in, hope to god that he doesn’t have a defensive cannon already up. Then, take 4 probes and kill whatever is building. Use 4 probes for EACH thing he builds... so if he builds 2 cannons, use 8 probes total. If you run out of probes, queue the groups up to hit the incoming cannons. While you are doing that, you will have to decide if you can still cannon rush him, or if you need to cancel and start teching.
All In Build
There are variations of the cannon rush that you can use and try. One of them that is funny is the enemy base forge. To do this, you run to the enemy base with your first or second probe. You build a pylon right in their face. Then, you build a forge right there next to it in their base. Once it finishes, you buy cannons.
It sounds stupid, but unless they react correctly, they will lose. They will NOT have a gateway or rax started, and they might not even have a pylon or supply depot. Anyone who tries to build a defense to this loses. There is no way they can get any cannons, zealots or marines to help them in time.They need to send 4 workers to kill everything you build, not target the pylon, not target the probe.
I don’t like this build because if it fails, you die. Not only do you lose they pylon, you lose the forge too. There is no way to recover if this doesn’t succeed. On the other hand, it's extremely exciting to attempt, and when it works, NOTHING generates more nerd rage. The change from curiosity to annoyance to panic is priceless. I recommend trying it for cheese connoisseurs.
And if you can do this to a terran, then so much the better. You will be doing everyone a public service.
A bold and adventurous spirit. A quick and discerning mind. The ability to laugh in the face of convention. And a willingness to sacrifice social validation and embrace your inner wild man.
If you possess these noble qualities, then you, too, can become a cannon cheeser.
Before we get started, my qualifications:
I have none. I am just a guy who plays starcraft. I am not good at the game. I am not bad at it either. When I play, I am a Diamond Zerg.
If people tell you that cheese doesn't work, don’t believe it. Anyone can get got. And if people tell you that cannon rushing is all in, don’t believe it either. Cannon rushing is a crime of opportunity. The key to success is having proper information and knowing when opportunity is knocking.
When to Cannon Rush
Cannon rushing is a crime of opportunity. If you decide, a priori, to cannon rush someone, you have at best a 50/50 shot at it working. You can’t just say, “I’m going to cannon rush.” Instead, you have to scout their base and look for the opportunity. If you see it, you need to act quickly. Otherwise, you need to have a plan to transition to a normal opening.
In order to know whether or not to cannon rush someone, you need to ask a few questions.
Question #1: What race are you facing?
The race you are facing makes a huge difference in your decision to rush. In order of difficulty, the races break down like this:
Zerg - Most Difficult
The Zerg is the hardest race to cannon rush because of three factors: Creep, Units, and Spine Crawlers.
Zerg Problem #1: Creep
When you are cannon rushing, you want to build as few cannons as possible to destroy or cripple their base. Creep makes it difficult to build cannons near the main base. So, you often have to come at them from an angle or from behind. This is often difficult to do and depends greatly on the map.
Zerg Problem #2: Units
The early zerg units can kill the probe quickly. Zerglings are fast, and they can appear early in a game (especially if the zerg is going to rush you). Queens are ranged, and can also kill the probe quickly.
Zerg Problem #3: Spine Crawlers
FIXED -> Spine crawlers cost the same as cannons (100 minerals + drone vs 150) but they do more damage (25 +5 against a cannon vs 20 for the cannon). So, once the zerg gets them built, they can take out your cannon line pretty handily.
Terran - Difficult
Terrans are difficult to rush mainly because of the Marine. Because the Marine is ranged, it can take out the probe quickly. It comes out faster than a zealot. But, it is also weak, so it takes a long time for it to eliminate the pylon. Terrans are also difficult to rush because they can move their buildings. More on this later.
Protoss - Medium
Protoss is the easiest to rush against because you know exactly what they have at any given time. They have the same tools you do, so you have a better sense of their timing and possibilities. The initial unit, the zealot, is slow and can’t catch the probe. Their buildings are immobile and can't move. They have no ranged units early. Because of this, your best chance of winning with a cannon rush is against another toss. But it’s still not a given.
Question #2: What map are you playing?
Once you’ve looked at the race matchups, you have to look at the map. The big question here is scouting. On a 1v1 map, there is no scouting necessary. You know where the guy is going to be, so you can just haul ass over there and see what's up.
On larger maps, however, you have to find them. This rush works better the earlier you get it started. So, if it takes you a long time to find the opponent’s base, it might be too late to rush them. The longer you wait, the further along the opponent will be in development. That means that by the time you get there, your window of opportunity might be gone.
In addition to map size, there are also map specific features that you need to consider. Some maps are easier to cannon rush. Other maps allow for unique cannon rushes. For instance, on desert oasis, you don’t need to build the pylon inside the enemy base to cannon rush. So, it’s a lot easier to try it than on some other maps. These are all things to consider when evaluating the map.
Question #3: What are THEY doing?
The biggest factor that determines if you rush or not is what you do or do not see when you enter their base. No pylons? No Rax? Early pool? They might be rushing you. Did they see your probe and follow it? No more stealth option. Are they building a forge? They might be cannon rushing YOU.
With those things in mind, let’s look at the two main opportunities for cannon rushing.
The Opportunities
In general, there are two opportunities to cannon rush:
One, you slip into the base unnoticed. You are in stealth mode. They don’t know the probe is there. You build cannons, they don't find out about it till it's too late.
Two, they see you, but they are a long ways away from having units (zealots, marines, lings). You are in rush mode. You try to finish your cannons and they try to stop you with workers.
So, with these opportunities in mind, enter the world of the cannon rush.
Step 1: Send an Early Scout
How early? I usually go after building the pylon on 9. It looks normal, and it minimizes impact on my economy. If you get scouted and people don’t see the pylon, it immediately raises suspicion.
On the other hand, some toss wait till 14 to make a gateway, so if they see the early pylon, you can often chase their probe out before you put down the forge, and they will be none the wiser.
Sometimes on 1v1 maps, I send earlier probes. But, usually, 9 is early enough.
Step 2: Build the Forge
When you know where the enemy is, start building your forge at your main.
Step 3: The Enemy Base
You should arrive at the enemy base with your forge under construction.
Now, you have to look for the opportunity. Once you get good, you will just have a feel for it. The main thing to note is if you think they saw you, or if you got in by surprise.
Discovered Entering Base
If you are discovered entering the base, you have to make a choice. Your forge should still be building back home, so you need to decide if you want to rush or not. If you let the forge complete, you are committed. Even if you don’t build a pylon and cannons, you will be behind in teching, so you need to decide quickly.
Against Terran and Toss, it is possible to rush even if they see you doing it. You do NOT have to hide in order to successfully cannon rush someone. But, you do need to be decisive.
When I am deciding to do this, I usually look at how far along they are on their build. If the toss does not have a gateway complete, I usually continue. Same thing for the Terran... if the barracks is just underway, I will usually go ahead. Zerg I usually won’t rush.
If the gateways or rax are too far along, or I don’t feel like the time is right, then I scout like normal, possibly cancel the forge, and transition into something else. You lose a bit of economy, but it is recoverable. You won’t be using any CB during this part, so you can just CB probes if you decide to bail.
If I see no gateways, no pylons, no rax, or an early pool, I think cheese. I transition by letting the forge complete, building two cannons next to my nexus, and cranking probes. This lets you shut down all early rushes, from 2 gate to reaper to 6-pool, and it lets you emerge with a very solid probe count. More on this later.
Step 3: Build the Pylon
If you are not detected or followed, you are still in stealth mode. Congrats, this is prime time for cannon rushing.
If you have been detected, and decide to rush anyway, then it's time to build that pylon in his face! Position it to cause maximum psychological damage and distraction.
The cannon rush starts when you plant the first pylon.
Start the pylon BEFORE the forge finishes, when the forge is 1/2 to 3/4 done. You want them to finish at the same time. If the forge is completed at home, and you haven't placed the pylon yet, you are running late. The longer you wait, the less likely your rush will succeed.
Placement is crucial. I usually don’t target Zerg, but when I do, I target the mineral line. For Toss and Terran, I usually target the CC or Nexus.
I try to place the pylon OUT OF SIGHT and in a position that makes it as hard as possible for his ground troops (zealot or marine) to get to once it is discovered. You want them to have to run as far as possible and pass through the field of fire of your defense cannon in order to get to the pylon. You do NOT want them to be able to snipe the pylon without taking shots from the first cannon.
Step 4: First Cannon
If you are still undetected, put the first cannon right next to the pylon. You will need this cannon to hold off the initial defense. It is not critical that this cannon be able to hit the target. It just needs to protect the pylon. If you are lucky, you will remain undetected as the cannon gets 3/4 complete.
Don’t build too many of these.
The main goal is to build as few cannons as possible. If this cannon completes, you are WAY WAY closer to successfully completing the rush, as a single early cannon can just wreck just about anything that is thrown at it.
If you are building in his face, then position the cannon to cover approaching defensive forces AND hit the CC or nexus. You need to start doing damage asap.
Step 5: Finishing Cannons
When that first cannon is 3/4 done, build two more cannons between the pylon and the nexus or CC. These are the cannons that will do the damage. They should be the first cannons your opponent sees, and they should be covered by the field of fire of the first cannon. You should have 300 minerals saved at this point for this purpoase. If it’s zerg, aim to hit the gas and mineral line.
Usually what happens is that the enemy sees the cannons building and sends some probes to hit them. As they approach, the probes start taking fire from the first cannon. At this point, it’s probably GG. But there are ways to respond, as noted below.
Against terran or zerg, you need to place the finishing cannons so that the marine or queen can’t hit them without taking fire from the first cannon. How to do this depends on the map and how the enemy builds. But carefully look at the field of fire for the cannon before placing it. It can mean the difference between success and failure.
Remember, these are the critical cannons. If they complete, the rush most likely succeeds. But normally it won’t be that simple. They will usually struggle and fight before they rage quit.
Responses
There are many responses to the cannon rush. Most of them are wrong. If you know what the responses are, you can deal with them and make it more difficult for your opponent to defend. Before you get started with the responses of the opponent, however, there are two things you need to know how to do.
Thing #1 - Probe Micro
When they attack your probe, run away. I usually run in a circle around the pylon or cannons that are building. There is no way that they can kill your probe unless your micro fails or they get a marine. Probes are too fast and their shields regenerate. So, as soon as they start to attack you, run the probe in a circle.
Do NOT run home just because they found you. You can do the rush even if they see you. Seeing it isn’t stopping it. Just don’t let your probe take unnecessary shots. Just queue up a big circle and let the probe run on its own while you do production back in your main.
Thing #2 - CANCEL
Do NOT let them destroy any of your pylons or cannons. Cancel your pylons and cannons before they die. If you do this, it only costs you 25% of the building cost, which is either 25 minerals for the pylon or 37.50 for the cannon.
You must learn to cancel buildings quickly before they are destroyed in order to maximize your chances of success, waste as much of their time as possible and minimize the damage of a failed rush.
Enemy Response Fail #1 - Pylon is Building - Send One Worker to Kill Probe
Some people try to solve the problem by sending only one worker to kill or follow your probe. One worker cannot stop anything. Probes are fast. If they send one worker to kill your probe, just queue it up to run a big circle in their base, and build the pylons and cannons as the other worker chases you.
Enemy Response Fail #2 - Pylon is Building - Send One Worker to Kill Pylon
If they send one worker to kill the pylon, laugh at it. It won’t do enough damage in time. They can’t stop you unless they commit more resources to the task.
While their probe is attacking the pylon, use your probe to attack their probe. If they don’t pay attention, you will kill it. If they do, they might try to fight you. In that case, either kill them (if you are ahead on damage) or run around in a circle.
Enemy Response Fail #3 - Pylon is Building - Send All Workers to Kill Pylon
Some people overreact. They send ALL workers. Workers collect minerals at a rate of about 0.8 minerals per second. So, if they have sent 10 workers, that’s 8 minerals per second. If you can waste their time for 3 seconds, you pretty much break even when you cancel the pylon.
If they send all the workers to kill the pylon, start building another pylon. Just watch the first pylon and cancel it before it dies. Usually, I will build this second pylon far away to make sure their probes have to travel and waste maximum time.
If they are killing your pylons, you may have to bail on the strategy eventually. But you can really damage their economy by forcing them to stop mining. More importantly, you damage their mind set and their rhythm. Also note that YOU won’t have to stop mining while this happens, so you can use this time to start building probes and catch up.
Enemy Response Fail #4 - Pylon is Building - Send All Workers to Kill Probe
If they send all of the probes after your probe, just laugh and run their probes around (or even out of) their base. As Borat said, "They will never get this!" There is no greater comedy than watching a comet tail form behind your probe as it trails angry workers around the enemy base.
Enemy Response Fail #5 - Pylon Completes - Send All Workers to Kill Pylon
This is my favorite mistake. When the pylon completes, immediately start building cannons. If they send a ton of probes to kill the pylon, good. The main goal is to get your cannons to complete.
Most people think that if they can take out the pylon, the cannons will power down. This is true. But, once the cannons are completed, it is really easy for me to build a bunch of pylons and get the cannons to power up again.
Anyone who has seen the Korean 4 warp gate knows that you can’t stop ALL the pylons from completing. One of them will finish. And when it does, the cannons will power up again. I have won many games like this.
The moral here is focus on what kills you... a pylon can’t shoot you, but a cannon can. It’s easy to build pylons: they are cheap and they complete quickly. Cannons are more expensive and take more time. Without the cannons there is no rush. So don’t let the cannons complete.
Defending the Rush - Early Detect
So what do you do if someone rushes you? The best way to defend the rush is to know that it is coming. If you find a probe hanging out, keep tabs on it. If it starts to build pylons, use the rush defense outlined below.
Defending the Rush - What to Do
If someone is cannon rushing you, take 4 workers and kill whatever they are building. If the pylon is already up, leave it up. Just kill any new things that get built. Don’t chase the probe. You won’t catch it. Just continue to tech and force the rusher to cancel everything.
At 4 workers, you are only losing 3.2 minerals per second, so every time he cancels, it costs 25. You have 8 seconds per pylon before you go negative, and you can usually stop it faster than that.
*Added for Clarification*
If he builds 2 cannons at once, send two groups of 4 workers, one to each cannon. If he builds 3 cannons at once, and you don't have enough workers, then queue up the first set of workers to hit the 3rd cannon. With all the workers, queue them up to return to mining when they are done so you don't waste time.
He should not be able to build more than 3 cannons at once because the rush happens so early. When I do this rush, it usually goes down before 4 minutes. You will either be firing on their nexus at 3 minutes and something, or you will be canceling and transitioning into something else. The later they try the rush, the better off you will be. Regardless, just keep killing anything he tries to warp in.
Eventually, he will either run out of money or you will have the tech to stop the rush outright (ie, marines, zerglings, zealots). The main thing is DON’T get hypnotized by the probe or the pylon. Just take 4 workers to kill whatever is building.
Defending the Rush - Cannons Up
If the cannons are up and they are hitting your base, that’s very close to a GG. But there are some things you can do.
Protoss
For protoss, it pretty much IS gg. Your only hope is to rush whatever zealots and forces you have to his base, and then hope you can base trade faster. But usually you won’t be able to because he will have cannons there by the time you arrive, and your only recourse will be to nerd rage and call him a noob.
If you have the cash, you can try to expand. But that's usually just delaying the inevitable.
Zerg
Zerg can fight back by getting a spine crawler up. Although you will take a ton of damage, spine crawlers have great range, and they can eventually push the cannons back. Because of creep, cannons can’t really get close to the main hatch anyway, so spine crawlers can help fend it off.
You can also try to use the queen to snipe the pylon if the toss has mis-positioned it. But, that's unlikely. Because of the creep, I rarely rush zerg with cannons unless there is a map like desert oasis that is prone to outside pylon rushes.
Terran
Terran has the best response options for anti-cannon rushing. The first thing you can do is move your base. Take ALL of your scvs and move them to your natural, then fly your command center over there. You can begin production again almost immediately without losing a thing. And since your barracks are already building, you can start cranking rines to go smash his base with.
Because of the placement of ramps, its difficult for a cannon rusher to sneak in between you and your natural. They usually have to go to the far side of your base where they can hide. So this line of retreat is usually open.
If the natural is not open, you can fly the CC to another expansion and just move the workers there. You can even move the CC to the OTHER side of the minerals sometimes, depending on the map and the angle of the rush. The main idea is that you GTFO when the rush starts and move to a new base.
If you can’t move and the cannon placement is bad, you can sometimes get the marine to snipe the pylon without the cannon hitting him. Do that if you can, then reinforce the marine. If you can snipe the probe, do that too. Terrans have the best shot at eliminating the probe because marines are ranged, so take advantage of it. But don’t rely on it. Good cannon placement usually makes this option mute.
Step 6: Responding to Rush Defense
If someone defends your rush, then as a good rusher, you need to be able to respond. These are things you can do if you see them defending.
Build Few Cannons
The most important thing that you need to understand is you want to build as FEW cannons as possible. I usually go for 3. The more cannons you build, the farther behind you will be if and when the strat fails.
If you make him run away, you are not necessarily ahead. He might have more minerals banked and a higher worker count. This is your chance to pull back to even. It's going to take him some time to get productive again. So, use that time to get your economy up. In particular, I like to expand into their base as soon as they run.
Transition into Gateways
If the person runs, they usually can’t run far. By this time you are behind on probe count and tech, but the disruption your harass caused probably evened that out. What you need to do now is get units. You should have a nexus full of chronoboost. So, build gateways and CB some zealots.
I usually build the gateways by the cannons, and then rush down and smash the natural. If they aren’t at the natural, I scout for them. But I usually keep the gateways with the cannons. A lot of times there are left behind buildings in their main. Just destroy those as you start to churn out some zealots.
Expand to their Base
Once I have enough minerals, I take their base as my expansion. You already have static defenses up in the form of the cannons and you already have gateways, so the expansion becomes my main. This is how you get back in the game economically.
It’s effective. Plus, it’s salt in the wound: All your base are belong to us. Literally.
This is also great because people who get rushed usually target your original main. Because of that, I usually just cannon it up a little and treat it as an expansion. I love the surprise when they march into it, fight through the cannons, and realize that there was nothing there.
Step 7: Nerd Rage
If you have followed along diligently, you have learned the ways of the cannon rush and successfully rushed someone. Prepare to receive your reward!
Nerd rage is a confection sweeter than honey, an ambrosia of the gods. Savor it. There are many ways to enjoy it. Be magnanimous in victory. Offer tips. Comfort him. Talk shit. The options are endless. Stockpile witty sayings and pithy remarks that you can use to rejoinder the vitriol that will be heaped upon you.
Some typical quips:
Loser: “You $@#$%#@$ noob! I will kill you! You SUCK!!!!!”
Loser: “I bet you are in the bronze leage you !@$!$##! loser”
Loser: “You @%$#!$ cheeser, that !@#$ will NEVER work again!”
Feel free to respond in the way that amuses you most.
There may come a point when you start to feel bad about cheesing. Don’t. Terrans don’t feel bad about playing their POS overpowered race. So you shouldn’t feel bad about cheesing. It takes a lot more skill to do a cannon rush than it does to do 3rax 1A GG.
And yes, anyone who says cheesing doesn’t take skill obviously isn’t very good at it.
Anyone can cheese a noob. But to cheese platinum and diamond level players, you need a bit of skill. A sliver of luck. And a touch of grace. If you learn to recognize your opportunities, you will have a viable opening that can end games quickly and crush your opponent psychologically. And who doesn’t want to do that?
Think About It
Stealth aside, the reason this rush works is because of two factors. The first is build timing. I can build a pylon and a cannon faster than you can complete a gateway and boost out a zealot. Even if the zealot gets out, he can’t kill the cannon or the pylon alone. It takes a long time. You will have to use workers.
The marine is in the same boat. But, because he is ranged, he is more difficult to handle. But only a little. He can take the probe out. Still, he can’t kill a pylon or a cannon very fast, and it becomes a race. Unfortunately for the defender, it is a race in which I know all the correct decisions, and you probably don’t.
Therefore, you will be analyzing while I am still in book. This gives me an advantage. The chances of you calculating the right response and not making a mistake are slim. On the other hand, I know exactly what to do based on your decisions. So, I can react instantly.
The second reason it works is pressure. Building stuff in someone's base puts them on tilt. If they make a mistake, they lose. If they don’t, I simply cancel my stuff and walk away. Total investment is usually less than 100 minerals on my part for a failed rusher.
I will be behind in probe count, and slightly behind on tech. But not that much. I have a forge and a nexus full of CB, and I can often make that ground back up. On the flip side, the disruption, both economically and psychologically, that it inflicts on my opponent is often be worth it.
There are two ways to win in chess... playing the board, and playing the opponent. This opening is designed for people who like to play the opponent.
Anti-Cheese
One of the positive side effects of this line of thinking is that if someone tries to cheese you before you cheese them, you have a great chance of winning. You will know that the enemy is cheesing when you enter their base. At some point, you will realize they have NOTHING. At that monent, your ears should perk up.
Fortunately, having an early forge lets you defend almost all of the early rushes you will face.
Zerg Ling Rush
Build two cannons by your nexus. You will crush 6 pool or any other zergling rush. Just make sure to use the cannon nexus and forge to block off 3 sides of the main pylon. Or, build another pylon at the base. If they can’t get a surround on the pylon, they are toast. Use probes to attack when they enter the line. I often repel this attack without losing a single probe.
Note: I used this to defend against Zerg rushes in SC1 on Bloodbath. If you haven’t played it, it is a map with a VERY short rush distance. This always worked. Just build a tight base. Don't spread your structures out.
Terran Proxy Rax
Terran proxy rax rush loses to 2 cannons by the nexus or wall off on the choke point. Just cannon up at your base the cannon rush them at theirs and when they run, take it as an expansion.
Terran Early Reaper
If you see the early reaper, just build two cannons - one in your mineral line, one on top of the nexus opposite it. This keeps the reaper from hitting probes or sniping your nexus or buildings.
Positioning is key. The reaper will try to find an area not covered by cannon field of fire, so place carefully. Never build your cannons at the choke point, because the reaper will laugh at you.
Protoss Proxy Rush
You win this match up by building 2 defensive cannons at your home base and an extra pylon, then continuing with the cannon rush at his base. Alternate building cannons at home and away, as the longer it takes, the more zealots he’ll have.
When you enter his base and see NOTHING (no pylon, no gate, no buildings), you know the proxy rush is on. Cannon up at your main, then beat him with cannons at his.
Protoss Cannon Rush
This is all about speed and knowledge. If you see the forge in their base, scout your own base immediately. If he has not built any cannons yet in your base, build a defensive cannon. Don’t build this one near your nexus... build far away it to shut off his angle of approach.
Most cannon rushers have not taken the time to study the opening, so you can beat them the same way you beat someone with an in-your-face rush... with superior knowledge.
If the cannons are already warping in, hope to god that he doesn’t have a defensive cannon already up. Then, take 4 probes and kill whatever is building. Use 4 probes for EACH thing he builds... so if he builds 2 cannons, use 8 probes total. If you run out of probes, queue the groups up to hit the incoming cannons. While you are doing that, you will have to decide if you can still cannon rush him, or if you need to cancel and start teching.
All In Build
There are variations of the cannon rush that you can use and try. One of them that is funny is the enemy base forge. To do this, you run to the enemy base with your first or second probe. You build a pylon right in their face. Then, you build a forge right there next to it in their base. Once it finishes, you buy cannons.
It sounds stupid, but unless they react correctly, they will lose. They will NOT have a gateway or rax started, and they might not even have a pylon or supply depot. Anyone who tries to build a defense to this loses. There is no way they can get any cannons, zealots or marines to help them in time.They need to send 4 workers to kill everything you build, not target the pylon, not target the probe.
I don’t like this build because if it fails, you die. Not only do you lose they pylon, you lose the forge too. There is no way to recover if this doesn’t succeed. On the other hand, it's extremely exciting to attempt, and when it works, NOTHING generates more nerd rage. The change from curiosity to annoyance to panic is priceless. I recommend trying it for cheese connoisseurs.
And if you can do this to a terran, then so much the better. You will be doing everyone a public service.
Subscribe to:
Posts (Atom)