In the past, I've written a few articles discussing "My Own Heartbreaker", or MOHb, where I indicated some of my preferences at the time for game design elements. You can find most of them under the MOHb and gaming philosophy tags if you're interested. This article will discuss where I stand now, after time thinking about the matter, recent gaming, and so on.
First, let me say that I do still like GURPS, D&D, Traveller, and so on. They are some fine games, and there are quite a few games, even recent ones, that retain the old-school emphases that I like. I've even begun to soften toward PbtA ("Powered by the Apocalypse") and similar games, though they still aren't my main preferences. Still can't stand FATE, and even less the "talking stick" games like Dread and such where the mechanics exist just to determine who gets to write the next line of the story. That is terrible, and in my opinion places the emphasis in exactly the wrong place, minimizing the characters and emphasizing the players. Some of those games go so far as to allow the talking stick player to make decisions for other people's characters, and that's just annoying to me—I would still go so far as to say that such games aren't roleplaying games at all, since you aren't playing a role any more than someone playing Axis & Allies is, to choose a random example of something that is not a roleplaying game. But I'll save that discussion for when I ever get around to reviewing Dogs in the Vineyard, the game where you can't find out how well you did or didn't do until after the action is over.
So, for now I'd rather talk about what I do want to see in a game at this point in my gaming career, and maybe a bit about my history of preferences in that context.
My most formative experience in RPGs, as with most people, came in my first ever adventure. It's possible that I've discussed it on this blog before, but it's relevant now, so. I was 10, and my friends had talked me into playing this new game, Dungeons & Dragons, which I initially confused with Dungeon Dice and so was baffled by their descriptions of how their games went. When they got me over to play, I was told that since I was new I had to play a "first level" character, and what class would I like? After being given the options, I naturally picked Magic-User, because who wouldn't be enticed by the promises of infinite power dangled by magic, and anyway I had no idea what this "module" titled "Tomb of Horrors" might offer as a challenge.
Rolling up my character, I learned that I had a lot of "gold pieces" to spend on things, but I didn't really see a lot of things in the list to buy. So I innocently asked the DM, my friend's older brother as I recall, if I could hire anyone to help me out. He looked blankly at me for a moment, then remembered something in the Dungeon Master's Guide and started flipping pages. "Here you go," he said and showed me some tables of laborers and another of mercenary soldiers. I listed out some things, added up the costs, and soon I had a sizeable mercenary company at my command. To make a long story short, the DM allowed me near-complete control of my soldiers, and so as it happened, I was the only survivor of a party that included some high-level characters simply because I'd risk soldiers instead of my own character when checking traps and such. Oh, and at least three (!) party members, not even counting a couple of my troops, reached their hands into a sculpted green devil's mouth.
My lesson: have other people, or robots, to do things for you. As a result, I really like games that allow me to have a faction or otherwise put me in a position of authority. Charisma is not a dump stat is what I'm saying. For the purposes of this discussion, I have really come to appreciate systems that include faction rules that make it easier to make use of groups in play. While games that force you to track resources directly, as D&D does, are good, but not as good as ones that allow you to abstract all of that and let your virtual accountants take care of the bean-counting. Reign is probably the first I've seen to explicitly do that unless you count the megacorporate duelling rules in TORG's supplement Nippon Tech or the similar rules in Shadowrun's supplement Corporate Shadowfiles, but now it's pretty widespread, being found in everything from the Sine Nomine games like Stars Without Number and Silent Legions to even GURPS (which has a refinement of their version of factions coming out soon). So, yeah, faction rules are pretty important to my ideal game.
Next, when I first saw Hârnmaster, I was a bit in awe of the depth of the system and how it connected to the detailed setting that they'd been developing. But the thing that most captured my imagination was the descriptive wounding system. Instead of drawing from a pool of "hit points" or "hits to kill" or "stamina" or whatever, the Referee would make a few quick rolls on a chart and end up with a wound that could be described: "an infected shallow cut of 3 injury points to the left thigh", "a 25 injury point deep puncture to the chest that is bleeding 2 points per round". Injury points refer to the penalty to actions that use the affected body area, so that a 3 injury point wound would subtract 3% from any skill or other d% roll that involved the particular body part. I've since seen similar systems in a few games, such as the original BTRC house system that was used for TimeLords, SpaceTime, and WarpWorld. BTRC has since changed its preferred house system twice, first to CORPS (which used a simplified version of that descriptive wound system from their previous house system), and then to EABA, which I don't know well enough to describe how it works. I own a copy in PDF, though, so I should probably go through it one of these days. It's just that PDFs are such a pain for reference works like that, in my opinion. They're fine for adventures, but rules should be in hardcopy, in my preference.
Anyway, now I have a hard time justifying point pools to myself. Descriptive injuries are easy to implement, provide more narrative flavor while still being sufficiently quantified for simulation purposes, and provide for a lot of other related rules—Hârnmaster tracks different medical tools and procedures used to treat different types of injury, for example—that similarly add to the roleplaying experience. So, yeah, descriptive injuries are a must in my ideal game system.
When I was younger, I was very interested in "realism" in games. That is to say that I preferred games where the results were within parameters that I could envision occurring within a given set of scenario assumptions. I still am, as it happens, but in my youth that largely meant more complexity. The more elements of the situation that we could model, and the closer that model's statistical outcomes were to actual statistical outcomes, the better was my thinking at the time. Now, maybe not so much. I've come to understand that most of the elements either don't need to be modeled—the usual situation—or else it turns out that our hypothetical models of them don't actually resemble the real-world events anyway (when GDW's pioneering and excellent* work on modeling wound physics in games turned out to be only partly accurate, I learned a lot about how science really works, and more importantly just where we actually stood in comparison to the claims made about our current levels of knowledge). The point is, though, that there are ways of modeling "realism" that don't need to obsessively detail every aspect of the simulation. The bizarre "hydrostatic shock" modifiers, "stopping power", and similar minutiae in some of the optional Top Secret rules were detailed, for sure, but also entirely lacking in any sort of realism, to pick an example. So, another element that I am looking for now would be simple but accurate modeling at the table.
That aside, I am perfectly fine with front-loading complex calculations. Detailed vehicle and weapon design systems have not only never daunted me, they have satisfied my sense of verisimilitude. Such systems, of course, can never match a detailed CAD program optimized for the purpose, but they can provide statistics that are close enough for gaming purposes. They also allow the designer to weigh tradeoffs in the design phase that aren't really dealt with in fiat methods of giving equipment statistics. Sure, a designer can just make up some numbers that look good and then paper over matters by abstracting whatever they don't want to deal with, but I am interested in going at things the other way around: providing a reasonably accurate simulation, then working out designs within that simulation to optimize for various tasks. This is all a really wordy way to say that my ideal game would include detailed vehicle and equipment design.
This has gotten a little long, so I think that I'll set it aside for now. I should return to this topic later. I'll give it it's own tag, too: ideal game.
*Really, it's great. There are aspects of it that I think could still usefully inform other models to this day, like the whole cross-section thing. That would usefully cover the difference between the relatively low energy of a .45ACP and the observed injury compared to, say, a 9×19mm Parabellum or 10mm Automatic.
No comments:
Post a Comment