EPTAlso, when we talk about the warpgate mechanic issues, it's important to remember that the problem only ocurrs because of the synergy between warpgates and pylons being built anywhere.
Considering all this I came with what I believe is the best solution for all the issues of P early defense while solving some of the warpgate issues at the same time:
So here's my proposal:
- Warp-ins are only possible inside a Nexus or MScore range. No longer dependent on pylons.
- MS core has no offensive capability.
- Warpgates are built as warpgates, regular gateways are removed.
- Warpgates cost 200 minerals instead of 150.
OK, let's see how all this plays out.
- MScore design is much more consistent, becoming a true mobility provider for the armies, allowing both warp-ins and recall to nexus.
- If one P goes for MScore, the other will have the option of going for a more eco build and still be able to generate an army to match the attacker's because the MScore does not add offensive power. This is very different from the current gameplay because in WoL if one P goes for warpgates the other P is also forced to go warpgate otherwise he will be producing army slower inside his own base.
Now protoss has a real trade-off for his gain of mobility.
- The defender will be able to end a Protoss all-in by sniping the MScore, which is easier than finding and destroying all the pylons.
- Protoss does not gain significant offensive all-in power in the other match-ups because the MScore compensates for the cost of warpgate tech. This can also be fine tuned with the gas cost and build time of the MScore, without additional complex variables.
- Regular gateways being removed is cleaner design because they only exist to prevent the very first zealot from being warped inside the opponent's base. This problem is also solved, so no longer need for this reminder of a design issue.
- Warpgates remain as the special production mechanic that adds 'flavor' to the protoss race, without creating as many issues as they do in WoL.
On a side note: I'm not a big fan of the 1-limit unit. But if Blizzard really wants the MScore to work, I think this is a much more consistent solution. Maybe a limit of 1 per nexus and a dissociation from Mothership (and name change) would work even better. It would work like a Nexus mobile add-on.
P.S. I know people will think of gameplay implications that I didn't consider, but please remember that there are still many unfinished issues with the current MScore.
I'm not trying to come up with a final and refined solution because not even Blizzard is capable of that.
The only real question here is if this is a better starting point than the current MScore.
