|
I can't recall anyone doing this at high masters or pro level and I wanted to show it and get the community's impressions. Basically is this a terrible cheese that's going to fall apart every time as I progress or is it reasonably viable? I would call it cheese because it does rely on your opponent not knowing it is coming and starting the cannon 20 seconds earlier could easily stop it. However you don't have to do it blindly as most 2 player maps you can get your overlord to the natural in time with the new overlord speed to abort it and it requires the protoss to play along, block your natural and then follow your drone to the third.
The build order:
for 2 player maps send first overlord directly to the protoss's natural
9 overlord 13 pool send a drone on 14 supply to attempt the 16 hatch attempt 15 hatch
i) If successful, carry on in a normal macro game, ii) If blocked head to the third and attempt to build a hatch there, if the probe does not follow play a normal macro game, send another drone from the main to the nat to see if the pylon gets canceled, if it does, take the nat and play a normal macro game if you like. iii) If the pylon is not immediately canceled and the probe is still blocking the third, begin aggression.
At this point you pull 4 drones, skirt the pylon at the nat and send them to the protoss's natural without the protoss seeing while the probe is blocking the third, they will stop the first photon cannon finishing and prevent the probe at the nat from finishing the wall in. Send 3 more drones about 15 to 20 seconds behind to bolster the 4 original drones for when the protoss pulls his probes to hold.
When the pool finishes you will make 6 lings and double extractor trick to get a queen build and an overlord with your next 100 minerals. As soon as you have extractor tricked the queen out, you can send 4 more drones. I've been sending 3 drones so far but I think you can make it a lot more aggressive if you send a ton more drones since you only need 8-9 drones to non stop produce lings and the game will be resolved long before you hit sustained production.
The reasoning:
All you're trying to do is prevent the wall in from going up, at which point you're trying to kill probes first the same as if you had 7 pooled except the pylon for the cannons in the main will be much later and you have 7 drones with your 6 lings to kill off probes, you will kill off a good number of probes and if he's going to hold you pull back just enough to to let your next set of lings arrive and the natural will be forfeit.
It's up to your own judgement when to stop producing lings if you aren't going to outright kill him and start making drones and expand. If you don't outright kill him and he gets his wall up its usually after losing a shit ton of probes holding to get the wall up as long as you didn't fuck up and he got it up before your 6 lings arrived.
I'm finding that it's often pretty obvious because you'll trade lings for a ton of probes in order for the protoss to get his cannons up and even then won't be able to save his natural and his main most of the time. Sometimes even if a cannon in the front does finish you can run some lings up to the main to kill it and move some lings behind the natural out of range of the photon cannon and deny mining while you drone up and prepare for a macro game from far ahead. On top of this when the engagement is over you have an overlord in his base on 2 player maps and almost there in 4 player maps when he will be no where near centuries or stalkers so he can't sneak anything past you.
Some replays:
http://drop.sc/193453 http://drop.sc/193454 http://drop.sc/193455 http://drop.sc/193456 http://drop.sc/193457
Please tear this apart, but please don't bother analyzing my play, I know I'm bad, it's the build I'm interested in having critiqued.
|
It has the potential to be good, but if the Protoss knows how to time his FFE against a 13 pool you'll never get through his wall unfortunately
Edit: wrote 15 hatch instead of 13 pool :/
|
Perhaps I did not make this clear in the OP, but the whole point of the timing is to get the first 4 drones out and heading towards the Protoss's natural whilst the probe is trying to block your hatch at the third and while the pylon at the nat is still building and does not have enough vision to see your drones pass by. If he only sent one probe and he goes to block your third he cannot scout the first drones.
Edit: In response to your edit:
I'm not sure you watched the replays, the 2 waves of drones are specifically designed to keep the front door open by blocking where the protoss wants to build his gateway and kill the first photon cannon.
|
Could see this working even at masters but a controlled response will probably be enough to hold and be ahead. If zerg pulls 4 drones to attack with and they arrive at the protoss base and protoss pulls 6-7 probes (which'll be the equivalent of 4 drones when it comes to mining time lost by you both) then I can only imagine protoss getting his buildings up in time to block the zerglings. Might check a replay to be sure but I feel like..... this is a bit too out of the box.
|
I do a lot of 4-5 drone pulls against nexus FFE, mostly on smaller maps or in bad positions (e.g. Antiga with your third next to toss main). Works best on a map with a wide natural (Antiga is perfect). Generally works in those types of favorable conditions, but it is more all-in and dead-if-scouted than not. This is low masters NA.
Basically, if they pylon block and go nexus first AND you're close enough, you can do damage--note that just getting pylon blocked at both natural and third does not mean that the cannon is late, so OP's criteria are incomplete. Often you take the low ground and he has to pylon wall at the top of the ramp, giving you a serious advantage (free gateway and forge), he's contained for a bit.
The problem is that your drone pull cripples you. So if you cannot break the natural, you will probably lose. And if he sees a handful of drones with his scouting probe, he will pull probes and easily shield the cannon while blocking the ramp. Even if you run into the main and drone up, he still has that second nexus, and you still lost a lot of mining on those drones, and you don't have your natural or third started.
It's pretty all-in, BUT I think it is a smart risk to take (I do it off 14pool, btw, and again, only if I see nexus first in close positions or on a small map) if his cannon is late and the map allows for it. It is an unexpected way (possbly the only non-early pool way) to nudge nexus-first from "greedy" to "risky and punishable"--something I have been trying for two seasons now. Something to have in your arsenal, but certainly this is not standard play to use when pylon blocked, as a safe forge-first will, in my experience, finish too quickly. I have not tested this extensively, but i do believe that it becomes too risky at that point.
|
|
|
|