In the second episode of this season Doctor Who, our heroes travel across an insanely hostile planet to retrieve the TARDIS…and it’s all a bit bland, really.
This week saw the return of perennial favorite British science-fiction series Doctor Who, with a brand new actor in the (sort-of) titular role and a new man running the show. One of those I’m excited for. The other I’m sort of dreading.
Once upon a time, in the far-flung year of 1974, Gary Gygax released the first-ever edition of Dungeons and Dragons, and in so doing singlehandedly created the tabletop roleplaying game as we know it. D&D had precursors, but they were miniatures war games, more akin to Warhammer than to what we would recognize as an RPG. In many ways, Dungeons and Dragons was sui generis, and its long shadow is still cast over the modern tabletop scene. Some games, like Pathfinder and (obviously) Fifth Edition Dungeons and Dragons, are more clearly descended from Gygax’s original design than others, like Monster of the Week, but they all spring, ultimately, from the same source. In many ways, this is Gygax’s world, and the rest of just are just living in it.
One consequence of this is that a lot of D&D concepts pop up in other games, even those not directly emulating D&D, because they’re trying to fit into the mold Gygax laid out. The concepts of character race and class pop up all over the place, and the concept of character advancement by levels is so ubiquitous that it’s only notable when it’s absent from a system. On a more basic level still, while Gygax did not invent the mechanic of resolving events with a dice roll, he introduced the world to polyhedral dice, and whenever a Game Master (another Gygaxian invention!) tells a player to roll and add a bonus, that’s a piece of Gygax’s legacy shining through.
All well and good. But not everything that’s been passed down deserves to be retained. Some concepts we cling to out of tradition, not because they still serve their intended purpose. Some mechanics we take for granted, without ever bothering to consider whether they ought to be. And since I’m sure you read the title of this post before clicking through, I won’t beat around the bush any further: Experience points, in the context of tabletop roleplay, suck. They are a bad way of managing character progression, and are only kept around because as part of the Dungeons and Dragons legacy, game designers keep putting them in unthinkingly. It’s time for experience points to die.
The Problem (For Game Masters)
Let’s get the obvious out of the way: DMs/GMs hate dealing with experience points. To players, collecting experience points at the end of a session is as simple as getting a number from your GM, adding it to your existing tally, and checking if you’ve passed the threshold for the next level. To GMs, it involves a lengthy series of calculations to ensure proper distribution, and an awful lot of anxiety-inducing guesstimation when awarding for non-combat accomplishments. It’s not especially difficult, but it can take a fair amount of time, and it’s extremely tedious and unpleasant.
Of course, doing the work of running the campaign is in the GM’s job description. Most of that work is rewarding, but some of it is tedious work that, nonetheless, needs to get done. So, if experience points were providing substantial benefit to the players, GM hardship would be no compelling reason to abandon them. However, I argue that the distribution of experience points provides only marginal benefits over having the GM simply distribute levels at what they judge to be appropriate times, which are more than outweighed by the costs. Experience points, you see, don’t just suck for the GM. They also damage the experience for players as well.
The Problem (For Players)
Suppose your group plays primarily from published adventure modules, as many do. Well, experience points have almost certainly damaged that adventure’s narrative pacing and story structure:
I had a discussion with James Jacobs about a number of questionable, from the story and GM standpoint, decisions in the Dragon’s Demand module – it was giving out “story awards” to the tune of 200 XP for climbing a DC10 mount of rubble to enter the dungeon. He justified it by saying [paraphrased] “Yes but we need people to get from first to sixth level over the course of this one module to fight our end dragon so we padded the shit out of it”.
It’s simple math, really. The module has a starting level, and various setpieces throughout that require the player characters be at a certain level to handle them. If you want to get the places from level X to level X+Y over the course of the module, you need to include sufficient opportunities for XP collection to cover that difference. And if not enough of those opportunities present themselves naturally, well…the XP has to come from somewhere, right? Padding it out may not produce the most enjoyable adventure experience, but if you want them to fight a big dragon at the end, you gotta do what you gotta do.
Now, you may say, your group doesn’t use published adventures, and the GM creates all of the scenarios themselves. Unfortunately, you’ll encounter the same kinds of issues. If the GM wants you to gain a level before fighting The Monster at the End of This Dungeon, because leveling isn’t under their direct control, the only way they can ensure it is by padding out the dungeon with meaningless encounters. Or, in the other direction, if you don’t want your players to become overleveled for an encounter you’ve designed, you may need to drop another cool one that you would otherwise have used.
These types of compromises are largely invisible to the player, since they occur in the design phase, before the player even enters the scene. And yet, wouldn’t your players enjoy the game more if every encounter had a cool narrative, thematic, or mechanical hook, and none of them were simply inserted as padding?
These problems are not insurmountable, of course. In fact, the simplest solution is to simply not care about your party’s advancement at all, and let the XP fall where it may. But it seems to me that totally abrogating your control over character advancement, a crucial part of the gameplay experience, in order to accommodate a system that offers marginal benefits and causes you busywork…is not ideal. A better solution is to simply ditch experience points altogether. Let the GM decide when the party is ready to level, or even decide by consensus among the GM and the party.
Before starting this post, I did some research on the old google machine to find some of the arguments in favor of managing player advancement with experience points (XP). These were genuinely a bit tough to find, because like the water in David Foster Wallace’s famous commencement address, the experience system is so assumed that hardly anyone feels the need to comment on its presence unless prompted to by someone else. Some of what I found is genuinely valid! Some of them…less so.
1. Players want to receive experience.
More than one GM reports that their players demand to receive XP in place of GM-fiat advancement. And this is a totally real thing! Ultimately, the GM’s job is to provide a fun time for their players as well as themselves. If your players really can’t be dissuaded from the notion that they need to see a number tick up to feel like they accomplished something, well, you may be stuck with experience points, even though they suck.
I do find it amusing, however, to note that the most vociferous defender of experience points that I could find (whose angry-man-shouting-on-the-internet schtick is so tired and lamely executed that I refuse to so much as link to his essay on the topic) simultaneously made ‘players want XP so GMs who don’t want to do it are lazy and ignorant’ the crucial hinge of his argument while simultaneously admitting that, in his own words, “players suck at knowing what’s good” and are not good judges as to the source of their enjoyment. And he’s absolutely right about that: anybody who’s ever tried to serve up entertainment for an audience, be they GM, author, or game developer, can tell you that there’s always a gap between what people think they want and what they actually want. Our human brains are really bad at determining the cause of our emotional reactions. ‘The players want it’ may be a reason why you’re forced to use XP, but that’s not the same thing as XP being good for the player experience.
Finally, this argument is actually a great reason for why game designers should leave XP tables out of their books altogether. The players can’t demand XP if there’s no XP system to be had.
2. Ticking up your experience points is viscerally pleasing for players.
Some have argued that the simple act of tallying up one’s experience points and seeing the gradual progression toward the next level is enjoyable in itself. And honestly…yeah, sure? I’m not going to try to claim that it isn’t. People enjoy seeing their numbers go up, and enjoy the building anticipation as they approach a new leap in power. Many, many, many video games take advantage of this psychological trick to hook players and keep them playing. MMORPGs and gachapon-based mobile games, in particular, would be dead in the water if not for this. Heck, remember Progress Quest? Just watching a progress bar fill up is satisfying, even without any player input at all!
So, this argument is absolutely valid. But given that these XP-related dopamine hits only come in one or twice a session, maximum, and lack the accentuating animations and sounds that make XP gain so appealing in video games, I question whether this can outweigh the costs of using an XP system.
3. Players need an advancement system that’s independent of GM control, so that they feel like their accomplishments are their own.
This argument has an element of truth to it, but I don’t find it very compelling. It’s definitely possible for players to feel like their ownership of their accomplishments is diminished if they seems to come by GM fiat. To the extent that leveling, in itself, constitutes an accomplishment, you want players to feel like they earned it.
The problem with this argument is that XP distribution is already under the GM’s control. Unless you award XP solely for combat and only by consulting the provided tables (an approach to advancement that not even XP’s most ardent defender would advise), character advancement is under the GM’s control, and can be arbitrarily manipulated. The GM can award XP generously to accelerate character progression, or withhold XP to slow it down. And even in the realm of combat XP, the number and difficulty of encounters is under the GM’s control. The GM’s control over player progression is more indirect and byzantine under XP, but make no mistake: if they want you to get up to level ten so that you’ll be an appropriate level to fight the dragon they’ve put on the deepest level of this dungeon, they’ll get you there, by hook or by crook.
Now, it’s true that in the context of a game, illusions of control can be valuable. Ultimately, the entire game rests on an illusion that the players are independent agents acting out their own will on the game world, while in reality they’re going through a prepared experience that’s more akin to a cross between an escape room and a ghost train ride. But is this particular illusion of control really so valuable that it outweighs the downsides of using XP? Is anybody really fooled by it? I’m skeptical.
This argument feels like a relic of the old days when adversarial GMing was the norm. If the GM is the player’s opponent, then yeah of course the players should want their character’s advancement to be as independent of the GM’s judgment as possible. But if you imagine the GM as collaborator with and facilitator for the player, as the vast majority of modern RPGs do, it simply doesn’t make sense.
4. GMs need XP in order to motivate and guide player behavior.
The thinking behind this one is, if you want to see more of a certain behavior, you can incentivize it with XP rewards. Want to see players engage with intrigue and roleplay? Give out heaps of XP for it. Want to see them use stealth and guile to avoid encounters? Make their numbers go up!
On the surface, this argument seems to have a lot going for it, but I have three problems with it. First, I don’t think it works. Oh, to be sure, if you dole out XP rewards for roleplaying or whatnot, and are clear as to why the bonus XP is being handed out, you may see players modify their behavior in the short term. But I’d be very surprised if this led to long-term changes in playstyle. You may entice them outside of the comforting boundaries of their usual play, but unless they decide they really like it out there, they’ll retreat back to form the moment the reward is removed.
The second is that even if you can change player behaviors, I’m not at all sure that you should. It seems to me to be better to try to meet your players where they are than to try to drag them into the type of play you prefer.
And finally, any behavior reinforcement you can provide with XP rewards is going to be competing with the behavior reinforcements inherent to XP systems, which tilt overwhelmingly towards kick-in-the-door violence-driven play. Game rules are good at modeling physical systems with discrete outcomes, but have more trouble modeling more abstract behavior with more conditional outcomes. In other words, it’s easy to make rules that govern how characters resolve their problems through violence, but it’s a good deal harder to write rules governing how players solve their problems by diplomacy, or trickery, or even stealth. Those sorts of solutions are too dependent on the world and situation the GM’s created for the game rules to handle them in anything but the most general terms. There’s a reason why the typical Player’s Handbook devotes many, many more pages to combat rules than to anything involving roleplay. It’s just easier to systematize.
However, for this very reason, violence represents a consistent well of experience points. Monster difficulty relative to party strength can be – and is, in every system with an XP system that I’ve seen – broken down into a table, from which the GM can mathematically determine the appropriate award. Solve your problems with trickery and guile, and you might get an XP reward. But if you solve your problems through violence, you will get one. The result is that any attempts to use XP to modify player behavior will be competing with XP’s overwhelming natural pull on player behavior, which drives players towards the murderhobo lifestyle.
5. GMs need XP to motivate players, period.
Your players took time out of their week to show up at your house to play a game. Presumably, they actually want to play the game. If you’re finding yourself having to dangle XP rewards in front of them like carrots before horses to get them to engage, perhaps you should do some self-reflection, because clearly something you’re doing isn’t working and the XP is serving as a shoddy patch over it.
6. XP curves are part of the game design; some levels take more experience than others, because those levels correspond to when players will get new and exciting powers, and by making them last longer it gives players chances to adjust to these new capabilities.
Looking at how D&D’s experience curves are set out, it is absolutely plausible that this is the design intent. But…who cares? Do you really think that a bunch of game designers huddled in an office discussing the advancement curve in the abstract are better-positioned to judge how much time your party needs at each level than you, their Game Master, is?
7. GMs like to use loss of XP to punish players who miss sessions.
No! Bad GM! Bad! You wouldn’t tolerate your players resolving out-of-game issues in the game world, would you? So why would you bring their attendance record into the game? Furthermore, players have real lives and sometimes their real lives make it difficult to attend sessions. You shouldn’t punish them for that.
Besides, this just makes your job as GM harder; designing encounters for split-level parties is a lot harder than designing for parties that are around the same level. Just…don’t do this.
Experience points are an archaic holdover from Gygax’s days that have long since worn out their welcome. They either rob GMs of control over player character progression, or their management requires that the GM make sacrifices to the overall player experience. There’s almost no reason to include them except tradition, and plenty of compelling reasons to not include them.
This obviously does not apply to games which utilize XP in a unique or different manner. For example, many Powered by the Apocalypse systems, such as Monster of the Week, award experience points not in response to player successes, but in response to failures. Blow a roll hard enough, and you get an experience point as a consolation prize. That’s cool and performing a very different function from D&D experience.
But classical experience points simply aren’t a useful construct anymore. Leave it in the past where it belongs.
Since the launch of Kiwi Blitz in 2009, Mary Cagle (alias CubeWatermelon, which is an adorable moniker) has been hitting the internet with comic pages. She followed up Kiwi Blitz, a still-running comic about teenagers fighting crime with a giant avian robot, with Let’s Speak English, an autobiographical gag comic about her time teaching English in Japan, and most recently Sleepless Domain, a unique and delightful comic about Magical Girls who protect their city from monsters in the wee hours of the night. Her comics are notable for their gorgeous colors (LSE, which is uncolored, excepted), distinctive characters, and round cartoon style. Although none of these have exploded in popularity like some of the classic webcomics of old (although, really, what has? Has any webcomic really blown up since Homestuck took off like a rocket?), I discovered all three within about a year of each other, and I’ve enjoyed them greatly, which inspired me to do one big post reviewing all three.
I struggled to decide what order to discuss them in, because the order I read them in is completely different from the order of publication, and each one has colored my view of the one that I read next. In the end, I decided to review them in the order I found them in: Let’s Speak English, then Sleepless Domain, and then finally Kiwi Blitz.
There’s snow on the ground, the sound of bells in the air, a turkey in the oven. Trees are inside of houses, instead of outside where they belong. Yes, it’s that time of year again: time for the annual controversy over a seasonal tune from 1944. Yep, it’s Baby It’s Cold Outside thinkpiece season once again. Is the song a romantic call-and-response ballad? Or is it a harrowing tale of date rape? Everybody vote on their phones!
Look, here’s the truth: I hate Baby It’s Cold Outside. But I don’t hate it for being about date rape (although I definitely do fall in the ‘this sounds pretty rapey’ camp). I hate it for the same reason I hate most Alanis Morrisette songs: for being tuneless and meandering. It baffles me that a song this terrible has become a widespread part of the seasonal playlist. As such, I’m not going to waste my time engaging with it by breaking down the exact terms of the debate around it, especially when so many other people have already done the legwork for me; if you don’t already know why people feel the way they do about it, read these annotated lyrics on Vox which break down fairly well how the two sides tend to read its controversial lyrics.
But I do feel compelled to engage in one area, because it touches on a broader point. Those who feel compelled to defend the song always fall back on one thing: historical context.
See, this woman is staying late, unchaperoned, at a dude’s house. In the 1940’s, that’s the kind of thing Good Girls aren’t supposed to do — and she wants people to think she’s a good girl.
And even more specifically:
Historical context matters a lot here. “What’s in this drink?” used to be a stock joke to which the punchline was basically, “Nothing, not even much alcohol.”
And honestly, it’s kind of impossible to defend the song’s lyrics while also paying attention to them without falling back on historical context because…I mean, it’s a song about a man pressuring a woman into sex. Without attaching historical context to it, there’s not a lot of wiggle room out from under that. And the historical context argument is a fairly strong one…or it would be, if I cared about the historical context. In this case, I really don’t.
That might sound like heresy coming from someone with a graduate degree in literature. Surely we always care about historical context, right? Well, if we were treating the song like a piece of history to be closely examined, of course would. But if that’s all Baby It’s Cold Outside was, we wouldn’t have annual bumper crops of outrage over it. Academics would no doubt continue to argue over it, as is our wont, but the debate wouldn’t make the editorial page of every major newspaper (as it does at least once every year without fail) because there would be no mainstream audience for it. Nobody would care.
Here in the real world, though, people do care. A lot. And here’s why: because Baby It’s Cold Outside‘s permanent place in the holiday playlist makes it perpetually current. Every year, it is piped into radio stations and shopping malls as-is. Every year, famous singers like Michael Bublé record and publish new versions of it, generally without changing a syllable of the lyrics. When people complain that Baby It’s Cold Outside‘s lyrics, they aren’t complaining about Baby It’s Cold Outside, the song from the mid-1940s. They’re complaining about Baby It’s Cold Outside, the ongoing cultural phenomenon.
In the 1940s, maybe the song was, as people have suggested, actually a sexually liberating piece for women. But the song hasn’t just sat in the archive since that time, it’s been continually revisited. Every year in December we return to the song and mindlessly reproduce it once again, renewing its pop-culture relevance for another year. The result is that the song has been unmoored from its place in history. If you took a random sample of 100 people who know the song well enough to sing along with it, I would be amazed if even ten of them could tell you it was written by Frank Loesser. Or that it was written in 1944. Hell, I’d be astonished if ten people in that sample could even correctly identify the decade it comes from! The historical context behind the lyrics doesn’t matter because what the song meant in 1944 isn’t really relevant to what it means now. Historical context is only a defense if the piece is historical. For most of the work academics of English and other cultural critics do, that’s just assumed, but it doesn’t apply to cases like these.
The song’s lyrics may have remained the same over the past 72 years, but the world around it hasn’t. When Frank Loesser put pen to page and wrote Baby It’s Cold Outside his lyrics may not have signified rape to his listeners, but for a lot of people they sure do now. And historical context only explains why Loesser created it as he did; not why we continue to recreate it every holiday season.
I’m not going to beat around the bush: I love the new Hitman game. It is an absolutely fantastic return to form for the series after the deeply flawed Absolution. It combined the things Absolution did right with an infusion of the series’ core gameplay flow, and some of the best level design in the series thus far. If you’re a fan of the series, or are looking for a jumping-on point, you should definitely buy it.
Important Note: the contents of this post were written in 2014 for a series of tumblr posts analyzing Hitman: Absolution and why it failed so hard. I intend to refer to it heavily in my upcoming review of 2016’s Hitman: Season One, and am not particularly happy with how tumblr handles long text posts, so I’m republishing it here and reformatting it into a single post.
The latest title in IO Interactive’s long-running and much-acclaimed Hitman series, Hitman: Absolution, was fairly controversial on release. Although it reviewed about as well as previous entries into the series (it brought in high-seventies to low-eighties on Metacritic, depending on the platform, whereas Hitman: Blood Money rated low-eighties; Hitman 2: Silent Assassin came in in the high-eighties range but was also released all the way back in 2002, so the numbers may not be perfect comparable), many devotees of the series were profoundly disappointed, even angry, about changes made to the series’ formula, to the point that IO Interactive started the development of the next Hitman title with an open letter promising a return to form. But in the meantime, it’s worth looking back at Absolution, a few years after its release, and asking: was it really as bad as all that? Was it really as broken as its detractors claimed it to be?
Spoiler alert: Yeah, it kind of was. What’s more interesting is why. Closer examination reveals that although some of the game’s problems were unique to it, many others were not. Rather, these flaws were minimized by the level design in previous games, whereas in Absolution the levels emphasized these faults and made them stand out. In this post, I will be looking at the game in three areas (Narrative, Game Systems, and Level Design) to try and clearly express what sets Absolution apart from its predecessors and why it comes up short in the process. Click on the read more for an introduction to my perspective and the context in which I will be writing.
So, first things first: I’ve put a bunch of thought into what I’m going to do with this series, in light of the revelation that there are sixty episodes in the first season of this show. I really don’t feel like dedicating upwards to a year to doing Power Rangers recaps just to cover the first season. This has been fun, but I don’t care about Power Rangers that much, and it’s already starting to feel a bit samey.
So what I’m going to do is that this will be the end of me covering every episode in the series. That’s a good ten-episode retrospective, that’s not bad at all. I am, however, going to keep watching it, and I’ll come back and do recaps for episodes which strike me as particularly interesting/bad/important.
But first, we have to get through two more episodes. And oh boy. The first one is…it’s definitely a thing.
Everyone who spends any amount of money on Steam is liable to wind up with a bunch of games they never play. I’m certainly no exception to that. And I’ve decided to turn it into a feature! Using the Wheelhaus, I’ve rolled up five games in my Steam library which I’ve never so much as touched, and given each of them half an hour of my time. I’ll play exactly half an hour of each, and write up my thoughts. The only condition on which I’ll stop early is if for whatever reason, I just can’t get the damn thing to work and 5-10 minutes of troubleshooting doesn’t solve it, in which case I’ll skip it and roll a new one.
Although I normally don’t like scored reviews, I am going to give each of these games a score on a scale from 0-5. This score reflects one thing and one thing only: how likely I am to play the game again. 0 means the game didn’t work at all, 1 means it’s shit and I’ll never touch it again, 2 means I probably won’t play it again, 3 means I might, but don’t feel strongly about it, 4 means I likely will come back to it, and 5 means it’s awesome and I plan to complete it.
We interrupt your regularly scheduled Power Rangers to bring you something truly special. My friend forced me to watch this, and now I feel obligated to share it with you as well, so that you too can comprehend my suffering. For your consideration, I present the dumbest thing I’ve watched this year: the first episode of Scorpion.
Right, that one. Although actually, that first one feels thematically appropriate.