Origins 2015 Debrief

And so my giant Origins 2015 debrief. For whatever reason it’s been tough to find the time to just sit down and type all this up, so it’s almost 2 weeks late. Needless to say, I had a pretty amazing time. Much like last year I spent all my time around Games on Demand, except this year I was able to run a couple games, which was pretty great.

I got in Wednesday afternoon and took some time to get my badge and get settled in. Mostly just killed time in preparation for ALL THE GAMING I WAS ABOUT TO DO. Continue reading


The Quiet Year

So, as I said in my last post I recently got the chance to play The Quiet Year. I really wasn’t quite sure what to expect going in, but I really had a good time with it.

When The Quiet Year originally launched on indiegogo I was pretty firmly on the fence, leaning towards not interested. However, I did really love the intro movie. Seriously, go watch it if you haven’t. It’s pretty fantastic.

Anyhow, I kept seeing fairly regular updates thanks to G+, Facebook, & Twitter. Eventually I decided to go for it. I like supporting indie developers, and I really like the only other game of Joe McDaldno’s I’m familiar with: Monsterhearts. Plus, the more I thought about it the more my curiosity got the better of me. I really wanted to see how the premise of the game would work and play out.

So, I put my money in and a few weeks ago Joe sent out the pdf of the game. I read over it and was very intrigued to see how it would play out. I’ve enjoyed other GMless games (Fiasco & Durance) and lately I’ve found myself drawn to games with ritualistic components, which this game definitely has. Continue reading


Sub-title: On How Playing A Game Wrong Will Make It Not Work as Well

First off, this is definitely not a rant or anything. I really like the game and I actually enjoyed playing it. I’ll talk a bit about the game and talk about what went wrong with my playthrough and why.

So, Durance. I’ve been excited about this game for a while. I backed it on Kickstarter and got the book in the mail a couple weeks ago. Read through it near-immediately and was ready to try it out. Luckily, I had that chance last weekend.

The short version of the premise: worlds are over-populated and there’s too many prisoners, so they’re sent off with some Authority to colonize planets. The colonization of Australia is a very direct inspiration. I like to call it Australia in space.

It’s GM-less and everybody gets to play two characters. A member of the Authority and a Convict. There’s a delicate balance of power, called the Ladder. Various roles hold different positions, with the Authority being headed by the Governor  and the Convicts by the Dimber Damber (say that over and over, it’s fun). Everyone gets a character on each side. At different power levels, so no one gets to be the Governor AND the Dimber Damber.

Every planet & colony that prisoners are going to have been surveyed and each have 6 elements that basically show them to be great prospects. Of course, those are wrong. In fact, half of each are wrong. Players take turns at the table determining which parts of the survey are wrong and which are right. They may include things like a good climate, alien life, and access to water. The colony survey might have to do with availability of space (and how cramped people have to live) or how evenly justice is applied. Those aspects all help color the colony and the players can flesh it out a bit.

The last piece is Drive. Every colony is driven by two things. One is servility, one is savagery, and the third is chosen from a list of 6 (by taking turns and eliminating). The last one might be “safety” or “control”. These drives are how things get resolved on the colony.

Lastly, every character gets an oath, this is something they’ve sworn not to do. There’s a nice list in the book to choose from, but you could come up with your own. The basic form is something like “Even though everyone is seeking <unique drive, e.g. SAFETY>, I will never do <something> to get it.” So the oath is always connected to the chosen drive of the colony. Then it becomes the players’ responsibility to put characters in positions where their oath is threatened and they might have reason to break it.

Eventually characters will start breaking oaths, things on the colony will change, and the story will head towards a conclusion.

And, since it’ll be natural for a lot of people to draw a comparison with Fiasco, it’s worth pointing out the major difference. Scenes are not limited. They’re not going to run out, so you don’t have to worry about using them up. A scene can be as light or as heavy as it needs to be.

Scenes are determined in a two-part process. One person will be the Guide. The Guide is meant to be an impartial observer and should not participate in the scene when at all possible. The Guide will look at the notable characters (PC’s), their oaths, and the unique drive. Then they’ll craft a question they want to see answered. Then it’s up to everyone else to set the scene and choose the players to be in that scene and then play it out. If there comes a point where the answer to the question becomes uncertain the guide should roll on the 3 available drives and based on that choose what drive will bring out the answer. Maybe someone bows down (servility) or in a fit of rage murders someone (savagery). Again, the Guide shouldn’t be involved directly, so when they determine the drive at play, it’s up to the players to interpret what that means in the scene.

If someone breaks an oath in the scene, there’s a few special actions that happen, and that character is considered no longer to be notable. They should fade into the background of the story and no more questions should directly involve them. Once a certain number of characters have died or broken an oath (about half), it signals the story is coming to a close and everyone should work towards that in the upcoming scenes. The book suggests about one more round of questions to wrap things up.

What Went Wrong

I’ll say it again like I did up top so it’s clear. I actually had a good time with the game.

