Like any designer I have to consider how my work is distinct from existing work. My Faction Sparkbook is not the first TTRPG product to systematize faction creation and play. I’ve read many TTRPGs that have fantastic rules for faction play, with Blades in the Dark, Stars/Worlds Without Number, and Cairn 2e as some exemplary examples.
Solipsistic Factions
But across all of them, there is a lack of relational mechanics for creating and roleplaying factions. I think this blindspot is the same blindspot most (traditional) TTRPGs have for character mechanics. Most mechanics for representing characters are solipsistic, they model characters and their attributes in a vacuum and treat relational aspects of characters as something solely within the domain of the non-mechanical narrative. This isn’t universally true of course, but I think it’s the default way many TTRPGs represent characters. I suspect that’s influenced how designers approach factions.
Cairn 2e, whose faction mechanics are fantastic and I think the closest to what I’m developing in my Faction Sparkbook, is a good example of this character-like approach to factions. When generating a faction in Cairn 2e you define its type, traits, advantages, agendas, obstacles, and agents, all with random tables. Some of the tables have relational options on them, mostly in the agendas and obstacles results, but the relationship the faction has with other factions and/or the PCs is not considered a core attribute needing definition.
Define the Relationships Between Factions
Many of the mechanics in my Faction Sparkbook focus on explicitly defining factional relationships. My “External Faultlines” tables directly define a faction by the relationships it has with other factions, and the structure of those relationships. The “Internal Faultlines” tables define a faction by the subgroups within it, and a faction’s “Influencing Force” is defined by how they interact with those outside the faction.
The “Faction Friction” table I put on my business card is an example of a relational faction tool. The relational column (“and with each other…”) is a condensed version of the External Faultlines tables from the Faction Sparkbook (v0.2). An assumption of that table, and the relational factions tools I’m developing, is that a faction should never be generated in isolation. It’s best instead to create two (or more) factions and define their relationships from the get go.
Faction “Reaction” Tables
Factions in TTRPGs are not compelling merely because they have relationships. The most compelling part of factions is that their relationships to other factions and the PCs can change (usually in response to the PC’s actions). “Reaction” tables go all the way back to OD&D, but I’ve always felt that calling them “reaction” tables was a misnomer. They’re more like “first impression” tables, representing how NPCs react to the mere presence of the PCs they do not know already.
But just like solipsistic character mechanics, where relationships are conceived of as part of the roleplay (and therefore outside the mechanics, for some silly reason), reaction tables never extend past first contact with the NPCs. They define initiate conditions only.
But that need not be the case, especially for factions. While it might make sense to fluidly roleplay individual NPCs (versus rolling to see their every next move), factions are often reacting to the PCs asynchronously. Because they’re groups with leaders, they’re often acting strategically, deliberating on what to do and then enacting a plan. This almost certainly occurs outside of the PCs view, with the faction’s reaction coming at an uncertain time in the future. This narrative situation lends itself well to a random table for GMs!
A Faction Retaliation Table
Few instances are more narratively interesting and tense than how factions might retaliate when harmed, wronged, or offended. To represent this, I’ve made a first draft of a “Faction Retaliation Table,” which I plan to include in future updates to the Faction Sparkbook.
As constructed, it has two subcomponents. The first is d4 “threats” for the ways in which a faction’s reaction to being wronged is to demand a debt be paid, with the threat of retaliation if it’s not. The Retaliation table refers to a separate “Debts Table.” I haven’t fully drafted this table yet, but it will include things like compensating the faction with money / rare items / time, or doing a deed for the faction / supporting them in some fashion, things like that.
The second component is d6 options for the ways in which a faction reacts with direct retaliation of some fashion. I’ve tried to describe them at a high enough level that they can fit any situation. There’s also a d10 option for rolling on both the “threats” and “retaliation” subcomponents.
Faction Retaliation Table
| When harmed / offended | ||
| d10 | d4 | Retaliatory Threat |
| 1 | 1 | Begrudging respect; demands debt (roll on debts table); court another faction as allies against you if refused |
| 2 | 2 | Rivalry established; demands debt (roll on debts table); proportional response if refused |
| 3 | 3 | Contempt garnered; demands debt (roll on debts table); disproportional response if refused |
| 4 | 4 | Masked rage, demands two debts (roll on debts table); sworn vengeance if refused |
| d6 | Retaliatory Action | |
| 5 | 1 | Court another faction as allies against you |
| 6 | 2 | Symbolic response / condemnation |
| 7 | 3 | Proportional response, same action |
| 8 | 4 | Proportional response, different action |
| 9 | 5 | Disproportionate response |
| 10 | 6 | Sworn vengeance with no bounds |
This is just a first draft, and it obviously needs some work. The asymmetry in length and complexity between the d4 threats and d6 retaliatory actions is an issue. I also want to make the d4 threats feel more distinct, and I may expand the d6 retaliatory actions to include more options.
But I’m happy with the first stab at a “Faction Retaliation Table.” It very much grew out of this feeling I have that what the Faction Sparkbook is adding to existing work is a systematized relational angle to faction play. And this relational lens to factions needs to extend beyond creating the faction and into how the faction is played in game.

Leave a Reply