Skip to main content

Fate Accelerated: Caper- Planning for Empty Seats

Planning for Session 1 of Fate Accelerated (FAE) Caper,. I am likely to have 3 players and I have 5 roles. This is a game heavily based upon the TV show Leverage, which I have seen a ton of.
As a review, the 5 roles are: Hitter, Hacker, Thief, Grifter and Mastermind.

Out of these 5 roles, I think the Mastermind is the easiest to remove. I think it makes sense to abstract away the planning of the heist and treat the Mastermind character as an NPC who contributes a Game Aspect of "Planned for this". This allows all the players to benefit from the Mastermind's role without requiring someone to play them.

Since there is still one role left over, I think that the same thing could be done with the remaining role. Hitter, Hacker, Thief and Grifter all have particular things they specialize in. The role not chosen can be represented with a Game Aspect of "Hitter", "Hacker", etc. If I had to choose a role to be represented this way, I would probably choose the Hacker. In Leverage this is often a support position so I think it would offer the least friction to remove the role from play.

So we have 2 Game Aspects that represent important parts of the team that are available to all players. These will probably be the only Game Aspects that I include and reflect the help and teamwork available to the players. Also, in the fun nature of Compels, if something sinister has to happen, these 2 roles give me a way to take shots at the team without directly confronting the players.

I think this is may be a fun way to handle missing players or necessary roles in FAE. Characters become Game Aspects. If you had a missing player for just a week, you could create an Aspect for the session that reflected the team's need to find them; something like "Terry's Missing". That could be both to the benefit and detriment of the players, just like any good Aspect.

Food for thought; something I'll try tonight!

Comments

Popular posts from this blog

Dragon's Pool

Here's a pitch for a new game setting for D&D I'm working on. First, I recommend you read Shadow of the Fox by Julie Kagawa. I'm enjoying it a lot; it's a fantasy Japan with a lot of great characters and fun over-the-top fantasy. The Dragon's Pool is an Asian-inspired setting that focuses on the mystical and magical. Long-term goals are to zoom out and see the lands of China, Korea, Mongolia and southeast Asia (Malaysia, Thailand, Indonesia). Short-term, Dragon's Pool will focus on a mythic Japan and the sea that surrounds it. Some of the homebrew topics I'm dealing with are the yokai (monster) races of Kitsune and Tanuki and a lot of mapping D&D Classes and Archetypes to Asian tropes. You can follow along for more and also check out the World Anvil page at https://www.worldanvil.com/w/dragons-pool-hans

Stories Never Told - Learn to Play

Stories Never Told is a role-playing game project in development! The quickest version is the new Google Form-based example that works like a Choose-Your-Own Adventure! https://goo.gl/forms/jVV3hC2FbiUxRrxi1 If you would like to see how the system works, please click the link below to view it in Google Docs. This is a longer example that shows all of the options. Stories Never Told - Learn to Play in Google Docs Did you take a look? Thank you! It would be great to get your feedback. If you're interested, fill out the following Google Form SNT Learn to Play Feedback Form The goal of Stories Never Told is to keep role-playing focused on the stories of the characters being played. Stories Never Told Role-Playing Game by Hans Chun is licensed under a Creative Commons Attribution 4.0 International License .

Playing Cypher - Transparent Difficulties

I've realized lately that I'm doing something very different from the play examples in Cypher System books. I've been telling my players the difficulty levels of everything before they roll. I think this is because the majority of my games have been one-shots, demos and short arcs at home. But I like it! There's been little consistent growth in play, so it's been natural for me to make things really transparent for players. Here's what I mean: A player attempts a task. They describe it, saying what they want to do. I tell them the difficulty number (i.e. 5) and what they have to roll to beat it (15). We use Skills and Assets to modify the difficulty. They get the opportunity to apply Effort. Then we roll. That's how I've been running the game. I notice that the Play Examples in the book and most games I've seen keep difficulties secret. I think this is a natural thing in role-playing games but I don't know if I like the practice. It seems to...