On Generic Systems: Cypher
11/22/2025 Updated Blogwagon participants:
Random Ape Encounter's assessment of GURPS
Fluorite Guillotine's assessment of Cortex Prime
lootlootlore's assessment of Savage Worlds
My friend “Tombombodil” in the MCDM discord made an interesting prompt statement the other day.
Someone should write an article investigating the style of play implicit in generic systems, because generic systems still have an identity and things they’re better or worse at.
I later underscored the prompt with the question “how generic is the system really and what types of stories [do] they support?” My friend soopersmert of the new Random Ape Encounter blog thought this was a compelling enough prompt to propose a mini blogwagon project to capture a corpus of authors reflecting on their table time with systems like GURPS, BRP, Cypher, FATE, Genesys, and others. Smert started us off strong with GURPS today and I’ll try to keep this post up-to-date as people choose to join in.
Of the flagship generic systems, I have the most table time with the Cypher system. I’m not a historian of the system so this may not be exactly the sequence of events, but after his work on 3rd edition D&D, Monte Cook took his game design chops to a new system/setting hybrid called Numenara. Numenara is an incredibly gonzo fantasy/sci fi hybrid setting and the system was the groundwork of what later became Cypher. The system itself is named for one of the two tentpole mechanics of the game, Cyphers, which are single-use consumables to be seeded everywhere in an adventure location. Cyphers are arguably the best inheritors of Vancian magic in tabletop gaming; they are weird, situational power spikes that any character can use to dramatically change the terms of a situation.
My Cypher Experience
I bounced off of Cypher the first time I interacted with it. There was a Humble Bundle for Numenara Destiny/Discovery that I got for some pocket change. I read the first chapter of the core book, felt my eyes glaze over, and stored it in my PDFs folder for a rainy day. The setting didn’t grab me and I didn’t really wrap my head around the core task resolution system. Rather than extensively quote myself, if you are interested in my writeup of the Cypher resolution system (the other tentpole mechanic of the game), see my post here. I’ve since come around on this mechanic, which I’ll discuss later.
Some time after this first interaction, I listened to a podcast interview with Jordan Morris, the author of Youth Group, a graphic novel about fun youth pastors fighting actual demons and devils. This premise tickled me and I thought it would tickle some of my local friends, so I put out some feelers to some tabletop communities asking if anyone knew of a system that would serve the premise better than trying to torture 5e D&D into shape for it. Someone pitched me on Old Gods of Appalachia, a branded application of the Cypher system to fit the horror podcast setting. I was intrigued; I hadn’t listened to the podcast but I live in Appalachia and thought that might improve the pitch to my friends. Something about the framing of the system for horror, its separation from the Numenara setting, and my additional context of running games by that time made the system click for me. I’ve run a few dozen hours of OGOA now.
In addition to this specific setting, I have played in some short shot games with Cypher enthusiasts from the Cypher Unlimited discord, I have run the “Claim the Sky” superhero/comic book supplement for a group of friends, and I’ve gotten to be sort of a player-coach for a GM in the MCDM discord, so I do feel qualified to talk about what has and has not worked for me in the system.
What Is Worth Commenting Upon?
Please note that I consider myself firmly a post-OSR blogger, so take this all with however much salt you need.
Legibility
At its core, Cypher is a D20 roll over system. For everything. And all rolls are player facing. This makes it extremely legible and fairly simple for players with experience in the 3x-5x D&D tradition to pick up and play. In two separate groups that I’ve run for, they have remarked that it is very easy to learn as a player. GMs in those groups have remarked that it is a good system for teaching people, especially 5e lifers, how to interact with the whole “scene” in play – the encoded steps of negotiating task DC encourage players to think about whether aspects of the scene would ease or hinder the task.
The converse of this point is that the system naturally asks that every roll (that is to say, everything that is more than a 0 out of 10 in difficulty) must go through this negotiation procedure. In a high-trust table of players who are fluent in the system, the negotiation is snappy and does not feel much different from the conversation-as-play procedures of the post-OSR. If players are new or rusty, it can quickly bog down play.
Strong Character Identity
I love Cypher’s concept of the “character sentence”. When I played in a short shot game as Jacques, the Ghost Adept who Conjures Bullets, I felt like that sentence immediately put me in the shoes of my spectral cowboy. I think this is really a sub-bullet of my point about legibility, but it should be underscored that it is very easy to create a character with a clear and communicable identity through Cypher’s character generation process.
This is further supported by the codified “Arcs”, an important part of character progression and advancement. In my playtime, I treated “Arcs”, the five-step recipes for establishing table stakes for a character, as player-driven goals, similar to Quests in His Majesty the Worm. Like any sort of player-driven narrative goals, some players take to this with a lot more agency and intuition than others, so I have observed people take command of sessions in pursuit of their goals and I’ve seen players sort of wait to be handed clues in order to make progress.
The knock-on consequences of this is that Cypher fits most smoothly with Nitfol style GMing. If the GM pre-writes a story, players are going to struggle to exercise their character identity. I’ve found good luck with blorb-style prep for some sessions, and I’ve also had good luck telling players the day before a session “there’s going to be a party, think about what you want to do to contribute to it” and gone in with an index card’s worth of notes to run a three hour session. With the mechanical focus of the game being one-off consumables, the only incentive for buildcraft or a focus on loot is to do fun narrative things in game, so it is not much of a Frotz game.
So is Cypher Universal?
I think so, but I am not a Cypher dead ender. The design of Cypher makes it a very nicely legible bridge between traditional adventure games and what we now call “storygames”. Just today I was reading an old blog defining story games which contained the insight:
In a story game, a player’s ability to affect what happens in the game is not dependent on their character’s fictional ability to do those things.
Cypher threads this needle with a handy XP-as-metacurrency system. Players can introduce elements to the game that their characters may have no part in, but the scope of those elements are (I think usefully) constrained by aspects of the character. Unfortunately, as I’ve lamented before, this metacurrency is also used for rerolls on tasks and on character advancements, so the storygame element is often left to gather dust. That said, there’s a reason the new storygame-for-5e-players darling Daggerheart specifically cites Cypher.
The reason I bring this up is because Cypher has a metric shitload of setting splats that are frequently fun, well-written, and do a good job of informing GMs how to set up genre games. When I ran Claim the Sky’s starter adventure as a one-shot for my friends, they really did feel like local neighborhood superheroes solving interesting problems. When I ran the OGOA starter adventure as a longer-shot game for some coworkers, they really did feel the creeping horror of exploring a laurel thicket that wanted to kill them.
Cypher can be bent into shape on genre and tone, but player characters will always feel like larger-than life lower-case-h heroes interacting in the world. If you want to run a game about heroic people handling interesting obstacles and challenging odds with a pretty solid hybrid between d20 fantasy and modern storygames, you can probably do it in Cypher.
Now. Would I go to the lengths of stapling on procedures to run a megadungeon or an old school wilderness hex crawl in Cypher? I know that people in the CU discord have, but I do not personally think it plays to the strengths of what makes Cypher fun to run and play.
My last meditation I want to leave Cypher-curious people with is one of my favorite pieces of advice about game-running that I think nicely captures what it should feel like to play this system:
[...] for now, remember this point: no single encounter is so important that you ever have to worry about the players “ruining” it. You hear those kinds of complaints all the time. “Her telepathic power totally ruined that interaction” or “The players came up with a great ambush and killed the main villain in one round, ruining the final encounter.”
No. No, no, no. See the forest for the trees. Don’t think about the game in terms of encounters. Think about it in terms of the adventure or the campaign. If a PC used a potent cypher to easily kill a powerful and important opponent, remember these three things:
- They don’t have that cypher anymore.
- There will be more bad guys
- Combat’s not the point of the game—it’s merely an obstacle. If the players discover a way to overcome an obstacle more quickly than you expected, there’s nothing wrong with that. They’re not cheating, and the game’s not broken. Just keep the story going. What happens next? What are the implications of what just happened?
If you want a system that empowers you and the players to just keep the story going, why not try your next genre one-shot in Cypher?