Last night was the first session of a planned four-session game of the Mountain Witch. TMW's a bit passe now it seems, since everyone's played it so many times, and even I've played it a lot, though this is the first multi-session game of it I've played.
There are things about the game though, which I think are still very interesting in play, and that aren't really present in many other games. Specifically, the way that the Dark Fates create a frisson of secrecy around characters actions, how everything the characters do and say is imbued with a deeper significance because it all gives clues to the Dark Fates, is surprisingly enjoyable even after playing the game a number of times.
I think multi-session play definitely makes the game shine. The limited scenario makes it a tempting game for scenario play, but the development of characters that comes across multiple sessions is adding so much to the game.
With four sessions to play with, I let the first session build very slowly, with almost no conflicts at all. We started play with the Ronin showing up in a grimy sakeya in the village at the foot of the mountain. The terrified villagers make their offer, and the Ronin each accepts. This let the players introduce their character in interesting and often significant ways. Some of them were clearly just in it for the money, while others appeared to genuinely care for the villagers.
We left on a cliffhanger, with the hostess of a dilapidated teahouse who had taken the Ronin in for the night transforming into her Ogre husband. Suitably bizarre for Japanese myth, and certainly a surprise for the Ronin, who were taking an onsen after a hearty meal of the local specialty, live nore sore.
Tuesday, February 16, 2010
Monday, January 4, 2010
KKKKKK
That's Kazekami Kyoko Kills Kublai Khan, not Kabbalistic Kleptomaniacs Kidnap Ku Klux Klansmen, or anything else.
I'm playing it with a friend on wave, and enjoying the heck out of it all over again. Playing Kyoko instead of the Khan is making me appreciate games with different rules for different character types, and the whole structure of the game, which feels like a kind of shadow-boxing or Capoeira display, is making me thing about Mo's "Push and Pull" in a way that makes it super relevant to game design.
I keep thinking that the game shouldn't work, that there's nothing to push against, that I'll fall over, and yet it keeps working, just fine. As a rule, I dislike games that are just free creation of fiction, without tension or consequences. And yet the game has subtleties that make it work, that provide friction and consequence.
Too much out-of-play discussion would collapse the game, I think, turning it into just another creative writing exercise. But the uncertainty of expectations, the tension between your desires for the story, the other player's desires, and then the sexual nature of the content, preserves a feeling that each statement is a concrete "move" in a game where something real is at stake.
I'm playing it with a friend on wave, and enjoying the heck out of it all over again. Playing Kyoko instead of the Khan is making me appreciate games with different rules for different character types, and the whole structure of the game, which feels like a kind of shadow-boxing or Capoeira display, is making me thing about Mo's "Push and Pull" in a way that makes it super relevant to game design.
I keep thinking that the game shouldn't work, that there's nothing to push against, that I'll fall over, and yet it keeps working, just fine. As a rule, I dislike games that are just free creation of fiction, without tension or consequences. And yet the game has subtleties that make it work, that provide friction and consequence.
Too much out-of-play discussion would collapse the game, I think, turning it into just another creative writing exercise. But the uncertainty of expectations, the tension between your desires for the story, the other player's desires, and then the sexual nature of the content, preserves a feeling that each statement is a concrete "move" in a game where something real is at stake.
Sunday, September 6, 2009
For the Story's Sake
There's this pernicious misconception that's been around for a while and which has always kind of bugged me. A few threads on Story Games recently have brought that misconception out into the open, and crystallised my thoughts on the issue.
The misconception I'm talking about is the idea that Story Now play is about doing "what's best for the story". The idea goes something like this:
Now aside from the stupid idea that creative agendas are a label you can stick on people, what's dumb about this is the fact that asking "what's best for the story?" is completely, directly, and unambiguously the opposite of Story Now play. Play in which the players are focused on creating a "good story" as the point of play is directly incompatible with Story Now play.
That seems kind of counter intuitive.
But it's not! The whole deal with Story Now play is that no one, not the GM, not the players, not anyone, knows what the story you're creating is going to be about, how it will eventually resolve the premise (if it does), and whether the story will eventually have a happy ending or a sad one. All this shit is up in the air. We don't even really know much about the genre of the story we're telling (There's a whole digression here about how genres are things that are retroactively applied to creative works, rather than a formula to be emulated, unless you're doing pastiche).
In Story Now play, it's impossible to know what will make the story "good".
So no one gets to say what the story is about, until it's done, until it comes out in play. If we knew what would make the story "good" we wouldn't be exploring a premise, we'd be emulating a genre. And yeah, sometimes that means that the story is going to suck a little. There'll be times when everyone will wish that the NPC hadn't got his head shot off, or that the dice had come down some other way, but we stick with how it happened in the fiction, because that's the contract we all made with each other when we started playing. We agreed that we'd see this thing through to the end, play by the rules, and live with it.
A "good story" is a shield for players to hide behind when they don't want the responsibility of making a statement in play. My character in Dogs doesn't slap a young woman NPC because I've decided that would titillate the other players. He does it because I'm saying right now that that's how he rolls. He's a guy who will slap a woman right in the face, and you have to deal with that. I'm judging him in my own mind, thinking "Fuck me, this guy is an ass", but I'm also thinking "I can't be honest to who this character is and not have this come out in play". And when the other players' characters judge mine, and find that he's not good enough to be a Dog, I agree with them. But it's not just something I thought would be "cool" in the moment. It was me saying "Here's a guy who, given this power over other people, thinks he's got the right to slap a woman in the face". And the other players are saying "Here are some people, given the same power, who won't cross that line."
It's us, the players, having a conversation about morality and power and the right to judge, and we're doing it through the medium of the game, and it's only possible because we stand behind our portrayals of the characters, and we don't let some idea about what's "good for the story" get in the way of that.
My character in Dogs, Michael, decided to stop being a Dog in our game last Thursday. It was tough, surprising for a lot of players, and the first real sign of the wear that the job is having on the Dogs' faith. Michael struggled to overcome his weakness, but he couldn't do it, and he knew it. He asked another Dog for help, and she told him she didn't think he was good enough either. It was harsh, and awesome. And none of us ever caved to what was "best for the story". There were panicked looks about the table as we discovered what was at stake in the conflict. I think Malcolm and Steve were worried that we'd somehow gone too far, that we should pull it back somehow. But we stayed on course. We saw it through to the end. And it was good.
The misconception I'm talking about is the idea that Story Now play is about doing "what's best for the story". The idea goes something like this:
Simulationists are all about "what's realistic?" or "what fits with the genre"
and Gamists are all "what will make me win?", Narrativists are always asking
"what's best for the story?"
Now aside from the stupid idea that creative agendas are a label you can stick on people, what's dumb about this is the fact that asking "what's best for the story?" is completely, directly, and unambiguously the opposite of Story Now play. Play in which the players are focused on creating a "good story" as the point of play is directly incompatible with Story Now play.
That seems kind of counter intuitive.
But it's not! The whole deal with Story Now play is that no one, not the GM, not the players, not anyone, knows what the story you're creating is going to be about, how it will eventually resolve the premise (if it does), and whether the story will eventually have a happy ending or a sad one. All this shit is up in the air. We don't even really know much about the genre of the story we're telling (There's a whole digression here about how genres are things that are retroactively applied to creative works, rather than a formula to be emulated, unless you're doing pastiche).
In Story Now play, it's impossible to know what will make the story "good".
So no one gets to say what the story is about, until it's done, until it comes out in play. If we knew what would make the story "good" we wouldn't be exploring a premise, we'd be emulating a genre. And yeah, sometimes that means that the story is going to suck a little. There'll be times when everyone will wish that the NPC hadn't got his head shot off, or that the dice had come down some other way, but we stick with how it happened in the fiction, because that's the contract we all made with each other when we started playing. We agreed that we'd see this thing through to the end, play by the rules, and live with it.
A "good story" is a shield for players to hide behind when they don't want the responsibility of making a statement in play. My character in Dogs doesn't slap a young woman NPC because I've decided that would titillate the other players. He does it because I'm saying right now that that's how he rolls. He's a guy who will slap a woman right in the face, and you have to deal with that. I'm judging him in my own mind, thinking "Fuck me, this guy is an ass", but I'm also thinking "I can't be honest to who this character is and not have this come out in play". And when the other players' characters judge mine, and find that he's not good enough to be a Dog, I agree with them. But it's not just something I thought would be "cool" in the moment. It was me saying "Here's a guy who, given this power over other people, thinks he's got the right to slap a woman in the face". And the other players are saying "Here are some people, given the same power, who won't cross that line."
It's us, the players, having a conversation about morality and power and the right to judge, and we're doing it through the medium of the game, and it's only possible because we stand behind our portrayals of the characters, and we don't let some idea about what's "good for the story" get in the way of that.
My character in Dogs, Michael, decided to stop being a Dog in our game last Thursday. It was tough, surprising for a lot of players, and the first real sign of the wear that the job is having on the Dogs' faith. Michael struggled to overcome his weakness, but he couldn't do it, and he knew it. He asked another Dog for help, and she told him she didn't think he was good enough either. It was harsh, and awesome. And none of us ever caved to what was "best for the story". There were panicked looks about the table as we discovered what was at stake in the conflict. I think Malcolm and Steve were worried that we'd somehow gone too far, that we should pull it back somehow. But we stayed on course. We saw it through to the end. And it was good.
Thursday, August 27, 2009
Dogs Interview
I don't normally listen to podcasts, mostly because I don't have time, but I've been home sick with the Bacon Fever the last few days, so I gave a few a listen.
Since we're playing Dogs at the moment, I checked out this interview by "ninjas vs pirates" with Vincent regarding Dogs.
I was impressed with the interview. They'd clearly done their homework, because they asked a bunch of questions that had popped up in Story Games threads from the previous couple of weeks. Vincent was cogent as always (is it just my New Zealand ear, or does he sound just like Adam from Mythbusters?). I think what I found most interesting was how they asked about specific mechanics, and how that contributed to the way the game plays. That was interesting from the perspective of playing Dogs, and from the perspective of designing games.
For my own play of Dogs, the question about "what's at stake" in conflicts was the most relevant. In our last game, we'd had a conflict where it took us a long time to figure out exactly what was at stake. I think we came to the right conclusion in the end, but some of the advice in the interview would have helped.
I'm definitely going to check out part two of the interview.
Since we're playing Dogs at the moment, I checked out this interview by "ninjas vs pirates" with Vincent regarding Dogs.
I was impressed with the interview. They'd clearly done their homework, because they asked a bunch of questions that had popped up in Story Games threads from the previous couple of weeks. Vincent was cogent as always (is it just my New Zealand ear, or does he sound just like Adam from Mythbusters?). I think what I found most interesting was how they asked about specific mechanics, and how that contributed to the way the game plays. That was interesting from the perspective of playing Dogs, and from the perspective of designing games.
For my own play of Dogs, the question about "what's at stake" in conflicts was the most relevant. In our last game, we'd had a conflict where it took us a long time to figure out exactly what was at stake. I think we came to the right conclusion in the end, but some of the advice in the interview would have helped.
I'm definitely going to check out part two of the interview.
Saturday, August 22, 2009
"Roleplaying" in RPGs
I've been having a frustrating couple of weeks with Story Games. It seems like the interesting threads with good topics get ignored, while bickering and inane banter just piles up the comments. I guess I'm mostly frustrated because I feel like I've made some interesting comments which haven't had any kind of useful response. So in other words, I'm feeling whiny because I haven't been getting enough attention.
Rob Bohl started an interesting thread about encountering players for whom "roleplaying" was an undesirable impediment to the process of playing roleplaying games. The thread (and my comments in it) didn't get the attention I think it deserved, so I'm blogging about it here.
This is largely a semantic issue, which usually means it's boring and pointless, but I thought it was a good opportunity to expand on a thought that had been percolating in the back of my mind for a while.
I think that "roleplaying", in the sense that the gamer Rob is talking about means it, is best described as a set of techniques. An (incomplete) list of these techniques would look something like this:
Defining what a roleplaying game is is a notoriously difficult subject, because, I think, there's no clear consensus on which techniques are essential to defining a game as such. For example, there are a large number of techniques that are employed in "traditional" RPGs but not in some newer games, leading some people to lable those new games "not RPGs". Some of these techniques include:
So are there any techniques that are essential to something being an RPG or not? The best I can come up with is the idea of a shared imagined space.
"Shared Imagined Space" is the idea that the players all contribute to a shared understanding of what is happening in a fictional space. In short, it's players describing fictional stuff about what's happening in the game, and the other players all agreeing that yes, that is happening.
But Shared Imagined Space itself doesn't make an RPG, right? Otherwise you could describe stuff happening in your game of Monopoly, like "oh, the hat and the iron are getting married" or whatever, and make it an RPG. Some people play a lot of games like this (especially games like "Bang!" and "Lunch Money"), but I don't think that makes them RPGs.
Or maybe it does. I don't know, but it doesn't sit easy with me, mostly because I hate playing games like this.
So another way to think about it, that gets around that problem, is to define RPGs by the use of the technique of Shared Imagined Space with impact on the mechanics of the game.
In other words, you describe stuff, and what you describe has an impact on how the rules of the game work. Purely based on judgements about the fictional content of the game, you make decisions about how to impliment the rules of the game.
That's a pretty controversial definition though. It excludes some indie favourites like "Contenders", and nearly excludes "My Life With Master", and I would argue (based on my previous post) that it comes close to excluding D&D4E as well.
So it's close, but not quite right. It's floating around in there though. It's something about how the Shared Imagined Space impacts on the game, or on the decisions that the players make.
In the end though, I don't think it's a very useful thing to have a definition of what is, or is not, an RPG. I think it's more useful to look at the whole list of techniques I described above, and look at a game as having more or less "RPG qualities". That's a useful definition I think, because it frees up thinking about designing and playing games. There is no technique that is "essential" to an RPG, and there is no technique that is forbidden. Not all RPGs use the same techniques, and when you play an RPG, it is useful to be aware of the techniques it supports.
Rob Bohl started an interesting thread about encountering players for whom "roleplaying" was an undesirable impediment to the process of playing roleplaying games. The thread (and my comments in it) didn't get the attention I think it deserved, so I'm blogging about it here.
This is largely a semantic issue, which usually means it's boring and pointless, but I thought it was a good opportunity to expand on a thought that had been percolating in the back of my mind for a while.
I think that "roleplaying", in the sense that the gamer Rob is talking about means it, is best described as a set of techniques. An (incomplete) list of these techniques would look something like this:
- Saying aloud what your character says
- Thinking about and describing "what your character would do"
- Having your character interact socially with other characters in the fiction
- Describing non-essential information about what your character does
Defining what a roleplaying game is is a notoriously difficult subject, because, I think, there's no clear consensus on which techniques are essential to defining a game as such. For example, there are a large number of techniques that are employed in "traditional" RPGs but not in some newer games, leading some people to lable those new games "not RPGs". Some of these techniques include:
- Each player controlling one in-game "piece"
- Increasing in-game effectiveness
- Mechanics for simulating violence
- A "GM" or similar
So are there any techniques that are essential to something being an RPG or not? The best I can come up with is the idea of a shared imagined space.
"Shared Imagined Space" is the idea that the players all contribute to a shared understanding of what is happening in a fictional space. In short, it's players describing fictional stuff about what's happening in the game, and the other players all agreeing that yes, that is happening.
But Shared Imagined Space itself doesn't make an RPG, right? Otherwise you could describe stuff happening in your game of Monopoly, like "oh, the hat and the iron are getting married" or whatever, and make it an RPG. Some people play a lot of games like this (especially games like "Bang!" and "Lunch Money"), but I don't think that makes them RPGs.
Or maybe it does. I don't know, but it doesn't sit easy with me, mostly because I hate playing games like this.
So another way to think about it, that gets around that problem, is to define RPGs by the use of the technique of Shared Imagined Space with impact on the mechanics of the game.
In other words, you describe stuff, and what you describe has an impact on how the rules of the game work. Purely based on judgements about the fictional content of the game, you make decisions about how to impliment the rules of the game.
That's a pretty controversial definition though. It excludes some indie favourites like "Contenders", and nearly excludes "My Life With Master", and I would argue (based on my previous post) that it comes close to excluding D&D4E as well.
So it's close, but not quite right. It's floating around in there though. It's something about how the Shared Imagined Space impacts on the game, or on the decisions that the players make.
In the end though, I don't think it's a very useful thing to have a definition of what is, or is not, an RPG. I think it's more useful to look at the whole list of techniques I described above, and look at a game as having more or less "RPG qualities". That's a useful definition I think, because it frees up thinking about designing and playing games. There is no technique that is "essential" to an RPG, and there is no technique that is forbidden. Not all RPGs use the same techniques, and when you play an RPG, it is useful to be aware of the techniques it supports.
Thursday, August 13, 2009
Gaming and Hierarchy

