I dunno. Why have 2 versions of the same race?Hawki said:Oh boy, here we go.
I'm with Pyrian. Singleplayer shouldn't be dependent on multiplayer, and vice versa. Since the Diamondback has been brought up, yes, why not use it in the campaign? The campaigns are their own thing with their own design. Something I love about the gameplay of both is the level of army customization, and mission variety. HotS was just the same, how we could evolve the zerg how we wanted, and choose between traits on a by-mission basis, working in game terms, and serving as a case of gameplay/story integration (fitting the zerg, given how fast they adapt/evolve). It's why in gameplay I'm definately looking forward to LotV, given that a) we'll have the customization and unique units, and b) it's fitting in with the protoss with the branches concept for the Khalai, Nerazim, and...something else (Tal'darim, I'm guessing), and c) mission design.
So no, these things shouldn't be in multiplayer, due to the amount of overlap and balancing issues. So on one hand, multiplayer gets to be balanced, and on the other, singleplayer gets to be its own thing. Best of both worlds.
It's not like unit balance alters the campaign story or something unless that creates unwinnable scenarios which is unlikely.
It's not just the upgrades, they systematically dumb the way a race plays down for singleplayer and that just irritates me.
Just look at the campaign hatcheries for example.
Why can't that be the multiplayer typic 3 larvae until a queen sneezes on it with an active ability hatchery?
Because that's tedious? Boo fucking hoo then either make a quality of life change every zerg player would thank you for (autocast sneeze anyone???) or keep the darn thing the way it is.
I have a feeling they will do something similar to the protoss in lotv.
Like right away you don't need to place pylons for buildings anymore or something.