Darks opening also made 0 fuckin sense so it was inpossible for Neeb to recognise. He respected the threat of allin because he's so good. As @RotterdaM08 said if he just went across with an early attack, kept the creep back or started trading when the SH count was low he crushes
-
-
Afficher cette discussionMerci. Twitter en tiendra compte pour améliorer votre fil. SupprimerSupprimer
-
-
-
I liked the early zealot runby Neeb did. Should he have done more? Seems hard to defend though if you're spending warpins on zealots that go across instead of archons.
-
Tonnes of this whilst your main army baits locust waves. Besides the SH youre looking at a low eco roach player. Zealot counters and any engage away from locusts is usually pretty good
Fin de la conversation
Nouvelle conversation -
-
-
Ugh, I don't like that map
Merci. Twitter en tiendra compte pour améliorer votre fil. SupprimerSupprimer
-
-
-
One of the questions we debated was why you don't kill the rocks outside 3rd so you can more easily push back swarm hosts. Too easy to push w Locusts then? Any thoughts?
-
I think it would have been a good idea! It's scary to let the mass of roaches in and also the roaches threatening the sides kept him spread put and pinned back so i get why he didn't find the time to do it
Fin de la conversation
Nouvelle conversation -
-
-
Didn't see this game yet, but what if Zerg goes SH nydus with units burrowed EVERYWHERE on the map? Impossible to bait SH if they're moving and hitting where you are not or are burrowed in small packs all over the place.
-
When 5000apm deepmind AI gets good enough to pull this off we'll get to see! Till then it sounds a mite ambitious :P
- Voir les réponses
Nouvelle conversation -
-
-
the tried and true method has been to let Zerg players force Blizzard to redesign it through toxic ZvZ
Merci. Twitter en tiendra compte pour améliorer votre fil. SupprimerSupprimer
-
-
-
Ay thanks mate
Merci. Twitter en tiendra compte pour améliorer votre fil. SupprimerSupprimer
-
Le chargement semble prendre du temps.
Twitter est peut-être en surcapacité ou rencontre momentanément un incident. Réessayez ou rendez-vous sur la page Twitter Status pour plus d'informations.