Choose your own adventurer

A long time ago (for verily I am a long way behind on my podcasts), Happy Jack’s were discussing the idea of creating pregenerated characters for one-offs but providing a list of disadvantages to choose from for each character. You get a pre-genned character but you can give it a bit of customisation. This got me thinking – why even stop there? You can give each character options for powers, skills, whatever. You could even give them options for backgrounds. Choose between a rival who is trying to kill you, a secret you can never speak of, or a long-lost sibling believed dead. The GM could then hand you an index card with more detail about your chosen option. It would mean the GM couldn’t rely on any individual background detail coming up, but it gives you a bit more ownership over your character. And the unused backgrounds could easily be saved for the next one-off, so you aren’t wasting too much effort.

One-offs can very easily be just railroaded experiences, you’re handed a character and away you go. I’ve got nothing against that – but this seems to be a really simple way to replicate some of the fun of character gen without sucking up so much time that you no longer have time to play the game.

Since drafting this article, I gave the idea a try as part of a one-off Dogs In the Vineyard game I ran for a con. Dogs traditionally lets you gen your own characters, but given that I didn’t have a lot of time, I decided to just create the characters in advance. But I didn’t want people to be stuck with whatever I gave them so each character had two alternate sets of traits, which I chose to illustrate possible backgrounds for those characters. (For example one of the characters could either be the guy who grew up in the big bad city and pulled himself up by his bootstraps, or the guy whose parents expected too much of him and he rebelled and went off to do something different from what they wanted.)

It worked pretty well, and I’d definitely do it again. It hardly added any time to my prep, and equally it added almost no time to the game compared to just handing out fixed characters.

Johari’s window

Ok, apologies in advance to management experts, because I am about to abuse a well-loved management metaphor until it is hardly recognisable anymore.

Johari’s window is a neat metaphor for learning and feedback. Picture a window divided into four quadrants. The top-left quadrant is things that I know about me, that you also know – public knowledge about me. The bottom left is stuff  I know about myself that you don’t know – my secrets, things I could reveal to you in future. The top right quadrant covers information about me that you know but that I am unaware of – this is important for management theory because it’s the space in which feedback can happen. The bottom right isn’t seen as especially important for management theory and it isn’t important for this post either. It’s the domain of things about me that nobody knows. Maybe there some great insight that can be gleaned there, but if there is, I (rather appropriately) don’t know what it is.

Image by Brent O'Connor

Incidentally, I have no idea who Johari is either. Whatever. [Edit: Googling around, because I just *had* to know, I see it’s actually called “A Johari Window”, so probably Johari is some kind of acronym and not a person at all. I shall persist in imagining I never discovered this.]

So, what does all this have to do with gaming? The answer is that you can use it for character generation. When you create your character, draw a window and write stuff in each quandrant.

The  bottom-left and top-right corners are for unresolved questions about your character. Who was that masked man? Who killed your father? What is the meaning of your birthmark? Why can’t you remember anything from the night of the 21st, and what happened on that night? Are you going to save humanity, or destroy it? But which quadrant you put each question in tells you whether this is a Dark Secret type of question – one you’re handing to the GM to answer, which might have an answer that you don’t like (top right quadrant), or one you’re going to answer yourself, at a dramatically appropriate time (bottom left quadrant). I suggest that by using Johari’s window, we can signal to the GM what questions are for her to answer, and which questions we want to keep for ourselves. Maybe you could even put some questions in the bottom right – these would be open to anyone to try and answer.

The top-left corner of the window has a use, too. Put things in there that are known at the start of the game. (Known to you as players, that is – maybe not to your characters.) By putting stuff in there you’re saying to the GM “this stuff is off limits”. If I say that my character is the son of a noble jedi knight, and put that in the top left corner, then the GM should not reveal partway in that the knight in question is actually Darth Vader. That would have been a cool plotline, but by putting my heritage in the top left I’m telling the GM to stay away from it. Break the top-left window pane at your peril.

The Trouble with Rose (a walkthrough)

The Trouble with Rose is a GMless, prepless, indie roleplaying game by Todd Zircher. It is in the style of a parlour game and falls in a similar category as Fiasco and Durance as games which divide the control of the narratives between all the players.

I first found it via the Story Games Forum and found the idea and Shakesperian flavour very hard to resist.  As I said, it is a similar style game to Fiasco but without the explicit car crash atmosphere, and so is better suited to my tastes.

The premise is short and sweet.  There is a person called Rose, they are in trouble.  You are playing their friends and family and your job is to build up a story about Rose; why s/he/it is in trouble and what happens next.   The simplicity of the scenario means it is easily adaptable to different genres and styles (there are a large number of playsets supporting the basic system). Rose could be a Fairy Princess, an AI deep in the Net, a schoolgirl, a pirate ship or as Todd suggests, Plutonium Rose, a rock star on the run from his groupies and the Mob.


The system is fairly simple, once a scenario has been agreed the players choose a character each, writing down six character attributes, 2 of which are in some way negative.  Some of our attributes were “own’s most of MadeUpShire” and the servant girl’s “total belief in the class system” but you might want to go for something simpler like “crack shot” or “very agile”. You then randomly choose 5 dominoes.  Each domino has 2 sides with 2 numbers on it (blank – 6), you take it in turns to direct a scene with your character in and choose a domino to represent the character attributes you will be displaying in the scene.  Blanks are wildcards and automatic failures, a double blank is played in the last round and always means that character will be removed completely from the action e.g. death.   You go round the table directing scenes 5 times. Lastly everyone draws a playing card which represents your character’s hidden agenda.

Things that worked well

The dominoes provided a good amount of story scaffolding and we made good use of a reflection period after each directed scene to tie up loose ends, discuss where the story was going and evaluate our progress.  Because of this there weren’t too many awkward moments where people go dry and the flow of the narrative fails.


Things that worked less well

We all felt a little pressured to bring in large amounts of other characters and NPCs into each scene.  This was to ensure we were giving each other enough to do.  However this meant we occasionally tied the plot in knots and strained the story. In future I would make more use of cut scenes, short flashbacks and internal monologues to flesh out characters and individual relationships, rather than making sure each person is talking in each scene.

Things we did differently

In the original game there is a means to judge each other’s role-playing prowess and award points on how well you brought your character attributes into the scene.  The person with the most points got to narrate the Epilogue. We agreed at the start that we didn’t feel this added anything to the game and that there were better ways to encourage and reward the same behaviour.  We ditched this aspect and I felt that was the right decision.

Secondly, whilst the game was GMless I feel (in all these types of game) that someone must take mental responsibility for managing the game and making sure things happen.  I made sure we had dominoes and copies of the system.  I guided everyone through character generation and actively facilitated the session, providing suggesting and prompts and encouraging others to do the same.  I’ll write more on managing GMless games later though – that is a whole topic on its own.


You may be wondering who our Rose was…she was the Scarlet Primrose, rakish hero to the French Aristocracy having rescued many of them from the Guillotine in the years after the French Revolution.  Half our characters were her family who believed her to be a ditzy dilletante, the other half were from her network of undercover contacts – much amusement and drama ensued when her two worlds collided.

I really enjoyed this game, it was great fun and we created a story which was engaging and interesting.  I still love the idea of entirely prepless games and GMless games and I think the Trouble with Rose is more the style of GMless game I want to play.  Best of all it has inspired me to write my own version of a GMless game.  So a big thank you and thumbs up to Todd Z.

Oh, I didn’t mention the best bit…it is free…go here to get your copy.