Are Lives Outdated Game Design?

A lives system is easier to understand if it is framed as a relationship between permanent and temporary checkpoints.

A permanent save spot records progress for good. A temporary checkpoint gives the player a shorter retry point inside that saved stretch. If the player dies, they lose a life and return to the temporary checkpoint. If they run out of lives, those temporary checkpoints disappear and the player is pushed back to the last permanent save.

Different games draw that line in different places. Older games might send the player back to the beginning. Later platformers might save at map points or level entrances. In Crash Bandicoot 4's Retro mode, the level is the permanent unit of progress, while checkpoint boxes are temporary.

The modern trend has been to erase that difference. Every checkpoint becomes permanent, and while some games may still count deaths, there is often no meaningful penalty for burning through hundreds of attempts in one difficult sequence.

The argument against lives is straightforward: losing them often means repeating content the player has already beaten.

That repetition can feel especially harsh for new or inexperienced players. Even being sent back to the start of a level can turn one difficult section into a large block of repeated work.

Lives are also difficult to balance. Give out too many extra lives and the system becomes ceremonial. Give out too few and the difficulty curve can spike in a way that feels less like mastery and more like punishment.

That is why many modern platformers removed lives entirely. Without a life counter, designers can tune the challenge around the room, obstacle, enemy pattern, or level itself, rather than around the penalty for failing too many times before reaching a distant save point.

The best argument for lives is that they add stakes. If running out means losing meaningful progress, then every mistake carries more weight.

That pressure can change how players behave. Instead of brute-forcing a sequence through endless attrition, they may play more carefully, learn patterns more deeply, and feel a sharper sense of relief when they finally reach the next safe point.

Lives can also make certain rewards matter. A 1-UP mushroom, a Mega Man face, a coin threshold, a secret room, or a bonus game can become valuable because it buys more attempts before progress is threatened.

That gives designers a useful incentive. Players may explore, take risks, collect optional items, or learn secret routes because the extra life is attached to a real consequence.

Lives do something else that a single permanent checkpoint cannot: they connect several challenges together.

The question is no longer just whether the player can finish one room eventually. It becomes whether they can complete a whole chain of rooms while preserving enough resources for the next one.

Mega Man is a clear example. Reaching a Robot Master is not only about surviving the boss door. The player usually wants to perfect the earlier parts of the stage so they arrive with enough health, lives, ammunition, and confidence to win the final fight.

That kind of meta challenge can be satisfying because performance carries forward. A clean early section improves the odds later, while messy play creates tension without necessarily ending the run immediately.

The problem is not always lives themselves. Sometimes the problem is letting a life count drift wildly across the whole game.

One answer is to tie lives to a specific level, boss, or challenge. Furi does this by starting each boss fight with exactly three lives. The player never begins with a huge stockpile or a crushing shortage.

That approach gives the designer a fixed tuning target. Every player meets the challenge under the same broad conditions, and the life counter becomes part of that encounter's structure rather than a global accounting problem.

It also avoids one of the most common life-system failures: the experienced player hoards so many lives that risk disappears, while the struggling player reaches the hard part with too little room to learn.

Another answer is to keep lives, but reduce the frustration of losing them all.

Kero Blaster sends the player back after a game over, but it lets them keep upgrades and cash. Repeating earlier areas is less painful because the player has still made some durable progress.

The game also turns failure into a small recovery loop. Waking up in a hospital gives access to a special shop where the player can buy helpful upgrades such as extra health or more lives.

Other games soften repetition in different ways. Sonic stages can offer alternative routes on repeat attempts. Roguelikes go much further by making lost progress bearable through randomized layouts, items, events, and situations.

Some games remove lives but keep the broader idea of risk across multiple challenges by making checkpoints part of the player's decision-making.

In Shovel Knight, checkpoints can be destroyed for gems. The reward is immediate, but the punishment is clear: if the player dies, they return farther back.

Panzer Paladin uses a related idea. Checkpoints require the player to insert a weapon, which creates a tradeoff between safety and keeping the arsenal full.

Ori and the Blind Forest lets the player create their own checkpoints by spending a specific resource. The decision shifts from "how many lives do I have?" to "where is progress worth saving, and can I afford it?"

The smartest approach may be to reverse the whole punishment structure.

Instead of punishing players who run out of lives, a game can reward players who complete a sequence without needing many retries. That keeps the mastery challenge intact without making new players repeat large chunks of content.

Bullet hell shooters often allow infinite continues, but the one credit clear remains a respected goal: finish the entire game without continuing. Sonic Forces counts retries against the final score, so high ranks require cleaner play.

Crash Bandicoot 4's Modern mode uses a similar structure. The game still tracks deaths even though it does not use them to eject the player from the level. A gem is available only if the player finishes with fewer than three retries.

This reward-first structure solves an important audience problem.

New players can keep playing without worrying that a difficult section will erase a large amount of progress. They get room to learn the level, practice the controls, and eventually move forward.

Advanced players still get the danger and discipline of a life counter, but as an opt-in challenge. They can pursue clean clears, higher ranks, gems, or other completion goals because they want that pressure.

The same system can therefore support two experiences: forgiving progress for players who need it, and high-stakes mastery for players who enjoy it.

So are lives outdated? The honest answer is that it depends on how they are implemented.

Balance matters. The distance between permanent saves matters. The rewards for extra lives matter. The cost of repeating content matters. The surrounding systems matter. So does how clearly the game explains the pressure to the player.

But the deeper question is why the game has lives at all. Lives can be added thoughtlessly because that is what older platformers had, or because a game wants a surface-level retro feeling.

That is not enough. A life system should exist because it creates the kind of tension, reward, mastery, pacing, or resource planning the game actually needs.

Lives are not automatically obsolete, but they are no longer automatic.

A game that wants tight stakes across a chain of challenges may still benefit from them. A game that wants fast iteration, accessibility, or room-by-room mastery may be better without them. A game that wants both can turn clean play into an optional reward instead of a mandatory survival tax.

The life counter is only one tool for controlling pressure. Permanent checkpoints, optional checkpoint risks, level-scoped retries, retained upgrades, score penalties, and mastery rewards can all solve adjacent problems.

The lesson is broader than lives. Great games are not built by copying old genre furniture. Every system should earn its place through intention, thought, and care.