Here's the firstsecond game design round table, coming at you with new guidelines, newthe same suggested reading, and a new topic! I have no idea how I'm going to handle the next attempt at integrating the "Conclusion" article in with the base round table, but I'm hoping for a somewhat more successful approach than last week's. Guidelines Here are some of the rules/guidelines it would be nice to have people adhere to (or read and then willingly ignore):

• What I write as part of the topic description is not intended to be an argument for or against a given mechanic, nor does what I write necessarily reflect my full thoughts on an issue. It's mere intended to be an introduction to the topic that, hopefully, more people will expound on.
• The goal here is to talk intelligently about the topic at hand, as such, any responses would hopefully attempt to make some sort of argument.
• An argument does not have to be lengthy to be well-constructed or well-written.
• Don't just toss in buzz words for the sake of using buzz words; the idea here is to discuss the mechanics at hand for the purpose of determining why they are good or bad and to convince other people of your own perspectives. Tossing in buzz words "just because" does more to segregate a discussion than promote it.
• This post will actually be closed when the deadline is up as to keep the discussion fairly self-contained. The closing date for these is up in the air at the moment; this thread will be closed either a week from today or two weeks from today (depending on the number and quality of responses received).
• Don't be afraid to generalize your points as you discuss points with users. It goes without saying that a good game design may depend heavily on the game it's being used in and the way it's implemented, but the idea here is to pick out great ideas and argue them for their intrinsic worth.
• Don't get too caught-up in minor details and always realize that, generally, the goal here is to make intelligent arguments to comprise a design discourse.
• Please, please, please use your real names in your post if you feel comfortable; the resulting article just feels awkward when I have to reference a bunch of aliases.

Suggested Reading The most important and relevant work which relates to this discussion was actually written about ten years ago by Doug Church: "Formal Abstract Design Tools". It's a great read for any designer. Round Table Topic -- The Death of Death There has been a slow and steady progression of the role that death plays in video games since the days of Ghouls and Ghosts and Super Mario Bros. No longer are most games tied to the old tenet of providing a player with an arbitrary number of lives, typically three for some reason, before the player is sent back to a previous spot in the game. This was a particularly brutal practice back in days of arcade games (which the aforementioned Ghouls and Ghosts and Super Mario Bros. were no doubt influenced by) where the goal is to punish the player and, more to the point, convince the player to insert an additional quarter or so. There were also extra lives given to players along the way to sort of feed the mini-addiction that these arcade-inspired games needed to feed in order to get players to cough up more change. This practice has persisted in the industry for ages to the point where designers still treat death and the process of player punishment much the same as we have for ages. Game developers and designers have largely abolished the system of giving players a finite number of tries or lives in a game, but so many games still cling to the concept of a player having a "life" to work with. This approach to handling the mortality or failure cases for the player can often lead to frustration (oh hey look at that) and that, for most titles, is not a desirable trait to aim for. There will always be the occasional Ninja Gaiden that will be released where designers very intentionally challenge player's skills. These kinds of games rely on a failure case as a means of reinforcing the lack of player skill or, alternatively, enforcing a certain in-game aptitude. There have been a handful of recent AAA games which attempt to make death less deadly. One of which is Lionhead Studios' Fable 2 which allows the player to die but then instantly resurrects him/her with permanent aesthetic scars applied to the player's avatar (also a minor experience loss). This mechanic still allows players to die and experience a failure case but it does not impede their progress through the game or, really, make for much player frustration (faux-challenge). The most recent and notable game which attempts to make its players think about death differently is Ubisoft Montreal's Prince of Persia. Prince of Persia treated death as a mere "misstep" and, essentially, gave it players an incredible number of mini-checkpoints that they would be restored to in the event of failure. Should games continually rely on death as a means of enforcing player skill? Is "death" the best way to do that? Is the current system of dying and returning to some designer-specified game checkpoint the best way of managing a player's progress through a game? Dying isn't fun, but is overcoming what caused a player to die before fun (and worth the annoyance of repeating a gameplay segment)?

Computer games that involve lifes often (even if only remotely) resemble simulations of life, and transport some of the authors views and experience with life. And life is deadly, we all know that. Being able to die in the game maybe makes the gaming experience richer, because as we (players and game designers alike) know that simple truth, that there can be fatal events, we can relate more and easier to it and create/play more lifelike games.

Losing the three lifes are three non-fatal failures to the player, and it communicates the simple rule of thumb:

If at first you don't succeeed, try harder.
If you don't succeed at the second attempt, try even harder.
If you don't succeed at the third attempt, give it up. There's no need to make a fool of yourself.

