As someone with limited experience on how to run a game, I’m always interested in learning more about it.
Most of us just fall into the role of the Game Master and start somehow without a predefined system. But it’s still a good idea to question our procedures to become better.
That’s why I enjoy reading blogs with Game Mastering tips, for example, gnomestew or the Alexandrian.
Another blog I can recommend is The Angry GM with the header “RPG advice with attitude”. And that’s what it is: really good information packaged into veeeery long texts and swearwords.
While I’m personally not a fan of the style, the substance is pretty great. It’s useful for many types of games although the author concentrates on fantasy RPGs à la D&D.
One of my favorite articles is Adjudicate Actions Like a Motherf$&%ing Boss! where Angry goes into detail on how to resolve actions (skill checks and all that jazz). Be warned, it’s a wall of text!
For my own reference, I created a flowchart with dot. With dot, you can create charts from plain text. It doesn’t create the prettiest graphs, but it’s neat if you want flowcharts without worrying too much about making it pretty and fiddling around with a graphical interface. Plus it’s easy to edit and to expand your graph if you need to.
Here is my dot code for the file:
label="How to adjudicate like a Boss"
start [label="GM presents the scene", shape=box, style=rounded]
response [label="Player decides response\n(intention vs. approach)"]
actionp [label="Is the action possible?"]
determineo [label="Can the action fail?\nIs failure risky/interesting?"]
usemech [label="Use game mechanics"]
outcome [label="GM decides an outcome"]
end [label="GM describes the result of the action", shape=box, style=rounded]
start -> response [weight=8]
response -> actionp [label="what (success/failure) &\nhow(what mechanics)?", weight=8]
actionp -> determineo [label="yes", fontcolor=darkgreen, color=darkgreen, weight=8]
determineo -> usemech [label="yes", fontcolor=darkgreen, color=darkgreen, weight=8]
usemech -> outcome [label="determine skill/ability etc.,\nroll dice", fontcolor=darkgreen, color=darkgreen, weight=8]
actionp -> outcome [label="no", fontcolor=red, color=red]
determineo -> outcome [label="no", fontcolor=red, color=red]
outcome -> end [label="intention -> outcome = success/failure?\napproach -> consequence = what has changed\nin the world?", weight=8]
If you want to follow along, install a program which can run Graphviz dot (see the link above). With Linux, it’s pretty easy just to install the Graphviz package. 1
And now my output when I type in
dot adjudicate_like_a_boss.dot -Tpng -o adjudicate_like_a_boss.png:
If you like Angry’s article this flowchart might be useful to you. And if not, perhaps it’s still fun to try dot.