Star craft 2 : Massive Queens not affect Protoss

[Antton]

In star craft 2 making Queens’s massive component doesn’t nerf protoss self-protective capability. You possibly will say oh what about queen rushes which beset beta? Queen rushes were stopped up when queen speed off creep was nerfed. You capacity be clever to do 10 min queen’s move forward, but 10 min is adequate time to scout and act in response to this move forward. On an additional zerg can protect beside sentinel. Whole speed roaches? JulyZerg at a standstill did not yet approach lock. Speedlings-hydra-speed roaches-Up one base-creep spread-up in supply-and alternative off investigate to holdup onward pylon? JulyZerg still couldn’t succeed. What else might have julyzerg completed game 5 to have saved himself since the push and the residual 20+ stalkers formed on two bases? Queens as a enormous component construct it so that Force fields cannot immediately be terrified in the middle of an army and permit protoss to win.

[RyanInt]

You can't do that for the reason that then every Zerg has to do is proxy hatch or send a queen through each early game roach run. The game is all right. If July had scouted the run or construct even 1 spine crawler or a consignment of roaches at his natural faster every the FFs in the world wouldn't construct the least bit of dissimilarity. Don't make bigger with no a plan to mark an imminent rush and be able to protect the development. It's simple. Critically one and all would freak fate build and proxy produce in Toss naturals.

[AZUL]

more than half the games that July zerg played 3/5 he scouted 4 to 6 entrance built/building and still then, still could not stop the move forward. If ST_JulyZerg act in response except motionless could not win, it’s not the player, it is that FORCEFIELDS is a broken down spell and you will not acknowledge it. This is immediately cheese. Scout the cheese obliterate it, win the game. Same steps for all competition. I do not be acquainted with what deluded description of rush you have or are familiar with, but queens off creep cannot be quick which was set in the beta.

[RockOn]

In the making for a queen to walk crossways the map would hold up a roach move forward by a vast quantity and provide the Protoss more than sufficient time to get ready for it. So no, it will not construct Zerg imba. Improved yet, are you acutely suggest that Zerg would put a hatch in their adversary natural to obtain a number of creep spread, and then spawn a queen there and then go after that up through a hurry? In addition, you have to pay out 500 minerals to obtain that hatch and queen up which is a batch fewer minerals you could be spending on attacking entity.

[Squibbit]

You be acquainted with that Protoss would extremely likely scout a hatch morphing on their usual, then the hatch in point of fact has to, you know, construct. And throughout the that whole time the protoss could protest downward there and kill the emerge, keep in mind no queen is there up till now so FF's will still be now as loltastically commanding, allow alone the information the Zerg will not have many component out so early on in the game so a few zealots might do the job. Then once the hatch has in conclusion spawned the Zerg then has to create a queen out of there. And throughout that whole time the Protoss is get ready for the sprint. If he can't grasp it off by then I consider its fewer "Queen OP" and additional "Protoss player was hold back".

[Wyvern]

A substitute hatch through a roach rush construct will possible not be feasible because the queen has a 50 second build time. That's an extensive time intended for toss to observe the substitute hatch and kill it. To obtain a queen beside through a roach rush build would interruption the rush by approximately two and a half minutes, if I am recollection build times in the approved manner. Not to talk about you could immediately kill the queen; I would be extra worried on the consequence on Protoss midgame move forward.