Categories
PbtA Story games Tabletop RPGs

The Star Wars World RPG rocks

My group played our second session of Star Wars World this past weekend, and this unofficial Apocalypse World hack by Andrew Medeiros is now my favorite Star Wars RPG.[1]

One of the things I look for in a PbtA game is interesting playbooks, and SWW has those in spades. When I was choosing one, I “narrowed down” the field to a half-dozen, all of which were equally appealing. Every single one feels like Star Wars, and you’ll immediately know which iconic characters they reference.

That feel carries through to the reskinned moves, the Force mechanics, and then straight on into actual play. With no prep needed (or desired), a Star Wars story unfolds during play, full of pulpy action, careening from frying pan to fire to frying pan again.

My two benchmarks for licensed property RPGs are:

  1. Does it feel like [Star Wars]?
  2. Is it also the kind of game I enjoy?

I’ve played plenty of licensed property games that hit #1 but miss #2, and I don’t play them anymore. Star Wars World hits both targets.[2]

To play, you’ll need a copy of Apocalypse World — SWW consists only of the basic moves, playbooks, XP triggers, and a countdown clock sheet. It assumes you already know how to play AW, and have a good understanding of how PbtA games generally run. It borrows from Dungeon World (paid link) as well, and passing familiarity with DW might be helpful.

I’d love to see Andrew strip out the Star Wars IP and artwork, apply a light gloss (“When you call on the Energy . . .”), fold in the full rules, add MC advice and examples of play and all that good stuff, and publish SWW as a complete game.

There’s a Google+ Community for the game if you have questions about it. For the moment, at least, the game itself lives on Google Drive.

Star Wars World is a slick, competent hack that works beautifully in play. I highly recommend it.

[1] I’ve played lots of WEG Star Wars and Fantasy Flight Star Wars, and tried out Saga Star Wars. I’ve never played d20 System Star Wars (Saga is pretty close, though) or Star Worlds (which is another unofficial AW hack).

[2] Stay on target!

Categories
Old school Tabletop RPGs

One choice, two consequences

Over on Monsters and Manuals, David McGrogan (author of the excellent Yoon-Suin, one of the starred recommendations on my big list of RPG stuff on Lulu) wrote a neat post about a rule of thumb for sandbox games: Two Problems for Every Solution.

David shares an example from his campaign that explains it well:

For example, in one of the games I am running, the PCs solved the disappearance of a group of villagers – but as a result of this they now have a vengeful demigoddess to deal with and a magic potion to track down, not to mention having to act as a go-between for two power centres and becoming entangled in an apparently unrelated issue to do with the enchantment of a young noblewoman.

Emergent play with a high degree of player agency is my jam, and I love this rule of thumb. It reminds me of last Sunday’s Star Wars World session, which makes sense because, as David points out, Star Wars is full of solutions that only beget new problems.

One bad roll popped us out of hyperspace in the wrong place, and we crashed our ship. We survived, and learned of a settlement not far away . . . full of dangerous poachers, and about to be attacked by angry natives. Problem > solution > problem, problem, and so forth. It’s a good fit.

For where I’m at in terms of sandbox experience, though, I’d like to offer up a related, but not identical rule of thumb: one problem, two consequences.

Making meaningful choices which have meaningful consequences is a hallmark of sandbox play (and other sorts of game with no predetermined plot), and “problem” is just another way of saying “meaningful consequence.” Reminding myself that choices ripple, and those ripples don’t lead to a single new choice, or consequence, or problem, should help my sandbox stay vital and alive.

When I’m stumped for how the world might react in my DCC RPG hexcrawl campaign, I’m going to keep both of these rules of thumb in mind.