|
As of this point I'm still in bronze, but I'm getting consistently matched against silver/gold and doing fairly well, still hoping for that promotion at some point. The following replay is a nice embarrassing loss to a four gating 'toss. It's definitely the MU that's giving me the most trouble. My goal in early game is to get a 5-6 roach rush early, get through his little choke point, and destroy his economy before he can really support four gates and put myself ahead on the eco side.
While I'm pushing with the roach rush, I get my hatch down, set to tech to lair, and drone up. This particular match he had a few more zealots than I'm used to seeing, so my roaches get smashed and he's free to expand away while I play catch up the whole game, ending in one push with collossi that destroys everything.
http://www.sc2replayed.com/replays/122247-1v1-protoss-zerg-xelnaga-caverns
There's the replay, any feedback from those high zergies would be appreciated! I'm almost defaulting to prepping for a four gate, as that's all I see. It's either four gate, or an easy win from a cannon rusher if I can catch it early enough. Comments appreciated!
|
Can't watch your replay ATM ('cause it's my birthday) and I'm not that high in diamond, but I can only recommend against prepping for a 4 gate by default. It's not too hard to scout the front for a few gates, to check his nexus for saved chrono (this might not indicate a 4 gate at low levels, it could just be poor macro) and to see the 1 gas. Automatically throwing down a few spine crawlers every game when you take your natural is a better way to prepare for most eventualities and is a better idea than preparing for a 4 gate when you haven't scouted one. (Yes, people do say not to build static defence when you haven't scouted a reason to do so, but it can be helpful to give you a "safety net" to help you work on improving macro)
Remember to always have a ling outside their base.
Also, aiming to rush roaches to their base can win you the game, but I'd think the 4 gate is a pretty heavy counter to the build. Either make sure (by practising against a computer) that you're getting the roaches out as quickly as you possibly can so you can kill him before he gets too much production, or try a different build with an earlier expand (14 pool 15 hatch). I don't remember the timings for a roach rush, but it might be a build order loss to a 4 gate.
While I won't tell you to abandon the roach rushing, since you can play how the hell you like, I'd suggest that you'd be much better served with a more standard build. You'll struggle to have enough larvae to beat a 4 gate off 1 base, so you really need that expo.
Can't check for replies, unfortunately, but GL with the 4 gates and happy new year.
|
On December 31 2010 18:16 francis163 wrote:As of this point I'm still in bronze, but I'm getting consistently matched against silver/gold and doing fairly well, still hoping for that promotion at some point. The following replay is a nice embarrassing loss to a four gating 'toss. It's definitely the MU that's giving me the most trouble. My goal in early game is to get a 5-6 roach rush early, get through his little choke point, and destroy his economy before he can really support four gates and put myself ahead on the eco side. While I'm pushing with the roach rush, I get my hatch down, set to tech to lair, and drone up. This particular match he had a few more zealots than I'm used to seeing, so my roaches get smashed and he's free to expand away while I play catch up the whole game, ending in one push with collossi that destroys everything. http://www.sc2replayed.com/replays/122247-1v1-protoss-zerg-xelnaga-cavernsThere's the replay, any feedback from those high zergies would be appreciated! I'm almost defaulting to prepping for a four gate, as that's all I see. It's either four gate, or an easy win from a cannon rusher if I can catch it early enough. Comments appreciated!
Random diamond here.... I usually 15 hatch vs protoss, and if it looks like he's going 4gate, just pump out speedlings and get a lot of spine crawlers (like 5). Haven't lost to a 4-gate that I remember recently...
|
I don't think you should be blindly doing a roach rush every game, but I think you're fine with that for now. If you're in bronze I think you just need to memorize your execution. Practice the following build until you can get your roaches to pop at 4:40 or earlier.
9 OL 12 Pool 16 extractor 15 queen 17 zergling 18 OL x2 (that's 2 overlords) drone to 19 only when queen is 3/4 done, roach warren larva inject immediately inject and roach warren should finish at the same time and you should have about 175 gas, 7 larva and enough to make 7 roaches. In bronze you should probably be able to a-move to his base and win, but try to control them well anyways.
Now many will criticize this and say "this is just a cheesy rush, it won't help you get better". This is true at the diamond level, but not true at bronze, being able to execute any build smoothly is good practice, it gets you used to timing your macro in a relatively unsophisticated way.
|
Well you're opening roach rush so your economy is going to be really bad. If your roaches didn't do any damage (as apparently they didn't that game) then a 4 Gate really shouldn't fail considering how behind you are economically. You won't have the economy necesarry to defend it unless you end up making so many spines that he can just expand and be ahead.
Try opening 14 Hatch vs Protoss, then all of a sudden you're going to have a way better economy and way more resources to defend with. From a 14 Hatch economy I only make 3 spinecrawlers, sometimes 4. The rest is just me cranking out roaches or lings when the time is right and saving energy on 1 queen to transfuse a spine crawler.
As a general rule, if you scout him using chrono on his cyber core twice or more its usually an indication that he intends to 4 Warpgate.
I'm not gonna bother with the replay because its senseless. You went for a semi-all in roach rush that you didn't do damage with. Any Protoss should be able to finish the game off with a large attack.
|
|
|
|