Cfrgtkky

I am currently making a run 'n gun platformer, in which the player dies instantly when they get hit. I'm curious how to make this feel fair. I'm aware of putting checkpoints frequently enough, allowing the player to retry almost instantly, and merciful hitboxes. But I'm curious to know how I should go about level design? Run 'n guns are much different from sanic-speed wall jump platformers like meat boy.

You see, games like Hollow Knight let you learn how to avoid taking hits early in the game by giving easy challenges. If you get hit by something unexpected in Hollow Knight, you can always focus and gain some health, and it wouldn't feel unfair. If that happened in my game, that would feel unfair.

Since I'm designing a Megaman-X like game with a boss at the end of each stage, how am I supposed to go about teaching the player how to dodge fast moving projectiles that you would only know how to dodge after seeing how they act?

And yes, there is going to be a first level before you can go play the other ones in whatever order you like.

That's the trade-off to this kind of game play design, the player is expected to die many times to learn mechanics and Boss abilities. To make those deaths palatable to the player I have a few ideas:

1) nothing can be random, everything must have a pattern that can be learned. There is nothing more unfair than dying to an attack you've never seen before and will probably never see again.

2) hit boxes should be precise and dependable, don't make them "merciful" because then the player will feel out of control, and the player should always feel in control.

3) reaching a checkpoint should be a Big Deal, make reaching checkpoints exciting and use them to pace the game so the player won't get fatigued playing nonstop. Think of Checkpoints as a pacing mechanic, not a fairness mechanic; the fairness comes from game play and not the rest stops in-between all that playing.

4) alternate easy progress toward a checkpoint with skill+learning challenges to reach the next, let the player feel good about playing better. If the player has immediate feedback like that then new challenges feel fair because they know that it can be learned, just like they did before!

5) bosses should be a Huge Payoff, and you might consider adding a scoring system to encourage players to go back multiple times to achieve special conditions and raise their performance scores. While the player may die a lot it feels fair if they are working towards an extraordinary goal.

In addition to Patrick's answer:

• Time it takes to retry needs to be short, borderline instantaneous. Take Super Meat Boy as an example. Compare with Teslagrad's 4 second death animation.




• Time it takes to regain your progress should also be relatively quick. This goes along with Patrick's comments regarding checkpoints. Taslagrad is pretty good here, as you respawn at the entrance to the room you just entered and most rooms can take only seconds to completely transverse, no more than a minute at the high end.




• No long term consequences beyond time lost. Don't penalize the player's exp or in-game currency. Such penalties lead to the player complaining about cheap deaths. For instance, in Teslagrad I found a particularly hard puzzle that kept repaving me facing towards the door I entered, and if I tried to start the puzzle without first turning around, I'd kill myself by miss-timing a jump+ability usage. Which cost me am additional 5 seconds as. I waited for the death animation to finish.



• 
  

  Put limits on the frequency, accuracy, and coordination skills required when building your puzzles or other challenges. The tighter the accuracy or timing the worse off your game will be, as those players that have issues (be they handicapped or just less skilled) will grow frustrated and rage-quit. This is particularly important when it comes to boss fights. "Do the thing 3 times, 3 times" is the biggest complaint I've seen about Teslagrad. Everyone rapidly figures out what they need to do, but actually doing it often requires incredibly precise timing or movement. The act isn't even that hard, its pulling it off 9 times in a row without getting hit that's the problem.

  
  
  
  
  
  • This is also why I hate Super Meat Boy myself. The slippy controls combined with the pixel-perfect jumping, frame-perfect timing is something I just can't do.
  
  
  
  

The best thing you can do when dealing with situations like these is to study other games that share mechanics and systems with what you intend. Given your description, the two off the top of my head that I think you should most look at are Metal Slug and Contra. Both involve gun usage as their primary mechanic in a sidescrolling platformer environment, and both involve one hit and dead mechanics like you describe.

Some things that you will notice in games like these is that because getting hit is so costly, there are almost no "surprise" attacks. Nothing moves fast unless there is a huge telegraph to go with it that clearly shows that you should move/jump/whatever so you don't die. You need to give people opportunities to see how things might kill them via a combination of telegraphing and make sure that the oncoming death is slow enough that they have a fair amount of time to react before it actually hits them.

Another thing games like this share is a lives system as opposed to a checkpoint one. Where death respawns you right where you died a moment or two later, usually with a little mercy invincibility to help you get through whatever just killed you. This allows you to use your number of lives as a kind of limited pool of mistakes available to you without breaking flow entirely. While this might not be strictly necessary, the ubiquity of it is something I would analyze for game feel, especially comparing with other popular "one hit death" games like bullet hells.

Finally, a critical piece is that how the game responds must be predictable! Successful play and flow in games like these requires understanding and abusing the mechanics of the game to enable deathless play. Randomness is not entirely out of the question, but things like enemy spawns, enemy AI, and bullet patterns should be very understandable and predictable so that skilled players can use that information to their advantage. Getting through a section because it was easier than usual or getting stymied because RNG hates you both feel bad when the mechanics imply it should be down to your skill.

Rather than one hit dead, short of strong bosses and special enemies, why not use injuries as a way to make things feel real. Injuries tend to slow player movement(jump lower, run slower), impede vision (blurry screen), hearing (gun shots sounds lower or louder depending) or any other the users other senses.

Or if you are definitely focused on keeping the one hit die, take lessons from Contra, frequent armor drops, lots of life drops, starting with lots of lives help. Though you have to create a good enough balance, that allows you to give the user just enough lives without the user feeling as if you are making the game too easy. User testing is a must for that option.

Another Idea from an older game I used to play, was a check point or auto save feature, when you make it to bosses.

Allowing friendly fire between enemy units: This allows the user to use explosions and other enemies fire to make the game a bit more forgiving, if they are talented enough to dodge missiles, shots etc. Which relates to predictability, another answer her discusses this a bit.

This one may be a bit far fetched, but adding vehicles (tanks, plans, cars, horses??) that can take a few shots before exploding at certain parts of the level, that may be littered with enemies.