Right?
But, um, dude. What about my story?
What do you mean your story?
When I generated my character, there were these tables, and they were all like, hey, wow, you get a random story attached to your character when you spin him up. And I was like, cool, hey, that is pretty nifty, now I can be like those dudes from Lord of the Rings and all.
Then you made me make a save-or-die saving throw and insta-killed my guy.
Dude, not cool.
Hey, don't blame me, old-school is back. This isn't D&D 4, a game that goes out of its way to make sure nobody feels slighted or marginalized at the table, that everyone's contributions are important, and those "ruin the night for one player" moments were written out of the game. Those days are over. This is the return of the real, and we are back to the old way of doing this, so toughen up and get with us old-schoolers, right?
Dude, I liked my story. Why have a story on your guy if the game is telling you to run around and kill our player characters off like some psycho in a slasher flick?
Oh yeah, I forgot this isn't AD&D, or even a retro-clone like Basic Fantasy or Labyrinth Lord. In those games, some of the true old-school classics, your guy was just a couple 3d6 rolls and some hit points, and you didn't even get a story chart to roll on. Heck, you didn't even name your guy until he got to third level and was worth caring about.
Yeah, well. Dude, I grew up playing World of Warcraft, and I am pretty used to the idea that losing my guy warrants a call to customer service. He may be the same hero who saves the world along with 5.5 million other players, but that's my story, and I am entitled to it.
Well, we have to be fair here, would you be that angry if I, as DM, insta-killed your Pathfinder character?
Well, dude, yeah. I put a lot of time into that build!
As I recall, you copied that build from someone else's forum post.
Dude, not cool. Even though someone else came up with it, I punched it into Hero Lab. Plus the paper I used to print it out, and the toner. It's a lot of work.
So let me get this straight. You don't play the old-school games because player death is easy, the characters are too simple, and the story parts are more compelling than the mechanics?
If I am going to spend my Saturday playing a game, I want something out of it, dude. I want my character to be a part of something, to matter, and for my choices to mean something. Just 3d6 in six scores doesn't mean anything to me, I want to design my guy, and have those choices matter. I want there to be some story to play through, and for that story arc to be a part of character design.
What about the concept of 'you make your own story?' You know, where what you do in the face of impossible odds is the compelling narrative, and watching dozens fall before the one true hero rises is a part of the fun?
Dude, the first guy I spin up is the one true hero.
But D&D 5 has save-or-die!
The game also has built-in stories. Where is the fun in having my character get killed before his aunt finds out he is a thief? This is story-based game.
Story-based does not mean 'player protection' from bad decisions. Even story-based games are like that. You walk a tightrope here, if you make great decisions, you may get the satisfaction of advancing your personal story. Fair trade?
Not if it is save or die. Dude, even if I played this for the combat and tabletop side I would be pretty pissed if I failed a save-or-die saving throw. All that work, all those adventures, just game over. It's a pretty rotten thing taking a character off the board with one roll. If I fail, I want it to be because of my bad decisions, not a cheap "you lose, thank you for playing" 50-50 roll.
It's the cheap thrill of Russian roulette with my player character, not cool.
Where this Started
You know, sometime long ago these games used to be about the thrill of working through a simple rules system that was deadly and absolute, and working out a way to survive and profit despite the sheer impossibility of survival. Many characters did not make it, because they were just that, playing pieces in Monopoly where you laughed if one of them fell off a cliff and you chalked it up to "how the game works." They were easy to spin up because they were so disposable, and you weren't supposed to invest yourself in them all that much.Nowadays, things have changed.
How so?
I agree that if you are playing a story based game, save-of-die sucks. I also think it sucks in a tactical game, because it robs you of your input, and it does feel like a Russian roulette mechanic for cheap tension. In a classic old-school game, I see its place though. Old school isn't about fair, and you stayed away from save-or-die monsters or situations, because you got XP directly from treasure, not the artificial challenge rating of monsters. Somewhere along the line someone introduced the concept of "if it is a good fight, players deserve XP" when that wasn't in the game.
The concept of XP for a good and balanced fight that you will most likely win comes from the admission that the game is mass-market entertainment. I feel it is a dumbing down of the concept, making the game more like a videogame, and putting in an artificial slot-machine constant-feedback reward system that keeps players coming back.
Save-or-die was in old-school games to discourage you from doing a straight-up fight with that medusa. It was better to sneak past her, find a way to deal with her other than combat. If you stole her 1,000 GP brooch, you got 1,000 XP. Any way you got it was fair game.
Nowadays, the medusa is engineered to be a fun encounter 'worth' the XP she is assigned. You get no XP for treasure, so you are forced to fight her for the XP. In a way, it is more bloodthirsty because you are putting a point value on a life (defeated however), rather than a goal or a treasure. This is a concept taken straight from videogames that reinforces the "kill for experience" sort of very basic and almost darkly sinister motivation for the game. Now, 'killing' means 'defeating in any way, knocking out, etc' in many games, but the points are 'owned' by the encounter.
There are also 'story XP' which is a system that attempts to cover story-players as well.
I do feel D&D's reward system has been messed up for a while, ever since AD&D 2nd Edition where they started the story award XP system formally, and also reset monster XP along those levels.
If the game wants to be story based, then remove XP for killing things.
If the game wants to be hack-and-slash, then remove story XP.
Reward Systems
Personally? I like story-based XP systems. I think XP for killing is a bit cold and bloodthirsty, like a genocidal bounty system. I liked the XP for GP thing of old-school play though, in a fun sort of way because it encourages creative play. The goal is to out-think the monsters and grab the loot. You are like this group of Ocean's 11 thieves looting and sneaking your way through dungeons, each person with a special ability (healing, fighting, sneaking, magic) but with only one goal - grabbing the loot the easiest way possible.If the king wants to pay your party a "story award" of 10,000 GP for rescuing the princess, then pocketing 10,000 XP is also your motivation. The XP are nice, but really everybody, we are here for one reason and one reason only, shiny gold coins.
In this context and the original game's motivation of "XP for treasure" a save-or-die mechanic makes sense. You are a playing piece out to accumulate as many GP as possible. Yes, some monsters and traps are "save or die," but the balance is to not fight them or be stupid enough to step into them. You certainly don't get XP for the artificial reward of "beating" them, so trick, avoid, and circumvent these monsters as best you know how and the tools given to you will allow.
So, save-or-die is in there, but it is something to avoid?
Exactly. It is a different design and motivation for the entire game. Balance issues clear up because there is not an artificial reward tacked onto a creature, so there is no need for a CR system to rate difficulty. An owlbear is an owlbear. Fight it if you think you can, or avoid it if the dungeon designer was smart enough to put another way around. Save-or-die was a disincentive, not a game design mechanic someone needs to balance.
The definition of "railroading" in pen-and-paper games changed too. In the old days, railroading was that a module designer forced you to solve a problem one way, or forced you into a fight you could not avoid. When RPGs went story-based, railroading was forcing you to play the story the module designer's way. In the old definition, railroading was more about giving the players choices in how they wanted to approach a situation. It was about the freedom to approach a problem and allowing for that.
It is partly D&D's problem because of its heritage. D&D by its nature is a "big tent" game that takes inspiration from many fantasy sources. This means the reasons people play the game are just as varied, and the game has to support many types of reward systems. It needs videogame XP for hack-and-slashers. It needs story XP for roleplayers. It got rid of XP for GP, which I think is a mistake.
Understanding Fairness
But yes, understanding reward and motivation are key to understanding why save-or-die mechanics work in some games and not others. It is ultimately about that feeling of unfairness, but to decide if something is unfair, you need to understand both the motivation for play and how the reward system works. Some games have simple motivations, so judging what's fair is easy. Other games are more complicated, and you layer in characters that take hours to design, or story systems on top of bounty systems, and things get more complex.Fairness is ultimately judging if a reward is worth the risks, and not feeling cheated should things not work out. In a way, fairness measures how you feel about defeats and successes, and the satisfaction of the proportionality of a reward given a risk.
No comments:
Post a Comment