Peak gliding
Here’s something that used to be common in 3D platformers that I don’t miss: having to carefully time a second press of the jump button at the peak of your jump to maximize your glide and get enough distance to cross gaps.
This is another example of “What’s hard about a game should also be what’s interesting about it." I enjoy exploring these games' spaces and finding the paths through them. I don’t enjoy carefully parsing sometimes-misleading jump animations and executing glides with incredibly strict timing requirements just to get around. I definitely don’t enjoy barely missing those jumps, because it usually means falling and having to redo some amount of uninteresting platforming just to get back to where I was and try again. And sometimes it means losing lives and if I fail enough I get ejected from the level completely, so that punishment gets in the way of exploration.
On top of that, it can cause challenge profile confusion. If you try one of these jumps several times and just barely fail each time, what lesson are you supposed to take from this? Should you assume that the timing window is really strict and you just aren’t quite timing it well enough? Or should you assume that the jump you’re attempting isn’t actually possible and you need to go elsewhere? How are you supposed to “git gud” if the game isn’t clear in its feedback on what you’re doing wrong?
I much prefer the design of letting the player just hold the jump button to activate the glide at the optimal time. This also ties in well with the popular mechanic of holding the jump button for longer/higher jumps, since you don’t have to force the player to release the jump button before the jump’s peak to enable them to hit it again. It does arguably lower the skill ceiling of controlling the character, but for me it’s a good trade-off because it lets you focus the game’s difficulty on the things that make it interesting by making the level design richer without increasing ambiguity and frustration.
0 Comments