Tag: Theory

Post about game design theory.

  • The Dice Bank

    The Dice Bank

    Dice and I have never gotten along particularly well in the context of roleplaying games. I appreciate them as fun Platonic solids (other than the black sheep d10), they feel nice in the hand, and I’m not immune to that variable ratio schedule behavioral reinforcement that comes with a critical success. However, every game I’ve published until now doesn’t include them. They’re just too random: they make clever plans fail to work, interrupt dramatic moments with incongruous outcomes, and very often make competent player characters look like bumbling fools. I spent many years working very hard to avoid resorting to them, mostly by eschewing randomizers altogether, sometimes by adding cards instead. This past year or so, though, I’ve reevaluated that position. All of those criticisms are correct, but trying to remove dice has revealed the situations where they shine.

    What are dice good at? Well, the most obvious thing is that winning a roll feels exciting, it’s a little hit of gambler’s dopamine. It’s so expected from most RPGs that when I’ve tested diceless games, players would sometimes report that it didn’t feel like they were actually taking an action when the moment lacked the binding agent of the roll. Perhaps more crucially, they take heat off the GM: players will readily blame dice for their misfortune, even at low probabilities of success, but their ire may lodge with the GM when that’s the person who keeps telling them they failed. Third is the basic yet endlessly useful function of rolling on charts to procedurally generate people, places, and events, which also ease GM pressure by giving them a semi-automated tool to refer to.

    The Six-Sided Solution

    So if dice cause as many problem as they solve, how do we retain the good aspects while excising the bad? By rolling first and saving (for) later. I’m calling this new mechanic the “dice bank”, and it works like this:

    Instead of rolling a die when you need to make a check, roll six dice ahead of time and put them in the center of the table. Whenever a player would roll a die, they instead choose one of the dice from the table and apply it to their check as though they rolled it (adding modifiers versus a target number as usual), removing it from the pool. Once all six dice have been expended in this way, roll a new set of six dice and repeat. The GM uses their own separate pool of dice for NPC checks.

    Everything else stays more or less the same. You can slot this system into any otherwise standard one-die resolution mechanic – although I wouldn’t recommend it for systems without penalties on failures, as otherwise you could easily eliminate low dice by calling for meaningless rolls. I’m using d6s for all actions in the game I’m working on to test the concept, but it would work just as well with d20 or otherwise. You’re still always rolling, but you can peer a few steps into the future and pick when you want that high roll and when you can accept a low one. Therefore you’re always making a decision when you go to pick up a die, which isn’t necessarily the case with the normal roll-to-save paradigm.

    I’m calling it a dice bank as a generic term, but in a given game it might easily be given a diegetically flavored term like “fate”, or described as the opportunities presented to you. It’s inspired by the video game Citizen Sleeper, in which each day you roll a set of dice and assign them to the actions you take during that day. Although in that game the allocations only modify probabilities up or down, with the bank you directly use the pre-rolled dice for actions.

    What this means is that, although you still get the full range of successes and failures at randomized rates, you’re making a meaningful choice every time you make a check. You’re asking yourself (and often, collaborating with the group strategically) how important it is to win this time, enough that you’re willing to fall on your sword next time. Input randomness instead of output randomness, a melding of skillful play and dramatic flow.

    It also creates some unique design space in how abilities might manipulate the bank: you might be able to change the size of the bank to “see the future” a little further, toss out dice you don’t like, refill the bank up to maximum sooner than waiting to use it all up, store a die and carry it over into the next pool, or even opt to do an immediate new roll instead of selecting a die from the pool. Perhaps most interesting is the possibility of abilities you trigger by spending a specific rolled number, e.g. a spell that can be cast only with a 5. Such an ability would be especially valuable if it wanted low values like 1 or 2, because it would be an efficient way to get rid of dice likely to create failures in normal checks.

    Dice might also be spent on things that aren’t strictly skill/attribute checks: in theory they could also be applied to encounter rolls and the like. Essentially anything the system procedurally generates (events, reactions, hex contents, treasure) could be handled in this way. By default I imagine that the GM would use their own dice bank for these, both in-game and out: it would turn pre-session prep into a sort of minigame in which rolled dice became a sort of budget to work with, assigning them to different things. Alternatively (or on top of that), players might be allowed to influence procedural rolls with their own dice, explained as, say, the ability of a hunter to track down certain prey and avoid creatures they aren’t interested in.

    Further Considerations

    There are several dials to be tweaked here that may significantly alter how the bank feels in play: first of all, how many dice go in the pool. I’ve chosen six to roughly match with the upper end of the number of players around the table, but it could be higher or lower, or simply be set equal to the number of players.

    Second, each player could have their own pool of dice instead of drawing from a communal reserve. This would have the upside of removing the chance of arguments about who got to use which dice, but the downside of limiting the teamwork aspect of sharing dice. Collaboration could be reintroduced by making an assistance action that hands people dice from your pool to represent your aid. However, for the sake of parity the GM would then potentially have to maintain dice pools for individual NPCs, which would be much more of a pain. This may not be a popular opinion, but I strongly favor GMs using the same rules as any other player at the table, for consistency.

    Third, it wouldn’t have to be dice: you could easily use a deck of cards instead. In fact, if pools were individualized as above, the system would simply become having a hand of cards that you played from, a well-established concept everyone is already familiar with. I suggest dice first due to the prevalence of dice as the medium of randomization in TTRPGs.

    Fourth and finally, the dice could be rerolled on a particular schedule, such as whenever you make camp, or at the start of an encounter. This approach has a certain appeal, but I’ve decided against it for because it gives you more opportunities to throw out low dice. The choice of when you allocate your low dice is the most interesting aspect of the system, and not something that should be easily avoided.

    Although fairly simple on its face, the dice bank could manifest cascading effects throughout the rest of the rules once actually put into practice, so I’m going to get a few rounds of playtesting in and report back in another post. I shall redeem dice on my own terms.

  • Fiction Finally

    Fiction Finally

    Of all the pithy sayings in Apocalypse World, perhaps the most often repeated is “fiction first”: the idea that an action taken during play should begin and end with narrative, starting with a player saying what their character does in purely diegetic terms, the MC taking note of that description triggering a rule-specified move, then framing the outcome of the roll back in diegetic terms again. Passing from mouth to mouth and text to text gradually gilded this guideline into a sacred mantra of the Powered by the Apocalypse style, a cynosure that separated it as a distinct mode of thinking about roleplaying games.

    However: this phrase does not appear in the text of AW. The co-creator of the game confirms that the whole concept was not of his making1:

    Post by @lumpley,bsky,social
