Monthly Archives: January 2016

Damage symmetry

Consider this house rule for traditional D&D:

When an attack roll misses, the attacker suffers damage from the defender.

This gives every attack roll the potential of loss as well as gain. Damage inflicted by the defender would be based on the equivalent of a basic attack as situationally appropriate. For example, someone attacking a dragon from behind and missing might take tail swipe damage.

How do you think it would change the game?

This shares some properties with what I have called monological combat before, though it remains more firmly within the familiar D&D approach to combat turns. See also: monological combat example and monological save versus magic.

Some potential consequences I can see include:

  1. Encourage avoidance behaviors because attacking feels riskier.
  2. Decrease the sense of stasis caused by several misses in a row.
  3. Speed up combat by increasing average damage per round.
  4. Cut down hoards of unchallenging enemies quickly.
  5. Decrease the defensive value of armor.

Given a choice as a player, would you like to use this house rule? Why or why not?

Doctrine of proceduralism

Proceduralism is the degree to which a game relies upon explicit procedures. It is one of many different descriptors that can be used to understand and classify games. Other examples of descriptors include mechanical complexity, optionality, loci of narrative control, and so forth. My intent when I build game systems and content is to encode procedures efficiently into the process of play rather than adding rules overhead necessary for the desired relationships. That is, I want the procedures to feel like a part of the game that players sit down to play, not some cost that must be paid. This has been my intent especially with the Hazard System.

In my view, many game designs underweight the immediate cost of performing game procedures during play. For example, in early versions of TSR D&D, encumbrance is handled by measuring weight carried in coins and summing over all gear carried. Though the coin counting encumbrance procedure would probably have the intended effect if it were used, it is often ignored because it takes effort that does not seem to be play. Though individuals differ regarding their tolerance for such hassle, there seem to be few inherent benefits to adding purely transactional costs to the process of play.

Further, procedures are maximally effective when all players in a group comply, meaning that procedure effectiveness is often subject to the player with the least tolerance. In a traditional tabletop RPG, a conscientious referee can often take on an additional burden to mitigate the cost of procedures on other players, but this has its own drawbacks.

This is probably a domain-specific manifestation of general decision-making myopia. For example, people tend to underestimate the amount of time a future task will take even given domain-specific experience. (This is the Planning Fallacy.) In games, this tendency often comes, I think, from a designer focusing more on the desired outcome of a procedure and less on the effort or hassle involved in the practice of using the procedure.

To formalize different kinds of proceduralism, consider that a procedure may either feel like play or feel like work. Call the first kind of procedure intrinsic and the second extrinsic, mirroring theories of motivation. Intrinsic procedures are not always simpler. Instead, they focus attention and effort on the game processes that are most rewarding to the players. For example, more procedural combat rules may be more engaging due to the immediate stakes. That is, they feel like play rather than work or hassle. Procedural fluency then could be thought of as the overall balance between intrinsic and extrinsic procedures.

The definition above incorporates player taste. While my general sense is that heavier logistical procedures are almost universally experienced as aversive, there do seem to be some exceptions worth noting. For example, competitive players or those that value game mastery may appreciate highly extrinsic procedures as long as they can be used, respectively, to gain a relative advantage over other players or overcome game challenges effectively. Though there may be some fit effects between procedure and player personality, even entirely ignoring this nuance there seem to be many opportunities to make game procedures more generally fluent given that few tabletop RPGs pay attention to the concrete experience of procedures in play.

Though play testing could evaluate a game on any number of different dimensions, such as inter-player power balance, compliance with some aesthetic standard, or pedagogic efficiency, I believe that procedural fluency is a particularly good candidate for evaluation. Some questions that might help identify procedural disfluency include:

  1. Are players following the rules?
  2. What are players handwaving?
  3. Are players creating shortcuts?
  4. Do the shortcuts accomplish the same goal?
  5. Is the reward payoff disconnected from the procedure’s deployment?
  6. Do players not understand the intended impact of the procedure?
  7. Do the procedures feel like a drag outside of the game itself?
  8. Is the procedure designed to solve an extra-game problem, such as argumentativeness?
  9. Does the procedure require prosthetics such as spreadsheet software?

Finally, to distinguish this doctrine from the old “system matters” position, it is worth emphasizing that proceduralism is only one dimension of many that define a game and that the experience of a particular game arises from far more than just following the procedural rules.