This post on Chris's blog that links to this post about sexism and violence as "stress release" in RPGs got me thinking about hierarchy in gaming groups and how there are some issues that are kind of "third rails" in discussion of gaming. They're sure to produce sparks when you bring them up.
One of them is the issue of "wish fulfilment" in gaming, how people play these games so they can do things they can't do in day-to-day life. That's an interesting subject, but I think it's being covered in the discussion on Chris's post.
What I've been thinking about though is hierarchy in games, how RPGs sometimes act as a way for groups to reinforce the power structure of the group, how "in character" actions can be a substitute for real life actions, and how sometimes real life issues come out "in game" in ways that we don't expect. I think sometimes players use "in character" actions as a way of keeping others in line socially. I know that looking back at even some quite recent play, there were times when people's in-character actions were clearly about punishing a player for not playing "right", and for not fitting in with the group.
I think "the party" is a pretty clear metaphor for the out-of-play social group.
I think "the party" is a pretty clear metaphor for the out-of-play social group.
This is most obvious in adolescent play, where there's a lot of tension and one-up-man-ship in play, where the players are all struggling to define themselves against each other. A lot of interpersonal aggression comes out as in character bickering, fighting, and so on. I don't think it's an accident that GMs tend to be the more socially competent and respected members of their groups. I think the amount of power that traditional games give GMs over the players in the game is directly related to the ways that the people who habitually take the GM role dominate their social groups. I know this was a feature of my early play, and from listening to others, I don't think that's an unusual experience.
I want to take a moment to say that I'm not at all bagging on the concept of GMs in games, or saying that roleplaying is an inherently damaging activity for young people. I'm saying that the format of gaming which has a GM position with considerable power over a group of players naturally facilitates and reinforces the existing social structure of a lot of social groups, and that in-game actions are not exempt from the interpersonal relationships that exist in those groups.
Groups reproduce in play the power structure that exists outside of play. So groups with a strong leader type are going to gravitate towards games that facilitate that role.I talked about some of this stuff in my post grad thesis, which was about the local gaming club in my town. I didn't really have the roleplaying experience or theoretical grounding to explore the idea fully at the time, but I was very aware of the way that the GM position worked in social groups, and how in-game actions reflected out-of-game social structures. I wrote about how the breakdown in a game I observed was directly related to the power struggle between two players in the group.
Of course, none of this made me very popular in the club. Talking about this stuff was implicitly forbidden. The "It's just a game" mantra was strongly invoked to dispel any analysis of power in gaming.
I think it's pretty clear that it's not "just a game", and that social structures do influence the way people play with each other. What I'm interested in is not the really obviously dysfunctional ways that adolescent players interact with each other in play, but rather the way that all in-game actions are really interpersonal interactions.
I think as a hobby we've got this really strong cognitive divide between "in character" and "out of character" as two totally distinct things. It's an article of faith that what happens in play is totally distinct from our real-life social interactions, and I think that's a mistaken idea.
Not that that is a particularly original observation, but I think it's an important consideration to keep in mind during play, and in design. All interactions between characters are interpersonal interactions between players in the game. They are all "real life" interactions. I think that's one of the strong differences between rpgs and other mediums, and it's both a strength and a weakness of the hobby.
Subscribe to:
Posts (Atom)