I have a few questions on how to respond to different situations:
1) ZvP 12 hatch, 11 pool vs forge FE. probe finds zerg early quick and builds two pylons to block himself in behind minerals before planting a cannon
2) ZvT 12 hatch vs fast scv on a 2 player map that plants an e-bay where your natural should be
3) ZvP overpool vs forge FE. probe finds zerg early quick and throws down a pylon where your natural should be.
1) I normally never 12 hatch ZvP but against players who choose random I will often 12 hatch. am i supposed to just glitch drones through the mineral to kill the probe/cannons? how many am i supposed to do? are there better responses?
2) i've seen pro's respond to this in a couple different ways but the most common one i see is many drones being pulled off and they just kill the e-bay. how many drones? does it depend on how much health the e-bay has? if anyone knows the details of different response to the e-bay block I would be very interested.
3) i see the normal response in this situation is to switch locations of the natural and 3rd but lately I've been doing a 4 hatch before gas build that I am wondering what people thought of. when the pylon gets thrown down I just build my hatchery next to it but still close enough to the minerals so that 2-3 drones can still mine fairly efficiently. I then take my 3rd at a normal spot and take my 4th where the natural hatch is supposed to be and proceed to a normal 4 hatch before gas build. what I like most about this response is that as a zerg you are pretty much just doing a normal 4 hatch before gas build. the only difference i would say is that you are losing a SLIGHT amount of mining time from a few drones because the minerals are slightly further away but it's not for that long. in my experience so far I have been ahead of the toss from this response.
i made a quick video of case 3 to better illustrate the hatch position. With strategic pylon placement my natural hatch placement can be prevented but so far I haven't run into anyone who has done so.
1) I'd make a spawning pool and pull five drones. Alternatively you can pull 2 drones and just lay the hatchery beside the engine bay. Make your 3rd hatch where you would normally place your second hatchery.
2) I have a good method for this, it works 100 percent of the time. Once my overlord spots the pylons I immediately transfer 3 drones to the natural. I then shift deselect the drone at the very front. Once the front drone is mining and the back two are there I start right clicking to go across the minerals. To get the back two drones stuck you can just spam click on the mineral. As long as the front drone mines, occupying real space, it'll work. If he sends More probes just transfer more drones to repeat the process. You get 2 to kill the probe. I'd recommend practicing this a bit. You also want a mineral patch that's deep inside where they are other mineral patches on the sides.
3) I think that's a really good response, that's personally what I do sometimes.
ZerO provided a very detailed guide on how to deal with a cannon rush behind mineral line at the natural after 12 hatch.
He says you should do the following in order:
Best: Attack probe first to win 1v1 battle. If probe hits first so that you lose the battle run away and move on to the next step.
2nd best: Right click mineral with three drones so that they converge, quickly press stop, and right click the other side of the mineral line (where cannons will be placed) at the speed of light. This will hopefully move the drones to the other side. If you can get enough drones to the other side, you could probably delay / prevent cannons from warping.
3rd best: If the above two fail, then make sunken (+lings) where it can hit a pylon but not be hit by cannons. Use larva trick to move larva to the side opposite cannons. Even if cannon is beyond sunken range, sunken will hit the cannon if the cannon is attacking the hatch. You can probably make around 10 lings before going in.
If your hatch doesn't go down and you only lose 2 or 3 drones, then you're in good shape.