I would like to talk a little bit, and hear your opinions, on something not too often mentioned when discussing action resolution mechanics and processes in tabletop roleplaying games. That is when during the process you do the roll. The endpoints on that spectrum can be called Go then Roll and Roll then Go. At their extremes

  • Go then Roll is declaring your action (I attack, I investigate etc) followed by a roll to see how well you did that action. Example: I attack the ogre - roll d20+mod vs AC - on hit do d6 damage.

  • Roll then Go often begins by declaring how you intend to tackle the obstacle (with finesse, by being offensive) followed by a roll and once you have the result of the roll you choose what is actually accomplished. Sometimes you even at this stage you say what your character actually does. Example: I directly engage the ogre with violence - roll [something] and count successes - spend successes on things in the scene such as dealing damage.

As with many other things my preference lies in the middle, a bit skewed towards Go then Roll. Most of my preferred systems lie there, Genesys and many (most?) PbtA to mention some. As I player I find myself more involved in my character’s actions and for longer. Less of a do stuff - roll - get result - hand over spotlight. It is a greater invitation to get engaged in the narrative. When GM-ing it is a bit the same, and more. Apart from dragging the players kicking and screaming into narrative responsibility (slight exaggeration) it is very insightful what the players/characters do after they have done their primary thing. After dealing damage do they got out of danger? Take the foe’s attention giving their mates space to recover? It just give me so much more.

Genesys does this by not only having success/fail in it’s roll resolution by also advantage/disadvantage. Adv/disadv can then be spent on activating abilities or changing (minor) things in the scene to mention a few options. Many PbtA have on some (many) moves “on hit choose one, on strong hit choose two” when when looking at what happens after the roll. Actually the PbtAs does this really well by presenting the result options in the same visual space as the roll mechanics, on the same move card. Visual design is game design.

Interested in hearing experiences, insights and opinions.

  • @cell@programming.dev
    link
    fedilink
    English
    41 year ago

    I prefer Go then roll as I prefer to have the player understanding reasons and risks. Then the roll decide if the impact is met or avoided.

    It also permit something that I try to do which would be Go, do your things, then roll. It’s easier explained with an example: in the case of creating a bomb. Is it a well build bomb or a one which will never be predictable? In fact, the character thinks it’s a good one. So I try to let the bomb being built without rolling. When the bomb is planted or ignited, then the player has to make the skill check to know if the bomb was correctly set. We experienced it as more fluid and more dynamic.