Everyone once in a while I'll get to tell someone, and they'll suddenly understand what I mean, that PbtA doesn't begin and end with the fiction, it begins and ends with the conversation.
"Fiction first" is an idea that came to PbtA later, from I don't really know where.

    This sort of philosophy seems to have crept in through a chain of derivations such as Dungeon World, that played a game of telephone about what the intentions of the original rules were. The book does name the principle of “to do it, you do it”, but this only means that moves must be grounded in specific actions the character takes (and that rolls cannot be avoided when a move is triggered), a solid piece of advice but one that applies to D&D as much as PbtA. Another likely contributing factor is the listed MC principle of “make your move but never speak its name”, that directs the gamemaster (and only them) to frame their own moves as pure narrative without reference to the name of the move they are making. This,  once again, is a fairly orthodox paradigm – virtually no TTRPGs before AW even bothered to systematize things the GM did into PC-like “moves”.

    Crucially: it doesn’t matter if later games of the lineage diverged from the source material. Apocalypse World is not a Q document from which deviance is heresy. One person extrapolating another’s work in experimental new directions is a fundamental function within the grand project of human art. However, this line of thought has, I would argue, strayed in the last fifteen years. It forgot its practical grounding in effective communication during play to transform into a shibboleth of roleplay-theoretical purity. I do not suggest any ill-intention on the part of the people who propagated the variant understanding and can appreciate the desire for free-flowing creativity it represents, but in practice it can present a stumbling block to fluidity of the group conversation roleplaying operates as.

    The primary problem “fiction first” creates is that of what might be called “move fishing”.  Because players are expected to not explicitly invoke their moves, they must instead narrate doing things and hope the MC recognizes their intent. In many cases this goes smoothly (it’s hard to misunderstand “I swing my sword at them”) but in more complicated situations it can result in players resorting to wink-and-nod indicators of what they want to get things going. This adds one more task onto the shoulder of the person at the table already dealing with by far the heaviest workload.

    On a broader level, the phrase encapsulates a dogmatic approach to play that seems implicitly uncomfortable with “playing a game” at all. The slogan treats the mechanics of the game as unsightly things that obscure the true Platonic form of Narrativism the players ought to summon during a session. Intriguingly, it wraps around, horseshoe-like, into the OSR concept of avoiding rule reference as much as possible in favor of detailed description of what is said and done, to be arbitrated by a GM employing their own understanding of how the world works – “the answer is not on your character sheet”. Clearly both strains of thought are reaching for something commonly desired, but difficult to triangulate.

    Certainly, game mechanics can (and very often do) get in the way of fun. Everyone remembers a time when a random table produced an illogical outcome for the situation at hand, or the complexity of a subsystem ground play to a halt. Streamlining systems into simpler, sleeker forms for the sake of speed has constituted much of the TTRPG design program of the last two decades. How little one has to think about rules while using them acts as an admirable indicator of their elegance. As Antoine de Saint-Exupery said:

    “…in the machine of today we forget that motors are whirring: the motor, finally, has come to fulfill its function, which is to whirr as a heart beats – and we give no thought to the beating of our heart. Thus, precisely because it is perfect the machine dissembles its own existence instead of forcing itself upon our notice.”2

    I do not believe we have perfected tabletop roleplaying games yet. Game design as a field is relatively new and much work remains to be done discovering those ideal natural patterns. However, I think we must accept as a bedrock premise: to play a game, you play a game. We don’t need to run an RPG through the additional emulation layer of a game of pretend, feigning that we don’t actually like assigning numbers to things and bouncing them off of each other. Let people say what moves they’re making! Give them big colorful buttons to press, and let them play to find out what happens.

    I won’t assert this as an absolute, given that the word “game” is a Wittgensteinian phantom that defies all but the haziest of definitions. Serious LARPs, for instance, often operate along quasi-ritual lines that encourage prior internalization of how play proceeds so as to minimally break the magic circle of role absorption during play. Even those, however, accept that when significant confusion and distress would intrude, they must fall back on out-of-character communication.

    Which is, ultimately, “the conversation” of a roleplaying game, at the very least the sort where people sit around a table and scribble notes on paper. The procedures given in the book provide rules of order for those assembled to carry on their discussion about what happens next. Some games even embrace that distinction between the players and the player characters, espousing the group as akin to a writer’s room hashing out the next episode together. One doesn’t have to go that far, though – it’s fine to stay in close third person, so to speak. Narrate what your character says in as close an approximation of their imagined voice if you like, but don’t feel guilty for wanting to roll dice every once in a while, too. It’s normal to cycle between the two modes; if you didn’t want to use rules, you could be writing a screenplay or a novel instead. In fact, you should, if the inclination strikes you! There’s a freedom to dictating precisely what you want to happen without needing the go ahead of a flowchart, and a satisfaction of creating something all your own.

    What you shouldn’t do it feel ashamed of not writing a story, and choosing to play a game with your friends. Each option is its own format with its own merits. Likewise, when you design a game, be willing to indulge yourself a little and admit that you enjoy making games. Mechanics are good, actually! Well-written procedures efficiently guide play toward interesting interactions and away from acrimonious disputes. We should expect games to offer us rules that we’re excited to manipulate, not burdened with the necessary evil of. “The fiction” is well worth maximizing, but it’s not zero-sum with mechanical engagement.

    There’s an old contestation that TTRPGs are not about telling a story so much as doing things in character that can be interpreted as a story in retrospect. While the weeds of that formulation are best left for getting in to in another post, the end state of a session is the same regardless: you look back and see that you’ve collectively created a story. Everything you did during the session, game mechanical or not, contributed toward crafting it. Fiction is always the final product.

    Footnotes

    1 https://bsky.app/profile/lumpley.bsky.social/post/3llkfqyha7k2p

    2 Wind, Sand and Stars (1939), trans. Lewis Galantiere