Template:Meaningful Checks

From AF wiki
Revision as of 06:23, 21 August 2014 by Frameworker (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Meaningful Checks
A check should only ever be attempted when both potential outcomes have consequences. Say you need to make a strength check to push open a door. The effect of success is obvious (the door is opened), but is there a consequence for failure other than just having to try again? If there is, then it's a valid check. But if there isn't, assume you eventually manage to push the door open and move on. One potential consequence is effort expended. For example you might be able to eventually force the door regardless, but if you fail the check you are exhausted from the attempt. Likewise there could be a time limit involved, and a successful check forces the door before reinforcements arrive.

Likewise, be prepared to follow through on either possibility if the check dictates it. If that sounds untenable you need to review your assumptions. A check may not be required at all, just a narration of what happens. When a check really should occur but one of the branches would derail the game it is generally acceptable to waive the check and move on if you are assuming a success. Assuming a failure is possible but much more frustrating. Any time you take this option you should highlight that the failure is due to circumstances outside the players control, and call out those circumstances so they have an avenue for changing them.

Never cheat a check. When you get a result you don't want it introduces precisely the chaos and surprise that makes a dice driven game different from a story driven game. What you thought was the climactic victorious moment is actually a tragedy or a setback. Go with it, and see what's down that path rather than trying to force the dice rolls to create the story you want to tell.