There'll be so many ways to handle life and death in games as there are game designers. Diversity is good. Personally, I like PoP *and* NG.

I think this topic ties strongly in with difficulty within a game. It is all about balance. I'll use two extremes to explain my point. In the first game, there is no punishment for failure. Death (or equivalent) is simply not possible as you have infinite health. In game B, if you die once, which is perfectly possible, the game resets. You have to start again, your save wipes.

The problem with the second one is fairly obvious. If you played a game for more than about 20 minutes and you had to do all that again, you simply wouldn't.

The problem with the first one is there is no challenge. If there is no challenge, there is no reward. Not only do you lose all sense of realism, and hence, immersion, the game ceases to be tense in any way. You no longer feel connected to the world or your character. If you can't fail, there is no point in succeeding. You'd probably turn the game off just as quick as option B (unless the game isn't focused on failure/success eg. in an exploration game, in which case everything changes all over again)

So, like difficulty, it is about balance. In Fable (2), I feel no fear when rushing in, as I know I can't die. I don't think this is a straight out bad thing - your meant to be a super powerful hero whose going to save the world, I would find it very difficult to believe that some small time criminal can take me down. Indeed, any death breaks immersion because, in real life, you can't die then try again.

For me, the answer is that the player should constantly fear death (depending on the game, but as a general rule) but never actually experience it. Obviously, this is nearly impossible to implement. One (ridiculous) idea I had was, make it so the player failed early on, which reset the game, but then make it very difficult/impossible to fail ever again. The player would constantly fear death, knowing it would reset the game, but never get frustrated, and honestly believe that they were just playing well. This wouldn't work, not least because it would get out on to the internet and the whole game would break. None the less, I think the principle still stands. You have to make the player fear death; creating tension, immersion and "oh snap!" moments, without them getting frustrated by having to retry everything.

Another thing to make sure you avoid frustration is, as that article the OP linked to, avoid cheap deaths. I, as a player, won't mind dying if it is fair game. If I know that miss timing a jump will result in death which will result in reload, that's fine. If, when walking along, something appears and I just die, I don't care how scary/tense/realistic it is, if there is nothing I can do about it until I have died and know it is coming, it is just frustrating and cheap.

One of the things we must overcome is what we define as a challenge. Do we really need death in order for a game to be perceived as challenging?

The most common challenge in games today is the avoidance of death. While this works for many games, this does not mean that we cannot think beyond this.

Challenges and the difficulty of a game can become more grey instead of just a black and white, 'do-or-die' situation. Puzzles, World navigation, character modifications are all examples of challenges that don't necessarily need to involve death.

Quote:Original post by Spoonbender
But perhaps it is something other genres could still learn from. Go and watch a typical action movie. The hero regularly screws up, experience setbacks and so on, but they don't die. They might have to start over from scratch, get booted out of the police force or whatever else. They get punished, sure, but they don't die. Perhaps games should do the same thing. Rather than killing the main character every time they screw up (and then ending up in a situation with no realistic/immersive way out), just let them, well, screw up.

I think this may be a bit of an archaic impression - in much recent literature, a few movies, and many TV shows, the heroes do die. I don't know, however, whether this is truly a result of changing attitudes toward fiction, or just a crutch used by struggling writers to add drama to otherwise mediocre writing.

Quote:Original post by bakanoodle
Challenges and the difficulty of a game can become more grey instead of just a black and white, 'do-or-die' situation. Puzzles, World navigation, character modifications are all examples of challenges that don't necessarily need to involve death.

Tetris is challenging because you are trying to avoid 'death' (the playing area filling up), world navigation is challenging because you have to avoid certain situations that risk death, and character modification is challenging in that it affects your ability to avoid death.

Quote:One of the things we must overcome is what we define as a challenge. Do we really need death in order for a game to be perceived as challenging?

The most common challenge in games today is the avoidance of death. While this works for many games, this does not mean that we cannot think beyond this.

Most games quantify player progress in the form of resources - be it gold earned, stats/levels, or just time. Challenge is synonymous with Risk, and the player can only risk resources - challenge then is allowing the player to be deprived of resources, a mechanic commonly called 'death'.

We can of course call it something other than death, and disguise it however we choose, but the core Risk/Reward mechanic remains.

Quote:I think this may be a bit of an archaic impression - in much recent literature, a few movies, and many TV shows, the heroes do die.

The heroes may die, but then they stay dead.
This reminds me of many strategy RPGs where once a character dies, then there is no way to get them back.
There is definitely something to be said for permanent death as a mechanic that could be explored more as well.