But, we definitely struggled with it. Part of that was that none of us had played and I’d only read through the book once.

But, really, what went wrong the most? And this should really come as no surprise, we just flat did things wrong as far as the rules were concerned.

The book suggests (and I think it should probably more than just a suggestion) that the Guide be aggressive when asking questions. Determine facts (don’t contradict anything already established). An example would simply be killing someone. It doesn’t happen in a scene, it just happens. But the question should be aggressive and provocative.

I think we were all too much in a Fiasco mind-set and were more focused on getting the scene set instead of just asking a powerful question and seeing where that went.

Also, we failed to really bring in most of the planetary/colony descriptions. They just all kind of fell to the wayside for some reason. Maybe we didn’t talk about those details enough in the beginning (probably).

We did kind of poorly with our Oaths. We forgot to really tie them directly with our unique drive, which left them feeling much less focused. We still broke some oaths, but without considering the drive when paired with an oath we all (there were 3 players) had a really hard time crafting situations for people to break their oath. Numerous times we’d say “I’m just having a really hard time figuring out what would cause them to break their oath.” I’m certain that’s because we weren’t considering the drive along with it.

We also struggled, as Guides, to find those moments of uncertainty. We all found them to be really elusive for some reason. And, now that I’ve read through the rules again, it’s because we missed a key connection. The uncertainty should focus on the outcome of the question. I can absolutely see how that would make those moments a lot clearer in play.

So, it was a great learning experience. Many times you learn more by failing than by a rousing success. And failure is a strong word. I think we all three enjoyed the game, even though we all struggled throughout. After I decompressed a bit (con weekends are always draining as much fun as they are) and re-read the book  a lot of things became much clearer.

I like when a game is designed well enough that when some things don’t work well, I’m still able to have fun in the moment and then later examine what happened and find really obvious answers in the book.

I feel like I’m now in a great position to play the game and have it go 1,000 times better now and I absolutely look forward to trying it.

Dread: First Reading

First things first: as of now I haven’t actually played Dread. I played a really interesting hack of it a while back, but as far as Dread out-of-the-box I haven’t played it yet. I just recently read the rulebook and I thought it would be an interesting exercise to note down some thoughts I have just from reading the book and then, hopefully, I’ll get a chance to run or play it at some point and I can compare that experience with what I post here. Continue reading

Zombie Cinema Actual Play

Only 3 of us in my normal gaming group could make the game this week. Normally I run FreeMarket, but with just 2 PCs, I didn’t think it would be all that compelling. Plus, I kind of wanted to play Zombie Cinema again.

I’ve already talked a bit about what Zombie Cinema does and how it works. I’ve since learned that a couple of minor things are wrong in that post, but I got the main points right and it’s not worth editing or writing a new post to clarify. Can’t get all the rules right the first time, right?

The first play through at GenCon was definitely a bit rocky. There were 4 of us. Two of the other players had played previously but both agreed they struggled with the rules a bit. So we read through the rules at the table (the booklet is pretty small) and pretty much just started playing. We struggled at a few points, but once we started seeing what was happening in game and comparing that with the rules things started clicking.

So, going into the game last night I was a lot more confident. Also, there’s some good resources on the Zombie Cinema website to help clarify the rules and offer some play-advice. Now armed with a single session under my belt and the help from the site I was ready to give it another shot!

The following is last night’s session condensed into story form. No mention of mechanics whatsoever.

Continue reading

GenCon 2011 Debrief, Part 5 (Games Played, cont.)

Finishing off the games I played this year are a couple games in a playtest phase: The Dungeon Job, and Spark.

The Dungeon Job

The Dungeon Job is a hack of Leverage being done by the Chatty DM.

Prior to sitting down I’d never heard of Leverage. I had absolutely no expectations. And sometimes that creates some of the best gaming! Just go in willing to have a good time.

The underlying system both games used are Cortex. Bear with me as I do most of this from memory from a game that I played 6 days ago. Luckily my brain tends to absorb game rules, so I should have the big picture stuff pretty accurate. Continue reading

GenCon 2011 Debrief, Part 4 (Games Played, cont.)

There were a few games I was specifically looking forward to playing this year at GenCon: Lady Blackbird (I managed to play in a hack of it, at least), Inspectres, & Apocalypse World.

Operation Blackbird

I’d heard good things about Lady Blackbird, so I was looking forward to having the chance to play it. Unfortunately I didn’t get that chance, but I did get to play in a hack of it. So, instead of playing in more of a steampunk/Victorian-type setting, the characters were all spies in the 60’s. Note: you can get the rules for Lady Blackbird here for free.

I’d like to be able to compare the hack with the original material. Luckily the system is simple enough that I think it will be able to handle a lot of different situations pretty well.

The system’s pretty simple — seriously, take a look at the link above and check out the pdf. The rules take up half of the character sheet. The rules are simple, elegant, & interesting. Continue reading