|
On December 08 2010 06:11 slam wrote: So would walling off with a stalker on hold position be a good solution to this? Stalkers also are better for defending against baneling busts, right?
You can't get a Stalker out in time to fend off a rush, and their damage is pretty pathetic vs Zerglings compared to a Zealot.
|
Hopefully Blizzard gets a hold of this info, I'm assuming they will patch that.
|
if you hold a probe right behind the zealot and make the harder kind of wallin with the zealot inbetween core and gate it should be able to hold though, I mean performing this trick would cost you a lot of lings then at least.
|
Wow, what a load off my fricken mind. I remember this from Beta, and I thought I remembered it being patched. I have lost a lot of games because my hold-position Zealot appeared to have lost weight or something.
At least now I know. Still sucks.
|
I noticed this on the PTR and started doing ZvP on live. It's really frustrating as protoss but I think walling off is your best solution.
|
Even without this zergs need to realize it will only cost them like 4 lings to kill the lone zealot.. guarding the wall.
I believe the timing is in such a way that the zerg should be able to get a steam of lings in while the 2nd or 3rd gate is going up..
|
On December 08 2010 06:15 Sleight wrote: What about Stalkers? Sentries? Probes? Yeah a lot more testing should be done, the replay only had lotsa speedlings. How about like 8 normal zerglings? thats more realistic early game since no stalkers would be out at that point in most cases.
|
On December 08 2010 06:15 branflakes14 wrote:Show nested quote +On December 08 2010 06:11 slam wrote: So would walling off with a stalker on hold position be a good solution to this? Stalkers also are better for defending against baneling busts, right? You can't get a Stalker out in time to fend off a rush, and their damage is pretty pathetic vs Zerglings compared to a Zealot. I don't think that a 6 or 10 pool rush would really be a problem. You can just use probes and zealot to defend against that. I'm talking about runbys where the zerg has like 15-20 zerglings. In my opinion that are the only ones that are a real threat.
|
Lol added reason to cannon block a zerg now
|
On December 08 2010 06:25 anTi_ wrote: Lol added reason to cannon block a zerg now
not anymore once the new patch kicks in.
|
this is stupid and must be patched, says the zerg
|
i had a guy pylon block me with 3 pylons yesterday on PTR.
i said "dont let the patch change discourage you from cheesing"
he said "ok"
|
On December 08 2010 06:29 AnAngryDingo wrote: i had a guy pylon block me with 3 pylons yesterday on PTR.
i said "dont let the patch change discourage you from cheesing"
he said "ok" I'm interested to see how the pylon block will evolve in high level games or if it will end up being pretty useless.
|
If blizzard don't fix this, I will be mad. hard time
|
because protoss is not underpowered enough of course!
|
Thread has hit required length for Blizzard to eventually pay attention to it. Just need to keep it bumped for the next couple days and we can be guaranteed that it will be fixed
|
What map is that replay? It's not the 'unit tester map' that pops up when I search on battlenet.
|
Yeah this has been going on for a while, it's happened to me more than a few times, you really need to have a second unit stacked up behind the zealot to prevent him from just getting pushed back.
luckily the kind of zergling aggression that is required to really leverage this (before your second unit comes out to help block) is economically devastating to the zerg, if you are able to stabilize off of it then you'll usually end up being alright.
|
hold position zealot can hold the spot since early beta. This was a problem during the early days, that zealots couldnt hold zerglins (oh my gawd, they had to get a sentry) so they fixed it, as long as the zealot(s) dont switch to attack move they wont get pushed away.
|
this have happend to me accidently so many times (though some of them probably were poor placement) Nice discover, hope it gets patched soon.
|
|
|
|