Why Ryse is The Most Frustrating Game of E3
I’m on the battlefield. I’m stomping through the corpses of my comrades swinging my sword at anything that moves. I begin a combo, I slash twice and then whooom slow motion is initiated, shi
t is about to get ‘cinematic’. A button prompt hovers elusively above the sword I’m about to drive into the throat of my enemy… argh I’m too slow! The prompt flickers, disappears.
I missed it. Damn.
But then somehow, for some reason, I still complete the cinematic ‘kill’.
Maybe it’s a bug I think, but no. Next time I deliberately press the wrong button. The kill goes ahead, no consequences. Then I try hitting no buttons whatsoever. The kill goes ahead. I put the controller on the table in front of me, the kill goes ahead.
What is going on here?
I ask one of the Crytek people hovering at the booth – is this a bug? Why am I completing kills when I hit the wrong button prompt? Or, worse, no button at all. Turns out it was a deliberate design choice.
“We don’t want the player to feel frustrated,” I am told.
<message edited by PositiveEmotions on Saturday, June 15, 2013 10:59 PM>