Friday, June 7, 2013

RPG Realism And Why It's Crap

The past week or so has been quite busy so I had to take a little break from blogging. I'm back with some thoughts that have been brewing about realism in tabletop rpgs. This post is an expansion of a point I brought up in a previous post.

I don't think any tabletop roleplaying system mechanics can be "realistic". Skill levels, attack and defense rolls, damage, experience, modifiers - none of them have a damn thing to do with realism. Mechanics are abstractions - even the ones that most people consider complicated - and in no way approach realistically simulating anything. As such realism is a complete waste of time as a design goal. If you're trying to create a ranged combat system to realistically simulate firearms, just fucking stop now. The same goes for sword fighting, or vehicle combat, or anything else. You're just going to wind up plastering "Most realistic rpg ever" on the cover and get mocked. Maybe go play a video game instead if you want that kind of realism.

But are video games really more realistic just because they're driven by HD-quality graphics and physics engines? Given the uncanny valley, flip-floppy rag doll physics and a host of common glitches that are fodder for nightmares or Tool videos I say, "No". That's because while photorealistic graphics and attention to detail is a goal for most video games, actual realism typically takes a back seat. Most video games strive to have consistency, believability, and suspension of disbelief. Everything else is gameplay and looking pretty, and those are the two things that tend to attract me to videogames (although looking pretty and glitchy as hell isn't).

Others just go for silly


Tabletop rpgs are a universe of magnitude simpler than a video game and "just realistic enough" is a lot more granular. Someone can go and run all of the physics calculations and figure out what kind of a damage bonus each point of strength should get, or how much energy a projectile loses per meter, but in the end all of those calculations will boil down to a singular abstraction of the reality the game takes place in. Realism flows naturally out of how those rules are interpreted and implemented in play. When realism is the design goal, in my experience complexity goes up and the chances of losing consistency or breaking down completely are much higher.

One of the defenses of realistic rules is that the GM often doesn't have experience with a particular circumstance - whether it be rock climbing, or driving a tank, or firing a gun, or hacking a computer. Therefore, the realistic detailed rules provide the framework for the GM to be able to adjudicate those situations. The problem with this approach is the designers often don't really know either (cf Vampire Undeath's being advertised as realistic and thoroughly researched, with a rule that a jammed assault rifle needs five minutes and an armorer to clear). This extends to many things like how difficult tasks should be (how many times have you seen a system with task thresholds that just seem out of whack), how often people succeed at tasks (ditto for people failing at tasks, but this is usually a dice issue), the number and scope of various modifiers, and how people learn. The designer might have pages of equations backing up why a particular modifier works the way it does and even that will be a white room affair that doesn't take into account countless variables.

That isn't to say it's not a good exercise to incorporate whatever level of realism into actually designing the mechanics. It might even help balance out some rules and figure out where the boundaries of believability are. But once that tweaking and honing is done, the consistency and playability need to be the ultimate goal -  not whether or not the game accurately represents the unladen weight of a swallow.