bradlllzzzz;2291385 wrote: Mr Tags;2291360 wrote:
I love how its nearly unanimous in favor of descope. Who thought flinch would be a good idea in the first place? How does this get through testing?
I understand they were forced to rush this but why not just keep with this at least this.. There was no reason to change it.
They stated that the reason that they changed it is because getting descoped is too "jarring" of an experience. This is what 343i said before the game released.
However, I don't agree with this line of thinking at all. In fact, I find flinch to be more jarring than getting descoped. Descope means that you were able to come back from a battle in which you missed a shot and now you unscope him and then you finish him off now that you have the upper hand. It added another big layer to the meta game and to the skill of ranged firefights.
You were able to ping a sniper constantly by laying down suppressive fire to cover your teamates. Now, that doesn't happen at all and can't happen because the sniper barely gets flinched and can easily recover and land a body shot and send your reticle to the moon.
Shootouts are being devolved into a who sees who first kind of experience. This is not an evolution of the Halo franchise in this aspect. It is actually devolving. This change for the sake of change when no change was needed needs to be changed back to descoping.
Let's just say that this TU holds my future of Halo 4. If it brings in things that will make the experience 100x better, then I will get back on, but if it won't and they keep this(as well as many other issues) in the game, then I can't see me bringing myself to keep playing this game.