Design

Running Heists in Cortex Prime (using Doom Pools)

faithfictionfatherhood Leave a comment

I’ve been working on some Cortex rulesets for a number of different settings and games that involve dramatic heists, espionage, and the types of tense action found in as varied places as Andor, For a Few Dollars More, Heat, Inception, the Gentlemen Bastards series, Mission Impossible, the Ocean’s films, etc., etc. I also recently watched most of Netflix’s Kaleidoscope (very much worth seeing), which might have been the direct catalyst for this write-up.

Regardless, these are the rules I’ll be using to run heists in my Cortex games until playtesting moves me to modify them. Maybe they’ll be useful for you, as well. If you’ve got criticism, thoughts for expansion and improvement, or stories of using the system, I will very much look forward to hearing them.

Heists

Rather than the default difficulty rules, Heists use a variation of the Limited Doom Pool system as well as Crisis Pools (Cortex Prime Handbook, pp. 32-33). Note that this system is only one in the toolbox for resolving actions—some “heist-like” activities (like a smash-and-grab) may be better served by the Narrative Action or Combined Action systems.

The Heist itself has a Doom Pool, starting with dice that represent the difficulty and complexity of the Heist (a low-level job begins with d6, d6; while breaking into the highest security facilities may start with a d12, d12 (such facilities should likely be the grand target after a series of set-up heists and should be used sparingly). We will call this specialized Doom Pool the Heist Pool.

Play starts with a brief Legwork phase as the players take actions to discover the countermeasures, security, and particular nuances of the heist they’re planning, then proceeds to the heist proper, and then to the aftermath.

Legwork

In the Legwork phase, each player describes an action their character is taking to learn about the target person, object, or facilities. The GM and player determine the Traits applicable to the test and then that pool is rolled against the Doom Pool.

If the test is successful, the character’s Effect Die is added to the characters’ collective Plan Pool. At the same time, the GM may purchase hitches from the player’s pool to add to the Heist Pool, representing security features identified, the target getting some indication of a potential attack, etc.

Each participating player should get at least one Legwork test. Once each player has had a chance to make a Legwork test, the players may discretionarily make additional rolls. Bear in mind that each roll carries the risk of increasing the Heist Pool as well as providing additional dice to the Plan Pool. Regardless of the number of tests made, no test may duplicate the action of a previous test made by another player; each new test must involve a new method of inquiry or course of action.

The GM should allow the players to see both the Plan Pool and the Heist Pool. If, after conducting their Legwork, they look at the relative pools and decide not to proceed, jump to the Aftermath phase.

Execution

Once the Legwork phase is complete, the players determine the general layout of the plan; they do not need to go into too much detail—the broad scope of who is doing what should suffice. Once established, the Plan Pool is rolled against the Heist Pool; this is called the Position Test.

If the Plan Pool beats the stakes established by the Heist Pool, the Effect Die may be used to reduce or eliminate a die from the Heist Pool. However, the GM may purchase hitches for the Heist Pool as usual.

The general result of the test should be interpreted to determine the general situation when we jump into the action of the heist. If the Plan Pool defeated the Heist Pool, the heist is going relatively smoothly when detailed play begins. If it failed, an unexpected complication has thrown a wrench into the works, part of the plan didn’t pan out, or something else has happened to leave the players scrambling to react and adapt to complete the mission.

At this point, use the Doom Pool to play out the heist. In addition to the other options, players may spend Plot Points for a Flashback; this allows a player to create Assets representing previous actions taken before the heist to set up the current action even though they had not been previously described. This ability is essential to ensuring that play keeps moving and that players don’t get incapacitated trying to plan for every possible scenario in the Legwork phase.

During a heist, the expenditure of d12, d12 (to end the current scene) indicates that the heist has failed and moves play to the Aftermath—with the characters all having successfully escaped without further consequences over those suffered during the heist. If the initial difficulty dice in the Doom Pool were d12, d12 (which should be an exceedingly rare event), do not spend those dice to achieve this effect.

The expenditure of d12, d12 is not the only way the heist may end unsuccessfully. If a series of failed tests against the Heist Pool results in a narrative where failure makes the most sense, declare that to be the result and move to having the characters attempt to escape before being capture, killed, identified, or otherwise inconvenienced.

Once the characters have escaped, move to the Aftermath phase.

Aftermath

Some consequences of the heist (including but not limited to injury) will undoubtedly occur during the heist itself. But no heist goes entirely smoothly, and here is where the GM gets to put some additional pressure on the players and their characters.

The mechanics of this are simple: the GM may transfer the remaining dice from the Heist Pool to one or more Crisis Pools representing continuing consequences of the heist. These may represent an institutional response to increased crime, investigation by law enforcement, a team of hit men dispatched by the target to recover lost goods, the betrayal of a fence or other trusted person, the ignition of a war between criminal or other factions, etc.

The players may attempt to address these crises per the normal rules—taking actions to throw pursuers off the trail, getting revenge on traitors, etc. They may also attempt to avoid these consequences as best they can—lying low for a while, fleeing to another jurisdiction, or taking other actions to let the heat die down. If the narrative militates that a crisis pool should no longer exist, take it out of play whether or not the characters have acted against it directly. Cases and trails go cold, new crises of the day emerge, the news cycle refreshes, and even the biggest of jobs becomes history eventually.

Fighting Styles in WFRP 4e

faithfictionfatherhood 1 Comment

If you’re a follower of this blog, you know that I am fascinated by swordmanship and historical European martial arts (HEMA), and that I very much enjoy roleplaying games that demonstrate some knowledge, however abstracted, of the actual practicalities of melee combat. In that vein, I’m going to discuss in this article melee combat and fighting styles in Warhammer Fantasy Roleplay, 4th Edition.

Whether by intent or happenstance, the designers of WFRP 4e managed to capture some of the feel (and advantages) of certain fighting styles in their mechanics. This article will be partly a review of those design choices and their effectiveness, but a good deal of space will also be devoted to some character build advice in light of various fighting styles.

Generalities

The various incarnations of WFRP (for now, we’ll leave 3rd edition out–I very much liked what FFG was doing there, but it’s its own creature) have long erred toward deadly combat. The grittier feel, the pastiche of early 16th century Europe, and the incorporation of some of the less pleasant aspects of late medieval/Northern Renaissance life (treated, of course, with some humor) have always attracted me to this setting and ruleset over something like D&D (which has it’s own advantages and attractions, don’t get me wrong).

With regards to combat, there’s just enough of the feel of HEMA to sate desire, without something as complex and specifically focused on medieval combat as The Riddle of Steel. I have, years back, run a WFRP game using TRoS, with good result, and while that system will always have a fond place in my heart, my current mood does not need the full complexity (and time consumption) of that combat system in my already-tight gaming time.

The first thing that WFRP 4e gets right, I think, is opposed melee tests. Earlier editions first had the attacker make an attack test and, if successful, the defender could make a parry or dodge test to deflect. Omitting the additional step eases things along and captures more of the feel of HEMA, where combatants are not taking turns pounding on one another but involved in a complex and fast-paced set of test attacks, maneuvering, feints, parries, moves and countermoves. While it might be more “realistic” to have melee combat resolved by a single opposed test, winner scoring the hit, the attack roll vs. defense roll allows for additional mechanics (like certain Talents and weapon Qualities) that further deepen the choices available in the system.

The second point is the (optional) rule for bonuses and penalties for relative weapon length and In-fighting (WFRP 4e p. 297, hidden in the Consumer’s Guide and not the Combat section). These rules are simple enough not to slow combat while providing a greater significance for choice of weapon in particular circumstances. In fact, the In-Fighter and Enclosed Fighter Talents really aren’t of much use if the GM is not taking bonuses and/or penalties for weapon length into account. In my opinion, these rules should always be used.

Hit locations, critical hits by location, and piecemeal armor likewise add to verisimilitudinous combat. Wounds are visceral and specific, the choice of how much armor to wear–and where to wear it–matters. Again, this really only works to full advantage if the GM and players are paying attention to the Encumbrance rules. I realize that many GMs and players hate using all but the most abstracted of Encumbrance rules, but these really aren’t that bad and are worthwhile in the end.

Some players don’t like their characters to be permanently injured and/or disfigured, and I understand that, but the roleplaying opportunities that are opened up by these systems should also not be overlooked (the Physician career is an extremely valuable one in WFRP!). If necessary, allow means of reversing permanent injuries (Shallyan blessings or Jade magic) some additional prevalence and accessibility–give your players a few scenes or sessions to grapple with lasting injuries with the hope of undoing them in the long-run. Some groups, of course, are happy to retire characters who sustain significant injuries (and content with a high character death-rate to boot), and there’s nothing wrong with that either. Further methods of keeping visceral injury while softening the long-term effects would be to adopt a troupe-style play system (where each player has several different characters to choose from in each session) or to allow a greater carry-over of XP between characters than the rules-as-written provide for.

The Advantage system in the core book, though perhaps more narrative than realistic, does provide a method for mechanically mapping the fact that, once a fight hits a crucial turning point, it becomes more and more difficult for the underdog to snatch victory from the jaws of defeat. The Group Advantage system in the Up in Arms supplement provides a system more in line with Wrath in Wrath and Glory, which is mechanically satisfying and promotes teamwork amongst players (both in themselves admirable goals) but provides less verisimilitude than the core system. On the other hand, no one wants to watch their character get hit right out of the gate and then be locked into a long pummeling as the opponent gains ever more Advantage, so opinions may vary.

The last thing I’d like to point out here before moving to specifics is the use of weapon and armor Qualities. I don’t always agree with specific choices made by designers from a “realism” standpoint, but I find that they are well-written to provide for actually-different styles of fighting. I’ll mention some of these minor criticism and some ideas for “correcting” them below.

Fighting Styles and Builds

Combat Skills and Characters

Note that the Endeavors rules (WFRP 4e p. 195) make it relatively easy to learn the various Melee skills outside of a character’s career, but much more difficult to learn Talents from outside of one’s career. Therefore, if your character is not in the Warrior class, or one of the careers in other classes that contain combat Talents, err on the side of combat styles that require few or no Talents.

If your table has altered the way you treat the Unusual Learning endeavor for purposes of Talents, then the above may not apply. You may also plan to move between careers (and classes) to collect the skills and Talents you want for your character. Personally, though, I could drive myself mad in consideration of all the different possible career combinations focused on acquiring specific Skills and Talents, so I would also consider letting the narrative dictate your career choices and taking the below into account as a separate consideration.

Sword and Shield: The Go-To Style

The sword and shield (or buckler) fighting-style should be the go-to fighting-style for most characters, and particularly those without much skill in combat. This style offers good advantages without having any Talents dedicated to it and can become even more effective with just a few Talents.

Characters who do not intend to fight unless absolutely necessary should carry a sword and buckler. The first advantage of this is that a sword has only 1 Encumbrance and the buckler has no Encumbrance. The buckler provides both an armor bonus to all areas (with the Shield 1 Quality) and a bonus to defense (with the Defensive Quality) and they are, relatively speaking, easy to acquire and inexpensive. As a bonus, this follows historical precedent: in 16th century England, the sword and buckler were known as “the servingman’s weapons.” They were easy for retainers to carry (where weapons were allowed) and also allowed for shows of bravado in fighting the retainers of other nobles houses while minimizing (to the extend possible while swinging sharpened steel) of significant injury. (On the other hand, the earliest fighting manual of which I’m aware, the Royal Armouries Ms. I.33, a German sword-and-buckler manual from around the 1320’s, also demonstrates the complexity of sword-and-buckler fighting and its usefulness for skilled combatants).

Shields fall under the Melee (Basic) skill, meaning that your character may start with some skill in the style even in a non-combatant career, and the Unusual Learning Endeavor allows easy training in the skill even if it is not a career skill. Regardless of Talents, this weapon combination is strong one. As a side note, my read of the rules (particularly those regarding off-hand parrying weapons) leaves the possibility that defending with a shield in the off-hand (without the Ambidextrous Talent) imposes a -20 penalty on rolls. However, I believe that that would be a misreading of the rules as intended and that using a shield imposes no penalties to defense.

As a point of strategy, I would recommend that the sword-and-buckler fighter use the Fighting Defensively rules (WFRP 4e p. 158, upper sidebar) to first generate Advantage. If you’re using the Advantage rules from the core book, this allows you to potentially generate a significant bonus to your tests before going on the offensive. If using the Group Advantage rules from Up in Arms (p. 132-136), you don’t gain Advantage for winning defensive opposed rolls (the test must be one you initiated to gain Advantage). Still, for a character not intended for fighting, use of defensive fighting until you can get help from a more-skilled ally must be considered.

There are two Talents that may be of particular benefit to the sword-and-shield fighter: Reversal and Shieldsman. Both are somewhat contingent on which Advantage system you are using (Core or Up in Arms Group Advantage), so I’ll address them under each system:

Under the core Advantage system, Reversal allows you to take all of an opponent’s Advantage on a successful opposed melee test (including defense). That could potentially be a tide-changer. On the other hand, it’s usefulness is limited by the fact that, under the basic rules, your opponent would lose all Advantage and you would gain one Advantage anyway. Shieldsman is also of somewhat dubious use; the core description of the Talent gives you Advantage when you lose one the defensive side of opposed melee test. The cost for gaining the benefit of the Talent is high; I’d rank “don’t get hit” among the top rules of combat, so maybe pass on this one. The good news is that, under the core Advantage system, there’s not a strong reason to devote XP (or career choices) to specific combat Talents at all.

Both Talents become much more useful under the Group Advantage system: Reversal as revised in Up in Arms retains the benefit of gaining Advantage on successful opposed tests while defending with a shield. Shieldsman allows you to spend Advantage to deal damage when successfully defending (or to push your opponent). Since those careers that include Shieldsman do so at level two, this is one of the easiest Talents to achieve to increase damage output (through a pesudo-extra-attack)–but contrast with Two-Weapon fighting below.

The concepts above are equally applicable to sword and shield as to sword and buckler. The advantages of the larger shields are additional armor points and the ability to oppose ranged attack tests at the cost of increased Encumbrance. If you’re character is going to be at the forefront of the fighting, a larger shield makes more sense than the buckler.

As a last consideration in this style: the bonus armor points from shields are especially helpful if you are wearing light or no armor. But what about heavier armor? The Knight, Knight of the Blazing Sun, and Knight of the Panther careers all assume you’ll be donning heavy armor (see below) but also contain the Shieldsman Talent. I think that a shield is less useful when wearing heavier armors for several reasons: (1) you’re much likelier to be over your basic Encumbrance allotment, (2) there are better weapons to use when you already have high armor (such as polearms and two-handed weapons, see below), and (3) you hit somewhat diminishing returns on armor points by stacking in this way.

Fencing: The Masterclass

By “fencing” I mean the use of the rapier and parrying dagger (“main gauche”). This style offers some excellent benefits but requires a character who is devoting the majority of their XP to fighting. In fact, my personal view is that this method of fighting is too costly outside of the Duellist career. Some benefit may be seen by fighting with rapier and buckler for those outside of the Duellist career who do not want to spend too many resources on combat.

I’ll address the latter situation first: WFRP’s description of the rapier doesn’t actually fit the typical description of the mid-to-late 16th-century and early 17th-century rapier (which would have been a long thrusting weapon with a blade cross-section that doesn’t allow for strong cutting, if any at all). Instead, it describes the “cut-and-thrust” swords that began to focus on the thrust but retain strong cutting ability (the “espada ropera”). These begin to show up in the early 16th-century and continue alongside the development of the rapier. The confusion of terms is entirely forgivable, as the distinction is really a modern one and the contemporary terms used to describe sword types lacked hard categorizations that would be satisfactory to the 21st-century scholar. For ease, I’m going to follow the WFRP naming convention and use “rapier” generally.

The buckler was used with both types of weapons (the “cut-and-thrust” swords and the “true” rapier). In WFRP, you only need the Melee (Fencing) skill to gain the benefits of the rapier–you get the defensive benefits from the buckler without having to acquire the Melee (Parry) skill (see below). What are those benefits? The rapier has three potential advantages over the basic sword: the Fast and Impale Qualities and a long length rather than average (despite the description of the sword given, the mechanics of the weapon do seem to lean toward the “true” rapier intended particularly for thrusting). Again, with the weapon length rules, this can be a good additional advantage (though context matters, and tight spaces or in-fighting will make the weapon a liability, as was historically the case). Fast and Impale are the real attraction. Fast allows you to make attacks outside of the Initiative order and imposes a -10 penalty to defend for weapons that do not also have the Fast quality. Impale increases the likelihood of Critical Hits. If you want to spend some of your character resources on combat skill, but not too many, rapier and buckler is a strong choice, requiring only a single Melee skill and no Talents to get solid benefits.

The “true” fencer is the one who devotes great resources to combat with rapier and an off-hand weapon (cloak or parrying dagger, primarily). In such a case, both the Melee (Fencing) and Melee (Parrying) skills are required (the Parrying skill, not the Fencing skill is used for defending with the off-hand weapon, otherwise a -20 penalty is suffered, so the Defensive quality of the parrying weapon is useless without the proper skill). What are the benefits of the parrying dagger over the buckler? There are a few: first, the dagger gives you a backup weapon in the case of in-fighting, hedging some of the liability of the rapier. Second, the off-hand dagger does not have the Undamaging Quality (which shields do) in the case of dual-wielding attacks. The cloak offers the Entangling Quality rather than a significant attack, which may be a worthwhile exchange when fighting in a group.

I’ll also pick out the “hidden” advantage. As discussed below, the Ambidextrous and Dual Wielder Talents are requirements for the successful use of rapier-and-dagger in making two attacks per turn. Both Talents apply equally to ranged weapons and melee weapons, meaning a character can carry a brace of pistols, fire them both in the first round of combat (before others have a chance to react if you have the Fast Shot Talent), switching to sword-and-dagger to follow. That gives two high-damage attacks that may cause the Broken condition right out of the gate, an impressive opening move.

The rapier-and-off-hand fighting style needs several Talents to reach full potential. As mentioned above, Ambidextrous (two levels, for 300 XP in-career) and Dual Wielder remove all penalties to making attacks with both weapons in a turn. Levels in Riposte allow a character to deal damage while successfully defending with a Fast weapon (a number of times in a turn equal to the levels in Riposte). Combined with the two-weapon-fighting talents, a character using this style can put out a lot of damage in a turn, against multiple targets.

This combination of Talents is only found in the Duellist career, meaning only characters in that career are especially well-suited to this style of combat. Fortunately, that class is also full of other useful Talents: Combat Reflexes is of only some use given the Fast quality of the Rapier, but Beat Blade, Distract, Feint, Step Aside, Combat Master, Reaction Strike and Strike to Injure are all strong combat Talents (if somewhat contextual). Disarm seem to me to be a niche Talent; most of the time it will be a better choice to deal damage.

Two-Handed Fighting: The Damage-Dealer

The downside of the Two-Handed fighting style is that it requires a skill only a few careers have access to (though far more than the Fencing and Parrying skills). The upside is the Qualities available on two-handed weapons. I believe that this is a fighting-style worth considering even for characters outside of careers particularly suited to it (such as the Up in Arms Greatsword career.

I’m going to focus on swords here, as they have fewer downsides when compared to the Great Axe, Pick and Warhammer (which can be great weapons for tough and heavily-armored characters). The Zweihander gives you the Damaging and Hack abilities, which are both excellent. Damaging allows you to use the one’s place of the attack roll rather than the Success Level to calculate additional damage. That could mean up to 9 additional damage on a roll that barely hits–combine this with an already-high damage rating (SB+5), and you have the potential to drop many combatants in a single blow. Hack deals damage to armor, helping you win fights by attrition against heavily-armored opponents. Additionally, the high damage output can be an extremely efficient way to secure multiple attacks in a turn if using the Deathblow! optional rule (

The Bastard Sword trades out Hack for Defensive but retains Damaging; this is a very worthwhile trade in my mind.

Two-handed fighting lends itself to heavy armor, which I’ll address separately below. Aside from those Talents generally useful for combat, I find the Berserk Charge, Strike Mighty Blow, Strike to Injure, Very Strong, and Resolute Talents particularly useful for the two-handed fighter.

The knightly careers and Greatsword career are most suited to two-handed weapons as a style, though the basic Soldier career can be used, and, if willing not to worry too much about the Talents, any career could acquire the skill through the Unusual Learning Endeavor.

A brief aside for some rules modification changes: the Zweihander is a very specific Renaissance weapon, one designed for fighting pike formations and not general combat. It averages six feet in length, up to eight pounds or so (extremely heavy for a melee weapon), has a long grip, often hooks on the blade and a leather-wrapped ricasso (the portion of the blade that is not sharpened, closest to the hilt). The purpose was to swing the weapon like a big sword to knock long pikes out of the way (or potentially chop them up) and then to shift to holding the weapon like a spear (with one hand on the hilt and the other on the ricasso) upon closing with the enemy. The first technique allowed you to close in without being stabbed; the second shortened your weapon for closer combat while pikemen were struggle to drop their pikes and draw their swords. Outside of this situation, other two-handed swords were faster and more effective.

WFRP and Games Workshop seem to use the terms “Zweihander” and “Greatsword” interchangeably. A greatsword unlike a zweihander, was of a more modest length (closer to four feet, with plenty of variation either way in a matter of inches) and weight (three to four pounds). The greatsword was differentiated (or at least is now) from the longsword (a two-handed sword, despite what D&D tries to tell you) by its focus on the cut rather than having a blade shape more versatile between cutting and thrusting.

I believe that the weapon in WFRP really represents the greatsword rather than a zweihander. A zweihander write-up should have two entries: one for using the weapon like a huge sword, one for using it in a more spear-like manner.

While I’m nitpicking, I think WFRP’s “bastard sword” really represents a more traditional longsword. I’d changing that naming and I’d use the following for a true bastard sword (which often had a blade shorter than a longsword but could be wielded in one or two hands): I’d make damage SB+4, length Average, and give it the Defensive and Fast Qualities when used in two hands and no Qualities when used in one hand. Set cost and availability by reference to the two-handed weapons and the basic sword, leaning toward the former.

Polearm Fighting: The Versatile Choice

At face value, polearms are very similar to two-handed weapons. They have a dedicated skill (Melee (Polearms)), the weapons take two hands to use, seem to favor a heavier choice of armor, and even have similar stats (with polearms generally doing less damage than two-handed weapons).

The difference is that polearms offer versatility in a single weapon. For this article, I’m going to focus on the Bill, Halberd, Partizan/Glaive, and Pollaxe. Each of these weapons has the Defensive quality–if eschewing a shield in favor of a two-handed weapon, this offers some parity between the styles. Each then, based on the specific design of the weapon, offers some combination of Hack, Impale, Pummel, Slash (2A) and Trip. The specific choice of weapon should perhaps depend on your character’s Talents: Pummel is especially useful with Strike to Stun, but of limited use otherwise. Hack, Slash, Impale and Trip need no particular Talents. All but the partizan have Hack, making them useful for those times you need to wear down an armored foe. Impale is generally useful for increasing Critical Hits. Because Slash requires a Critical Hit, and the partizan gives you the choice between Impale and Slash, the combination is perhaps less effective than others. Trip can be an excellent Quality, particularly if used to set up strikes by teammates (or if using Group Advantage and spending for immediate follow-on attacks).

I would be comfortable saying that the choice between two-handed weapons and polearms is a toss-up and depends on your character’s (and your group’s) needs. I personally lean towards the two-handers.

Since I’ve made some suggestions for weapon changes in the categories above, I’ll do so here as well. Historically, there were two major styles of using a spear and/or quarterstaff (and these correspond somewhat with the use of other polearms). In the English style, the focus was on the thrust, making the weapon fast to strike and useful for maintaining distance. The German style wielded the weapon much like a longsword, focusing on strikes rather than thrusts and better able to defend against incoming attack. Switching between methods is not terribly difficult on the fly. That being the case, I would add Defensive or Fast to the spear (I’d also allow players to choose between Long and Very Long lengths) and change the quarterstaff’s Defensive to Defensive or Fast.

Cavalry: I’ll Take Swords for Five-Hundred

The lance and demi-lance are useful weapons…once. The Impact Quality makes them truly devastating, but outside of the battlefield, how often are you really going to use one? That leaves the Cavalry Hammer and the Sabre. Both use Melee (Cavalry) from horseback but a different skill (Melee (Two-Handed) and Melee (Basic), respectively) when on foot. The hammer has Pummel so, if your character also has the Two-handed skill (and Strike to Stun, preferably) it might be preferred. However, none of the Knight careers have the Talent (I might have thought the Knight of the White Wolf would), nor does Cavalryman or Light Cavalryman. Less than useful, then. On the other hand, the sabre uses a widely-available skill (all of the careers mentioned above get Melee (Basic), though Freelancer and Knight do not until Level 2). The sabre can be used in one-hand, allowing for the use of a shield and retains the Slash Quality (though it changes from 1A to 2A unless you use it with the Melee (Fencing) skill, but why bother), making it better than a basic sword.

The choice here is clear.

Armored Combat: Do You Even Lift, Bro?

Given the danger of combat in WFRP, armoring up as early and often as possible can be a useful choice. But it’s not necessarily an easy one. First, you need to look at the inherent penalties that accompany certain pieces of armor (particularly helmets and plate leggings, but bear in mind you suffer -10 to stealth if wearing any chain or plate). Then, you need to consider the Encumbrance penalties from lots of armor: you’re very likely to suffer -1 Movement and -10 Agility from your armor (And that’s before you consider your weapons and any traveling gear. Also, don’t travel in your heavy armor unless you’re expecting a fight).

A full suit of Plate Armor will give you 10-11 Encumbrance points from the get-go. You may want to wear some chain or leather under it (you can choose either or combine them). The relatively low ratings of armor (even plate) means that you either need to double up or accept that there’s a high cost and quickly diminishing returns for wearing lots of armor. But armor rating isn’t the only consideration: plate armor allows you to ignore half of Critical Hits, and that’s no small thing.

A fairly well-rounded set-up with some “oomph” to it would be a leather jack, leggings and skullcap under a breastplate and open helm. That gives you three points of armor on head and torso with one point on arms and legs and six points of Encumbrance. Add a shield and you get another one (buckler, no encumbrance) or two (shield, one additional Encumbrance). Even that, though, will put you into Encumbrance penalties unless you’ve specifically built your character in expectation of wearing armor.

Your basic Encumbrance level is Strength Bonus plus Toughness Bonus. You’ll want to get these stats into the forties as soon as possible. Very Strong and Very Resilient will be of significant benefit, if you can get them. Strong Back and Sturdy should also be acquired if you can. With the exception of the Knight of the Blazing Sun, all knight careers offer Sturdy at Level 1. Sturdy increases your Encumbrance rating by 2 x level, so picking up several levels before advancing would go a long way.

Bear in mind diminishing returns: assuming you get your Strength and Toughness up to at least forty and take four levels of Sturdy (a whopping 1,000XP), your Encumbrance maximum would be fourteen. You’ll have two to three points of Encumbrance for your weapon (assuming you’re not carrying several), leaving you eleven points for that full suit of plate with nothing underneath.

A durable set-up would be full plate (closed helm) with a mail shirt, a leather jack, leggings and skull cap. That’s fifteen encumbrance, plus three for your weapon. So, if you can get your Strength and Toughness into the forties and take one level of Sturdy, and tolerate the first level of Encumbrance penalties, you’re good to go. Take two levels of Sturdy and you can add a medium shield for even more protection. Without the shield, you’d have five AP on your torso and three AP everywhere else (while ignoring half of Critical Hits). With the shield and a Toughness bonus of four, you’re ignoring the first nine points of damage–that’s not too shabby.

Bear in mind, though, that the Robust Talent adds damage reduction per level of the Talent in a manner similar to Armor Points. You should strongly consider (if available to your character), adding this to the list of your character’s Talents if pursuing a front-line fighter, armored or not.

The Knifefighter: Close and Personal

This is not a mainline fighting style; it should be reserved for those characters who never intend to fight fair but may need to do some dirt from time to time–particularly when the victim–erm, opponent–is unawares.

Knives and daggers don’t do a whole lot of damage to begin with (and knives have the Undamaging Quality), so a high Melee skill and Strength bonus will be helpful. On the same lines, the Strike Mighty Blow Talent would be useful, as would the Stealth skill. The Combat Reflexes, In-Fighter, Enclosed Fighter and Disarm Talents would all be useful if you are unable to take down your target in the first strike.

There may also be times when a dagger or knife is all you have on you–the social or legal formalities may prevent the carrying of serious weapons in certain areas, or you may simply be caught traveling light. All of the above would help in such situations; as the goal when outgunned should be to break off the engagement and survive, the Flee! Talent may prove useful in such situations.

The Brawler: Back to Basics

The Brancalonia Roleplaying Game emphasizes as part of its genre that the law is unlikely to take much notice of the occasional bar brawl or streetfight where no weapons are produced and no “serious” injuries are inflicted (though unarmed combat can, of course, prove deadly). The same idea fits in WFRP: there are plenty of times when the Powers that Be simply have too much else going on (or simply don’t care) to deal with petty conflicts that do not involve anyone of importance. Further, there are some times when violence is a means to an end and not the end itself–the Protagonist and Racketeer careers are plenty evidence of this. You’ve always got your fists (almost always, anyway), and sometimes a knuckleduster is easier to carry into a restricted area than even a knife.

Then there’s the historical fact that all combatants were expected to have some skill in unarmed combat. Learning to brawl was a part of childhood, a fundamental that ought to be established before teaching skill in any weapon, and a common feature of melee combat even when weapons were involved. For all of these reasons, a character whose identity (read: career) involves combat ought to have some proficiency in the Melee (Brawling) skill. Most of the Talents applicable to knifefighting above, as well as the Dirty Fighter talent, make for good supplements. But, unless the character expects to do a lot of roughing people up without permanently injuring them, the Brawling skill is secondary to the armed-combat skills.

Conclusion

I hope this article has given some ideas of how the WFRP system captures the “feel” (to the extent that we can honestly reconstruct it) of medieval/early-modern combat without adhering to intricate and byzantine complexities. I hope also that it’s given you some solid build advice on choosing what kind of fighting techniques and equipment will best suit your character. On the other hand, there were a number of “masters of the art of defence” in the period, and a character whose ambitions lie in becoming one among them could be interesting to play and an effective member of a party. There are a number of ways such a character could go, moving between careers as necessary to represent different courses of study.

If I’ve missed something you see in the WFRP system, or if you’ve got other thoughts to contribute to mine above, I look forward to hearing from you!

Addendum – Shields and Melee (Parry)

It has been brought to my attention that the WFRP4e errata “clarifies” the use of shields. Despite the listing of shields as “basic” weapons, the errata states that a -20 penalty should be assessed to a character defending (or attacking) with a shield unless the Melee (Parry) skill is used, forcing a player to decide whether they want to trade AP for a -10 penalty on defense (as a shield adds its AP to all locations and the -20 penalty is partially offset by the +1 SL to defense tests granted by the “Defensive” quality) or whether they want to devote precious character resources to the Parry (Melee) skill. AP are nice, but not getting hit is better–especially in a system as deadly as WFRP!

From a mechanical standpoint, this makes very little sense. Instead of providing a solid (and marginally affordable) defense for characters less-skilled in combat it provides a nuanced and ultimately problematic choice. And, from a historical/practical perspective, this is not how shields work. I’ve never sparred with someone using a shield where the shield made them easier to hit. To my knowledge, none of my shield-wielding sparring partners were either ambidextrous or had any training in sword-and-dagger or rapier-and-dagger styles of fighting (I’m thinking here of situations that would translate to the mechanical reduction of the shield penalty described above under the WFRP rules). The use of a shield is instinctive and natural, while it may require training to fully master, it requires little or none to achieve basic proficiency. The nicest thing I can say about the errata is that it’s a headscratcher of a design choice.

Needless to say, if you give effect to the errata in adjudicating your game, almost all of the advice I’ve given above in the main article regarding shields goes out the window. I’m inclined to believe that that should not be the case. You are, of course, free to disagree.

So, how do we remedy this issue, should one be so inclined? The simplest thing to do is to just ignore the errata statement–there is no penalty to defending with a shield and it uses the Melee (Basic) skill. But, if you want to take a more moderated approach, remove the penalty and also remove the AP bonus or the + 1 SL to defense–I’d personally lean toward removing the former. Alternatively, you could remove the penalty but say that the Melee (Parry) skill must be used to get the additional +1 SL to defense tests. That would at least replace stick with carrot.

Addendum – Damage

Having now played a few sessions under the new rules, I must admit some shock at the particulars of attack and defense rolls. I had mistakenly taken for granted that attack and defense worked mostly like previous editions: i.e. (1) the attacker makes a test, (2) defender makes a test (which I viewed as a parry test in previous editions but now made automatic), and the attack fails if either the attacker fails at his roll or the defender succeeds at his. This is not the case. The current system has each side make their test and calculate their success/failure levels separately, with success levels represented by positive numbers and failure levels by negative. The difference between the two (assuming the difference is in the attacker’s favor) is added to damage dealt. In other words, the defender’s result is subtracted from the attacker’s result and, if the sum is a positive number, the attacker deals the sum as extra damage. The result is essentially the same as if we were using a roll-high system where each side rolls dice and adds applicable bonuses and then the defender’s result is subtracted from the attacker’s result to determine whether the attack was successful and, if so, how successful. It’s the fact that we’re using a roll-under system here that gives the approach some quirks. The foremost of these quirks is that the attacker can technically fail his roll and win–if the defender fails their roll by a greater number of levels. That situation “feels” odd but is mechanically effective.

Because the statistical effects of a mechanic and the “feel” of the mechanic do not always coincide (human perception and emotion being the odd thing that it is), player’s ought to be prepped for this potential result so that they are not blindsided by an attack they think has failed based on the attacker’s roll but that has not because of the sum of both rolls. Is that logical? Not really, but to effectively deal with another’s emotions, we must accept those emotions as they are rather than telling the person whether they “should” or “should not” feel that way. Be prepared.

At the same time, this system allows for some truly massive damage to be done in a single strike. That’s not necessarily a bug, you might well see it as a feature, especially given the reputation and intent that WFRP combat be lethal. I’m not particularly in favor of altering the “rules as written” in this case, but I do want to point this out so that individual tables can make sure the system is working for them and not vice versa.

If you don’t want your characters to be so susceptible to unlucky falls of the dice, you might consider altering this rule so that only the attacker’s positive success levels are added to attacks as additional damage. That makes characters slightly safer, but also drags out your fights, makes armor that much more effective, and probably has some additional effects I’m not thinking of, so proceed with caution.

Alternative Combat Systems in Cortex Prime, Part III: Holding the Line and Coordinated Actions

faithfictionfatherhood 1 Comment

For the previous part of this series, click here.

In this part of the series, I’m going offer two (sub)systems for handling particular types of combat situations; the first riffs off of the “Bloody Versus” while the second utilizes a nuanced form of “Narrative Combat.” Let’s get to it:

Timed Defensive Actions

“Mal: Zoe…are you here?
Zoe: Do the job, sir.
Mal: You hold. Hold till I’m back.”

–Serenity, 2004

This system can be used for situations where the characters are fighting a defensive battle against waves of attackers while keeping mechanics streamlined compared to character-by-character combat.

The GM needs two things at the start of the engagement (which can be set in adventure prep). The first is the dice pool used to represent the attacking force. Create this as you would any opposition, starting with a pair of difficulty dice representing the base quality of the attackers and adding dice for a Distinction and other applicable Traits. If the size of the attacking force warrants it, consider using the Scale rules, but bear in mind genre as well as the close narrative—if you’re playing a game involving special operations forces in an 80’s-style action movie, they’re probably expected to absolutely wade through the enemy and Scale would not be appropriate.

The second preparatory item is a mechanism for tracking the enemy’s fighting ability or the amount of time the PCs must hold out before help arrives. Depending on your damage system, the enemy force may have a die step that is whittled down, may have a Stress or Trauma die that is stepped up, or may have a damage track. If the conflict is a matter of holding out for time, you can set up a track or a “clock” in the style of Powered by the Apocalypse games.

Variant: Random Timing: If you want to add additional drama (and stress to your players), you can take a cue from miniature wargaming and have the conflict last for a random number of turns. To do this, decide upon a definite number of turns the conflict will last (e.g. “at least 3”). After the predetermined amount of time has run, roll a die at the end of each turn to determine if the event that would end the conflict (air support or reinforcements arrive, another team manages to destroy the attackers’ path to the characters, etc.) occurs. Use whatever die size you’d like and start with a chance of occurrence you feel comfortable with given the difficulty of the engagement for the characters. For example, you could start with a D6 and the conflict ends on a result of 6. For each time this die is rolled and does not meet the threshold, reduce the threshold by one. In the example above (d6 vs. 6), if the conflict doesn’t end on the first post-turn roll, in the second turn you roll d6 vs. 5, and so on.

In each turn, each player character rolls the appropriate pool against the Opposition Pool. For each PC who fails, that PC takes stress, trauma or injury depending on the damage system you’re using and how deadly your game is overall (I’d personally not recommend immediately applying damage that takes significant time to heal unless your setting has ways to circumvent that—magic or tech—or this defensive action takes place as part of the climax of the story where the stakes need to be turned all the way up.)

Assign the PCs their own track that represents their ability to hold their position. For each failure against the Opposition, mark a box along the track. When the track is full, the PCs are overrun by the enemy.

Variant: King of the Hill: With a slight modification, this system can be used to simulate a “king of the hill” scenario where both sides of the conflict are attempting to take and hold the same location. In this case, build a track with a center point, and have the character’s net successes or failure move the track in their favor or against their favor. When the track has filled on one group’s side, they have managed to seize the terrain with a strong enough position that the other group may not immediately attempt to take it back. If you want to limit the amount of time the conflict can last, remove a box from either side of the track every so many rounds as attrition and exhaustion take their tolls. Of course, one side or the other may take injuries enough that they abandon the field, and that’s okay, too.

One potential issue with this system is that it does not necessarily spotlight the actions of any particular PC, but this is relatively easy to overcome. You can plan certain events between the collective rolls in certain turns and give a particular player a chance to address that particular event before it affects the overall situation.

As an example: say you’re running a modern military campaign with special forces operators holding their position until requested air support is able to decisively end the confrontation. Between the collective rolls representing the characters’ defensive actions, let’s say a tank rolls up and begins to train its main gun on the characters’ position. The player character with the anti-tank weapon gets to take a shot to eliminate the newcomer before it becomes a problem. If this character’s attack roll is successful, the tank is destroyed and does not factor into the opposition in the next collective test. If the attack fails, add another die to the opposition pool representing the need to take cover from tank shells in addition to the rest of the assault. Obviously, the specifics of such opportunities should be drawn from the various abilities and foci of the characters to give each a time to shine, if not in the same engagement then over the course of the adventure.

If the characters have time to prepare for a this kind of defensive action, allow them to create Assets or Resources (i.e. expendable assets) for the conflict. Instead of applying damage to a character who fails an opposition test, the opposition pool’s success die could be used to eliminate or step down an Asset or Resource. In this way, not only do these Assets and Resources provide some benefit to the characters’ rolls, but some additional “armor” to keep characters in fighting shape for future conflicts. Whether an Asset or Resource applies to all PCs’ rolls in a turn or to only some is a judgment call for the GM to make based on context.

Variant: Defend Actor: This system can also be used to simulate situations in which some of the PCs are providing cover and defense for others to complete a non-combat action. Perhaps one or more of the characters needs to complete an ancient ritual while the rest of the party defends from attacking orcs. In this case, rather than keeping a track for the timing of the defensive action, create a track for the number of successes needed for the necessary task to be completed. For each character addressing the non-combat task, a success checks one box on the track and a heroic success checks two. If multiple characters could reasonably be assigned to either defense or the non-combat action, modify the defensive opposition pool (in conversation with the characters so that they can collectively decide where they want to put everyone) based on the number of defenders. You can use scale to do this, but the addition or removal of a die will probably be best for most situations.

If the characters are overrun, they must retreat from their position without completing the appointed task. If the task is successful, it should have ending the onslaught as a narrative consequence (in addition to the story-moving effects).

Coordinated Actions

“Either you’re part of the problem, or you’re part of the solution, or you’re just part of the landscape.”

-Sam, Ronin, 1998

This system is suited for those perfectly choreographed operations that depend on everyone completing their individual tasks at the right time so that the entire operation goes off without a hitch. These are your Mission Impossible montage ops, your small-unit actions to waylay a traveling vehicle and extract a VIP before making a getaway, your high-intensity but short action scenes where everyone has a particular role to play.

I used to love RPG sessions (particularly in Shadowrun) where the players would sort through maps and security schedules, lists of equipment and mission objectives to come up with an elaborate plan. But two things would either happen: (1) the plan needed so much detail that one of the players got tired of it all and decided to kick down a door and start shooting, or (2) playing out the elaborate plan took us three more sessions and everyone got tired of it. These rules are designed to condense the planning to the most exciting parts and play it out with the kind of speed and intensity usually reserved for film.

And really, it’s just an adaptation of the Narrative Combat rules from the previous post, with an added cue from the “Engagement Roll” of Blades in the Dark.

Here’s how we do it: the player characters have their objective. They’ve gathered the necessary intel and the equipment necessary to achieve the objective (perhaps setting up Assets for their various rolls). Then, the PC team plans the op, assigning discrete actions to each PC, like so:

It’s a snatch and grab on a moving vehicle with a target guarded by professionals. PC #1 is the driver, both approach and getaway. Number 2 is the bag man, tasked with extracting the target. Numbers 3 and 4 are shooters to provide cover for the extraction. PC #5 is a hacker whose task is to change streetlights to the advantage of the group, to jam any communications from the target and bodyguards, and to wipe any surveillance footage from city cameras. So, each character’s actions might be described by the following:

  • PC 5 modifies the street lights to box the target vehicle in.
  • PC 1 drives at high speed to block the target vehicle from escape.
  • PC 5 jams communications.
  • PCs 3 and 4 engage the bodyguards, suppressing them or eliminating them as necessary.
  • PC 2 engages the target and pacifies him.
  • PC 2 puts restraints on the target and gets him into the PC vehicle.
  • PCs 3 and 4 make a fighting retreat to the vehicle and get inside.
  • PC 1 drives off at high speed and uses evasive driving to lose any tails.
  • PC 5 wipes security footage to ensure that the PCs aren’t followed by the authorities.

As with Narrative Combat, each individual PC’s various actions are given sequential difficulty thresholds, and then each player rolls against their opposition (I think the best way to do this is for the opposition pools to be created in dialogue with the players, but the opposition roll results to be withheld until the GM narrates the results).

If all players meet all thresholds, the operation goes off without a hitch—the PCs have nabbed their target and taken him to their hideout without anyone being able to identify or follow them.

If any of the players fail, however, there are consequences. If there are only some minor failures—perhaps Player 3 fails his final threshold to return to the vehicle, then you can assign a Complication or injury and the operation remains successful as a whole. If a major threshold is missed (say PC 2 fails to pacify the target), or if there are multiple missed thresholds, then we use the collective rolls in the style of Blades in the Dark’s “engagement roll.”

If you’re not familiar with that mechanic, the engagement roll is a single roll intended to move past the boring bits of a heist and straight onto the excitement, its result sets the narrative positioning of the players as we jump in media res into their action by establishing whether things are going very well, very poorly, or middling at the time play of the heist begins.

In our situation, there’s a bit more complexity for the GM as she’s interpreting separate roles to create a cohesive narrative position for the transition into another type of mechanic to continue the action—this may be turn-by-turn combat, another alternative combat, or some sort of contest or conflict to represent the characters’ escape after things go wrong.

In the example above, with PC 2 failing to subdue the target, the GM might determine that the situation is thus as play moves out of the narrative combat system and into the alternative format: The target, though groggy from a blow to the head, is escaping on foot through a crowd of innocent bystanders. PC 2 is giving chase. PC 3 and 4’s successes mean that at least none of the bodyguards are following after PC 2, but now the rest of the group needs to get out of the middle of the road, evade detection, re-establish communications with PC 2 and find a way to meet up before the local authorities or reinforcements find PC 2 and/or the target first. Had the other PCs missed significant thresholds as well, additional complications would be added to the narrative as we “zoom in” to the aftermath of the botched operation.

Unlike the “generic” Narrative Combat system from the last post, there’s no need to establish consequences for each threshold of each roll in this particular use of the mechanic. The GM can wait until seeing all the rolls to weave together the results, assigning consequences only where necessary.

This system can be used for all sorts of character actions that are planned and prepared in advance. In addition to examples above, generic heists, ambushes, coordinated cons and other exploits can use this alternative to turn-by-turn resolution.

Conclusion

Two more tools for the toolkit in the bag. I think that both ideas are flexible and adaptable enough to accommodate a wide variety of narrative needs. Still, I’ll be adding to this series as I think of additional systems to streamline various types of action sequences or combats.

Again, I can’t stress enough that these are tools to be used alongside the conventional methods for resolving combats and conflicts based on what best fits any particular situation and the play style of the table.

Alternative Combat Systems in Cortex Prime, Part II: Bloody Versus and Narrative Combat

faithfictionfatherhood 2 Comments

For the first post in this series, click here.

As I mentioned in the first post in this series, we’re going to look at my adaptation of two systems borrowed from other writers: Luke Crane’s “Bloody Versus” from The Burning Wheel RPG and Peter Rudin-Burgess’ “One Roll Combat,” appearing in Lowborn: an Independent Grim & Perilous Fanzine for Zweihander RPG’s first issue.

Both systems intend to use a single roll to determine the end result of a combat, though the Bloody Versus (by my read, at least) is more focused than One Roll Combat. Let’s take a look at some adaptations for Cortex Prime based on the two.

Bloody Versus

Like most aspects of The Burning Wheel RPG, the core combat system in that game is relatively complex. I’m personally also not a fan of the “scripting” system for close combat, the conceit of which ignores the fact that a fighter makes choices about actions in combat based on cues from the other fighter(s), and not completely blind. But that’s besides the point since we’re looking at Bloody Versus.

Bloody Versus distills combat into a single opposed roll between the fighters. At first blush, a player may complain that this gives too little control over the outcome of a fight, but I’m not sure that this isn’t just a variation of the gambler’s fallacy; whether the statistics are compressed into a single roll or several, they’re still statistics about likelihood of winning, and it’s arguable that any Assets or other things set up for a single-roll combat have greater value than in a turn-by-turn combat, so it may all be a wash. Again, this is just one tool for your toolbox, and it may or may not work to the satisfaction of your table. But I’d judge it based on its narrative usefulness and whether you’ve got players who really want the nitty-gritty details of combat rather than on comparative statistics.

Here’s the issue with a Cortex Prime Bloody Versus: how do you set the stakes? How do you determine if a fight is a lethal one or just a good, old-fashioned donnybrook that results only in bruised faces and egos? Partially, this depends on how you’re handling damage and injury in your game—if it’s a light-hearted game then scaling should look different than if you’re playing gritty dark fantasy.

It should also be noted that the basic rules for Conflict and being Taken Out in a scene are essentially a Bloody Versus (or maybe a Bloodless Versus) depending on circumstances. There’s nothing to say that you can’t just bounce between those rules and turn-by-turn combat. But I’d like to offer something a little more substantial—that doesn’t necessarily preclude the occasional use of the “core” Taken Out rules.

We’ll do that by a bidding system. If you’re using the “Stress/Trauma” system from the Cortex Prime Handbook or some variations I’d described in the series on making Cortex Prime gritty, you’ll need to first determine whether the conflict is a lethal or non-lethal one.

With that determined, we’ll turn to the “Risk” die. Each character chooses a step for their Risk die—this is added to their Pool, but also becomes the Stress/Trauma received if they are on the losing end of the conflict, giving characters some added agency even in a one-roll combat.

Bear in mind that the use of the “Risk” die inverts the normal scheme for Effect Dice—each character is essentially setting what the Effect Die against them will be if they fail, while the selection by the opposing character sets the same. This focuses player agency on the risk rather than looking for the best possible Effect Die after the roll. For me, this seems narratively appropriate, with the added bonus that you won’t spend time looking for Effect Dice after the fact.

As a consequence, though, you’ll need to decide whether the ability to spend a PP to add a second Effect Die is available. For my own games, I’d rule that this expenditure may be used against any “average” opponent but not a PC, an Elite fighter or a prominent NPC. It’s plot armor, yes, but in a relatively unobstrusive way. If you want to go all out, by all means—so long as your players are all in agreement.

It should be noted, also, that this system, as written (and barring the use of PP for additional Effect Dice as described above), does not allow for a character to be killed outright by a Bloody Versus test. If you want to step up the relative danger, you can rule that a character automatically receives a Plot Point if any 1’s are rolled, but that each 1 rolled steps up the Stress/Trauma received by 1 step. This, of course, adds additional risk and unpredictability a part of a Bloody Versus test. And it reflects reality—even the best of warriors can make a mistake that leads to his demise, even against a less-skilled opponent. This rule also means that the winner may take some damage from the test, even if victorious. As with the above, this also matches reality and deepens the risk (and therefore drama and meaning) of even a Bloody Versus roll. On the other hand, you’re playing a game where a death necessarily means a particular part of the story (probably a part of the story important to at least one person) also dies. If you’re using a damage track (as in my posts on making Cortex Plus grittier), you might actually get some additional protection here, depending on the length of the track compared to the “six steps to death” you get under the “Stress and Trauma” rules of the Cortex Prime Handbook. Don’t forget that your system for Armor may effect the overall balance as well.

The Group Bloody Versus

The rule above works well for one-on-one combat, but perhaps less so for larger-scale engagements. Let’s look at some ways we can scale up.

The easiest method is to pair PCs with combatant NPCs. This is cleanest, of course, with an even number of PCs and enemies, but you can also use Mob rules (if appropriate based on the enemies) to further condense the fight.

Bloody Groups

If a one-to-one match-up isn’t possible, then we need to get a little more creative. As I mentioned in my series on swordplay for writers and gamers, it’s really only practical for about three combatants to face a single opponent at once; add more people in and the likelihood that allies injure one another increases exponentially.  This does not mean that you can’t put a group of five enemies on one PC, but you should bear in mind that such an arrangement probably means that two of those enemies are hanging back until there’s an opening for them to switch out with one of their fellows.

To use this method (which I’m calling Bloody Groups): first, group fights as you would for one-on-one fights, assigning additional combatants to each PC as necessary and as matches the positioning of the characters. Then, select a primary actor for the group. To that character’s pool, add the highest dice from two of his allies pools. Roll this against the PC’s pool. From the PC’s perspective: (1) on a failure, the PC takes damage per Bloody Versus; (2) on a success, the primary opponent takes damage per Bloody Versus; (3) on a heroic success, the primary opponent and his two allies all take damage per Bloody Versus. Here’s the kicker: any opponent fighting a PC, whether the primary actor or his two allies, adds any injury/Complication die to the PC’s pool, as any injured party gets in the way of his fellows, and it’s likely that, if there are additional troops standing by, they’ll switch out to allow the uninjured to continue the fight. For ease (and additional realism), establish the injury level at which enemies flee or are no longer combat effective; once they reach this level of injury, remove them from the fight (or, if it’s that kind of game, potentially allow the PC’s the opportunity to kill the fleeing combatant as he attempts to withdraw).

Bloody Skirmish

We can zoom out even further, as necessary, keeping the core of the Bloody Versus system. For an all-out melee where we don’t necessarily need to track each exchange individually, we can use what I’m going to call the Bloody Skirmish system.

To begin, establish a base difficulty for the group opposing the characters—this should be based on the skill of the combatants, not their number. Add dice to the pool for group Distinctions, Assets or other Traits in play as you see fit. Add a Risk die to determine how aggressively the group fights. Lastly, if you’re using a track for damage rather than the Stress/Trauma system, determine the length of the track for this group and when the group suffers a Consequence die due to losses.

Each PC rolls a Bloody Versus against the single opposition pool, applying damage to the opposition as a group or to PCs individually.

If the group greatly outnumbers the PCs (and your genre and narrative fit with this approach), use the Scale rules (Cortex Prime Handbook, pp. 99-100). This should make players reconsider plunging headlong into overwhelming odds (but there’s no accounting for what certain players will do, never tell them the odds, damn the torpedoes and all that).

Narrative Combat

And now we come to my adaptation of Peter Rudin-Burgess’ “One Roll Combat” system, which I’m going to call “Narrative Combat.”

Where Bloody Versus handles conflicts that are focused on the violence itself, the Narrative Combat system is better suited for quickly handling situations where combat is incidental (supplemental?) to the PC’s goals.

The system works like this: after the situation is defined and everyone understands who and what is in play, each player sets out a set of three to five actions (the GM should specify the exact number) that the player wants to accomplish. These actions must be in logical order and in the order in which the player wants to accomplish them. Players and GM should converse to clarify intent, methodology and likely effects for each action individually and as a whole.

Once there’s agreement on these points for a player and PC, the GM establishes difficulty thresholds, with the lowest threshold representing success in the first action, the second threshold set a certain distance from the first and representing success or failure in the second action, etc. As Rudin-Burgess is writing for a d100 system, these thresholds are linear and fixed; making for an easy port if you’re using Static Difficulty (Cortex Prime Handbook, p. 25). The first action might be at difficulty 8, the second at 10 and the third at 13 depending on the nature and difficulty of each action.

Alongside each threshold, the GM establishes a consequence for failure. This may be Stress or Trauma (or some other damage inflicted depending on your system), a Complication, an unintended consequence or change in the scene, etc.

Then the player rolls his assembled pool (again the GM and player should collaborate to determine the most applicable Traits to include in the pool based on the overall sweep of the actions declared). For each threshold met or exceeded, that declared action is successful. For each failed, the associated consequence is applied.

When all players have rolled, the combination of successes and failures is used by the GM to narrate the overall result of the conflict scene. It’s an efficient and creative system.

If you’re using opposition dice pools as per the usual in Cortex Prime, then some modification of Rudin-Burgess’ system is necessary over a simple scaling of difficulty thresholds. As this is true for the majority of my Cortex games, I’m doing the following for my Narrative Combat System:

We start with a base difficulty of two dice for the first action. If there are any other applicable Traits for the pool, those are added in. This initial pool is rolled and establishes the first difficulty threshold (per the usual of taking the two highest rolling results and adding them together). For each additional action, a die of an appropriate step is assigned; it’s result is added to the total from the initial roll, so three dice are totaled for the threshold of the second action, four are totaled for the third, etc.

For this to work, the opposition pool should stick to lower-stepped dice at each step: unless there’s significant justification for doing so, I’d stick mostly to d6s and the occasional d8. If this is feels too imprecise for you, add some techniques from Powered by the Apocalypse games: instead of modifying the difficulty itself to suit narrative positioning, scale the consequences to suit the difficulty (your GM “moves” as it were).

If you want to make things even more efficient, have all players roll against the same opposition pool. If their plans are more divergent, it may be more appropriate to use different opposition pools.

Conclusion

So, there you have it: a system (and variations on a theme) for condensed handling of conflicts in which violence is the focus and a system for conflicts in which violence is much more of a means to an end than an end in itself. You could, in theory, stop reading this series now and have two tools that could cover the vast majority of situations for your game (tweaked only slightly for genre and power level) without having to resort to man-to-man, turn-by-turn combat except where you want to.

But I hope you won’t stop here. In the next post, I’m going to provide some systems tailored to specific types of conflicts/combats, starting with a system for holding your ground against assault.

For the next post in the series, click here.

Alternative Combat Systems in Cortex Prime Part I: The Rationale

faithfictionfatherhood 3 Comments

Combat can be the most exciting—or the most excruciating—part of a gaming session. It’s easy to get bogged down in the minutiae: checking particular rules (and exceptions), contemplating the potential results of every available action like you’re Deep Blue, clarifying who’s where, what conditions are in effect and what happened on previous actions.

We’ve all been there. The active player is taking minutes to determine his turn while everyone else is playing on their phone. The combat itself is necessarily a matter of slow attrition punctuated only rarely by decisive blows. Rinse and repeat, potentially for hours. I don’t want to say that the conventional style of RPG combat, with its sequential individual turns and actions for each character involved doesn’t work; it can result in exciting and enjoyable combats. But if we take the example of D&D in particular, as the originator and exemplar of this system, the smorgasbord of titles both amateur and professional available on DriveThruRPG.com to “make combat more exciting” indicates that there are many cases where the system doesn’t work as well as we’d like.

And this figures, given that D&D (and therefore RPGs in general) developed out of wargaming. The turn-by-turn system is an artifact of, and beholden to, the miniatures wargame.

Some Alternatives

There are a number of ways that games or homebrews have tried to address this, with varying degrees of success. Making a game deadlier necessarily condenses combat and makes clever tactics (and/or use of rules) even more important.

The Riddle of Steel is one of my favorite examples of this. Its visceral combat system attempts to closely model the actual mechanics demonstrated in the fight manuals of the medieval and Renaissance periods. It does so quite successfully. When I ran games in this system I was simultaneously a study group leader for the Association for Renaissance Martial Arts (ARMA); I’d spend hours as a “Session -1” with wooden weapons showing those players who weren’t in ARMA with me what the techniques in TROS actually looked like. But the system is not without its faults, either: it had no significant guidance for an overall initiative system, leaving players to judgment calls for a number of situations commonly addressed in other games. To me, it’s a prime example that no RPG combat system can do everything, even if it does some things exceptionally well.

Knowing that, why do we expect a single system to effectively cover all combat situations equally well? The result, as with D&D, is that we have a combat system on top of which we add the occasional non-combat goal for flavor and variety. But shouldn’t it be the other way around? Shouldn’t we have systems, plural, each focused on different types of situation. Some combats are about injuring or killing the enemy, yes, but many resort to violence in service of a goal that is, ultimately separate from the injuries inflicted on the opposition. This is true even of military operations. As commonly as they are deployed simply to destroy the enemy, they are directed to capture and hold valuable locations, to destroy enemy resources, to drive the enemy from a particular area, to infiltrate an area to perform reconnaissance and surveillance—or to provide forward observation for targeting airborne or artillery-based weapons. In many of these cases, the enemy will be engaged only to the extent necessary to accomplish the mission, because simple attrition is not a great way to win a war (as the American Civil War and, especially, World War I demonstrated).

The Torchbearer RPG keeps this in mind, at least on an abstract level, where the various “intents” (such as Capture, Drive Off, Kill) in a conflict determine the character traits used for rolls.

“Powered by the Apocalypse” systems ultimately treat combat no differently from the rest of the rules, except that consequences and GM “moves” may more frequently cause Harm to the characters. There is no set initiative system, and each “combat test” remains more about the development of the narrative than a tactical mini-game. It leaves much flexibility for how the GM interprets player cleverness, creativity and innovation without needing rules to explicitly do this. On the other hand, for those who are more Gamer-oriented (if you subscribe to Ron Edwards GNS Theory) may find this less than satisfactory.

This Series

This series will present a set of systems for Cortex Prime for particular types of combats, not as an obviation of or replacement for the standard “man-to-man” general RPG combat approach, which has its appropriate uses, but to work together with that system based on the narrative needs of a particular game and the desires for depth of tactics for players.

Elsewhere on the blog, I’ve provided some rules for streamlined military/modern combat engagements. Those will not be repeated in this series, but could be added to the list of options provided here if so desired.

Some of these systems will be taken from the ideas and creations of other writers (and credit will be given where due) and adapted to Cortex Prime, but most of them will be my own creations.

But let us begin with some theory about the role and nature of combat in RPGs.

What is War For? What is it Made of?

Combat is an essential feature of most (but certainly not all) RPGs, whether or not they fall into the “traditional” camp. There are, I think, a few reasons that this is the case. Let’s look:

First, there is the simple fact that many people play roleplaying games because they are a way to experience adventure and danger in a safe way. Most people do not want to be punched in the face, much less risk their lives without extreme need. But they do want the thrill of such stakes, which is why video games, combat sports (whether martial arts, paintball and airsoft or competition shooting), action movies and combat in RPGs are popular.

Second, satisfying narrative requires conflict. Armed (or otherwise) violent confrontation is conflict in its barest sense; it necessarily poses questions to drive a story: Will the characters prevail? Will they survive?

Third, as Louis XIV had cast on his canons (albeit in Latin) and as Joe Abercrombie used as the title of one of his novels, violence is “the last argument of kings.” Or, if we’d rather resort to Heinlein, who has his Mr. Dubois the teacher of “moral” philosophy in Starship Troopers remark to a student who tells him the “violence doesn’t solve anything,”

“I’m sure the city fathers of Carthage would be glad to know that….Violence, naked force, has settled more issues in history than has any other factor, and the contrary opinion is wishful thinking at its worst.”

When two sides refuse to compromise, and a situation must be resolved, violence may sometimes be the only available course of action. I don’t think I enjoy that fact as much as Heinlein did, but I agree that it is sometimes an existential truth we must face. In the adventures of our heroes in particular, violence may be the logical (narrative) result when all other means fail.

Fourth, some gamers really enjoy the challenge of combat, of making tactical decisions and outmaneuvering the enemy. And that’s as good a reason as any.

By way of transition from what combat is for into what it should do, the astute GM should bear in mind that that means that combat should be actually challenging—otherwise you’re depriving your players of the satisfaction of victory. The good GM should be a student of war in all its forms (this does not require one to be a practitioner of war, which is perhaps another matter altogether, discussed on other portions of the blog). So, number one—combat is another type of puzzle, problem and challenge for the players to address, and one with stakes higher than many others they’ll face.

As Apocalypse games make plain, combat should drive the story forward. This does not mean that every combat need be decisive; a battle in which the two sides fight to a standstill and must withdraw heightens the conflict and must necessarily make the players question whether they are powerful enough to prevail by force and whether another approach might be preferred.

Combat, when done well and used well, at least, provides options for high drama. What will the character’s fight for? What won’t they fight for? What is significant enough to a character that she is willing to kill (or die) for it? The cliché that you truly learn who a person is by seeing them in a fight is true when it comes to crafted (even when collaborative) narrative—combat need not be just a matter of mechanics; it can become an opportunity for deep roleplaying.

As much, combat is a useful tool for pacing a Roleplaying Game. There is, of course, the old gaming adage that if things slow down too much, have the bad guys suddenly show up to kick things back into gear. But it goes far beyond that. There’s not room to go into the full details of this subject (which can easily be a blog series—or book—in its own right), but good narrative swings back and forth between high-intensity scenes and low intensity scenes. This gives the audience both excitement and pauses to reflect on what the occurrences of the “high points” mean for the narrative moving forward. Think about the Fellowship in Khazad-Dȗm—they flee from goblins and Gandalf confronts the Balrog in a high-intensity scene. The scene that follows the rest of the Fellowship’s escape slows down so that the characters can reflect on the loss of their erstwhile leader and what it means for their quest.

Here’s the issue, though: when combat slows to a crawl as you play out each second by second, it fails to provide the high-intensity sort of scene that it should. When a low-intensity scene follows, as it naturally should, the energy at the table remains low and everyone loses immersion and attention. This is fine if the players enjoy intricate combat for its own sake, but it’s been my experience that I only have one or two of the players in my group for whom the gaming or simulationist approaches to combat are a particular draw.

Conclusion

I think all of this gives us a rubric by which to judge the utility and value of some alternative combat systems. Any system that replaces turn-by-turn combat must: (1) make at least enough logical sense to be acceptable to gamers and simulationists, given the caveat that they must necessarily be more abstract than turn-by-turn systems, (2) following the first point, be at least somewhat satisfying to use, (3) move the story forward in a meaningful way, regardless of specific outcome, (4) allow for meaningful choices, which in turn allows for drama and character development, (5) have stakes high enough to match a “standard” combat system, sometimes softened to account for less control on the part of the players as to outcome, (6) must provide a useful tool for maintaining pacing.

The flexibility of the Cortex Prime system allows us to create a number of different approaches to combat, as you’ll see.

What’s Next?

In the first substantive post in the series, we’ll look at two general systems I’m adapting from other games: Luke Crane’s “Bloody Versus” from The Burning Wheel RPG and Peter Rudin-Burgess’ “One Roll Combat,” a brilliant article written for the Zweihander roleplaying game and appearing in Lowborn: an Independent Grim & Perilous Fanzine for Zweihander RPG’s first issue.

After that, we’ll look at some systems for particular types of engagements created by yours truly.

For the next post in this series, click here.

Augmentation in Cortex Prime

faithfictionfatherhood Leave a comment

The following is a system for handling (para)human augmentation, primarily for cyberpunk and other sci-fi settings, but adaptable to steampunk, fantasy settings or any other setting aspect involving implantation and supplementation of natural body systems to achieve spectacular effects.

While the base Cortex Prime Abilities or Powers systems could be skinned to cover the same material, this system attempts to unify this mechanical aspect of Cortex Prime under its own subsystem to both accentuate this component of setting and to provide for a more narratively cogent method of addressing (para)human augmentation.

Using Talents for Augmentation

Rather than using a Trait Set, as the mod below does, to represent Augmentations, you could simply create a list of Talent SFX, with each Talent representing a particular system. This might be the preferred system where augmentations are present in the setting but not a central feature (for instance, Star Wars has cybernetics, but they are typically background dressing).

Grit and Power Levels

At the simplest, these systems can be made a Trait set available to all characters, with a set number of dice to assign between specific traits. This works especially well with cyberpunk settings that have no mystical or magical aspects to balance against.

The relative power of each augmentation system can be adjusted narratively. For instance, does a d8 in Strength systems mean that a character can punch through concrete? Throw a car? Or simply that the character has a level of strength on par with world-class body-builders? Does a character with Cognition d8 have intellectual skills on par with natural geniuses (perhaps a more complex designation than once thought given developing neuroscience) or superhuman skills of calculation and analysis? Of course, the step of the system’s die can be factored in as well—dice at steps d10 or lower may be within the realm of natural human ability, while dice at d12 represent augmentation beyond natural human potential.

These narrative factors can be combined with mechanical effects to further define the relative power of available augmentations. If you are using rules like a Limited Dice Pool, you could have an Augmentation die not apply toward the limit—this will accentuate that augmentation really does allow someone to achieve beyond normal standards. If you’re also using a track for Stress and/or Trauma, you could also allow a player to voluntarily take a point of Stress or Trauma to add a third die (perhaps specifically the Augmentation die) to the result rather than spending a Plot Point to do so. For a middle road, allow the expenditure of a Stress/Trauma “point” to have the Augmentation die not count toward the Dice Pool Limit. I’d map this as an SFX that automatically applies to each System, much like the “Use a d4” mechanic for Distinctions.

These options may work especially well in settings where human augmentation is an important aspect of genre—such as cyberpunk or certain science-fiction. As a more specific example, this might work especially well in a setting like Eclipse Phase, where characters can “resleeve” into different bodies and you want to accentuate the importance of body selection.

The System Itself

The system itself is relatively simple. Rather than seemingly infinitesimally granular selections of particular upgrades and augments, this mod looks at the sum total, classifying the Traits in the Augmentation category as “systems” that represent the overall effect of upgrades. The systems I would recommend using are: Athletics, Charisma, Cognition, Perception, Reflex, Resilience, Stealth.

Whether you use the categories I’ve designated or substitute your own, you should give a general description of the system that explains what sorts of capabilities a person with that System has as a guide to when the die from the System might apply (or when possession of the system grants narrative “permissions” that may not be reflected in mechanics but in the sorts of things the character can do.

Specialized systems providing more discrete and specialized functions can be mapped as SFX. You may consider giving characters a certain number of SFX for free at each dice step or provide that certain SFX are automatically gained at certain dice steps.

If you’re using other Traits that have SFX, or if you’re using Talents, you’ll want to carefully consider whether your choices will lead to “SFX bloat” that will complicate gameplay inordinately over the value they provide. Additionally, you’ll want to think about just how much you want to accentuate Augmentations versus other Trait sets.

If you choose not to use SFX, then you might provide short narrative descriptions of the kinds of capabilities a System has at each die step.

I’ve provided sample write-ups and SFX for my Systems below. Given the length of the article (and constraints on my time), I’ve only included a few sample SFX in each System. When I am able, I’ll supplement those SFX in a subsequent post.

Systems Descriptions

Athletics: Athletics Augs enhance the strength, flexibility and endurance of a character (but not their reaction times, which are enhanced by Reflex Systems). These are the most-commonly thought-of augs for the average person, because they are at once those most obvious in action and those with the most directly frightening consequences.

  • Oh Yeah!: Spend a PP to smash through a wall, even if made of brick or stone.
  • Optimized Cardiovascular System: Spend 1PP to step up or double any Endurance Augs when taking an action. If the action fails, shutdown Athletics Augs. Recover by activating an opportunity in a Bridge scene.
  • Hyper-oxygenated Blood: The die step of any Complication of Difficulty die accounting for fatigue from physical exertion must exceed the Perception Augs die or the character disregards it. For any such Complication that does apply to the character, step it down by one step.

Charisma: Charisma Augs enhance a person’s social capabilities through a number of means. This may include pheromones or other chemical signals, analytical systems providing feedback on observed body language, voice modification for a more mellifluous sound, etc.

  • Empathic Analysis: When including Charisma Augs in a social Reaction, double or step up Charisma Augs. Pay 1 PP to do both.
  • Mood Stabilizer: Spend 1PP to ignore penalties from social or mental Stress or Trauma, or Complications, for a Test.
  • Halo Effect: Spend 1 PP to step up or double Charisma Augs on a test to persuade others. If the action fails, shut down Charisma Augs and recover by activating an Opportunity in a Bridge scene.

Cognition: This System covers augmentations that enhance the computing or analytical power of the human brain. Subsystems tend to enhance object identification, pattern analysis, sensory interpretation, creativity and intellect: human methodologies for competing with the power of artificial intelligence (whether or not that means “sentient and conscious” artificial intelligence or the complicated computing algorithms already in use today).

  • Multitasking: Split Cognition Augs into two dice at one step down or into three dice at two steps down.
  • Flow State: Step up or double Cognition Augs for one action, then step back to two dice at one step down. Recover by activating an Opportunity during a Bridge scene.
  • Probability Analyzer: Spend 1 PP to add Cognition Augs (or step up by one if already in your pool) and reroll all dice on a Reaction.
  • Efficiency Optimizer: Use two or more Systems dice in a single dice pool, reduce each System die for one step for each Systems die added beyond the first.
  • Overclock: Step up or double Cognition Augs for a scene, or spend 1PP to do both. While active, take Mental stress equal to the step up the second-highest-rolling die.

Perception: This System represents augmentations that heighten or expand the sensory perceptions of the individual—the ability to see in other parts of the light spectrum, to filter certain sounds and focus on others, or even the addition of senses that (para)humans don’t normally have—a snake’s heat-sensing pits or a bat’s sonar.

Depending upon the nature of the System, a character with a Perception die may have an image link that can display a sort of Heads-Up Display (HUD), along with video, text and images, directly into the view of the character. They may also have the ability to record photos or videos.

  • Digital Zoom: The die step of any Complication or Difficulty die accounting for distance from the visual must exceed the Perception Augs die or the character disregards it. For any such Complication that does apply to the character, step it down by one step.
  • Enhanced Resolution: In a pool containing Perception Augs, replace two dice of equal steps with one die of +1 step.
  • Flash Suppression: The die step of any Complication of Difficulty die accounting for blinding lights must exceed the Perception Augs die or the character disregards it. For any such Complication that does apply to the character, step it down by one step.
  • Enhanced Spectrum Targeting: Add a d6 to your dice pool for an attack against an opponent at near range you cannot see and step back your highest die by one step.
  • Threat Identification: Spend 1PP to add Perception Augs to your pool (or step up by 1 if already in your pool) and reroll all dice on a Reaction.
  • Multispectrum Vision: The die step of any Complication or Difficulty die accounting for poor visibility must exceed the Perception Augs die or the character disregards it. For any such Complication that does apply to the character, step it down by one step.

Reflex: Reflex augs reduce reaction times through increased sensory-processing speed, reduced muscle-response times, and added speed and power for transmissions through the nervous system.

  • Enhanced Fine Motor Control: Spend 1PP to ignore Complication dice applicable to a test involving dexterity.
  • Reaction Enhancement: Step up or double Reflex Augs for a test involving Initiative. Spend 1 PP to do both.
  • Synaptic Acceleration: If a pool includes Reflex Augs, you may replace two dice of an equal size with one die one step higher.

Resilience: Where Athletics Augs cover enhancements to physical endurance, Resilience Augs models systems intended to protect the body from harm, whether from toxins, disease, environmental hazards, or direct physical injury.

  • Subdermal Nanoweave: Your Resilience Aug die (or its equivalent step depending on your damage system) functions as armor against physical attacks.
  • Toxin Filters: In a test to resist toxins, whether airborne, injected, consumed, or otherwise, double or step up Resilience Augs. Spend 1 PP to do both.

Stealth: Stealth systems conceal the user from detection or from identification. This may range from lubrication of joints and the strengthening of muscles and tendons to allow for quieter movement to complex augmentations that allow the user to change the color of their skin, the length of their hair and the shape of their facial features, with various specialized components to provide various kinds of stealth.

Because of the wide variety of possible stealth functions, use of SFX or a solid description of capabilities at various dice steps is essential for this System. For example, if not using SFX: at d6, the System’s focus should be on the avoidance of detection by the senses. At d8, this expands into defenses against sensor detection and perhaps “active camouflage.” At d10, shaping of physical features and appearance becomes possible.

  • Active Camouflage: Spend 1PP to double Stealth Augs against an attempt to detect you visually or by light-spectrum-based sensors.
  • Impersonation Protocols: Step up double Stealth Augs for one scene to mimic a person for whom you have detail information about appearance, physical attributes, habits, vital signs and behaviors. Then, step down Stealth Augs by 1 step. Recover after a scene in which you do not use Stealth Augs.

The Limits of Ascension

You may want to put Limits on these Systems, either to reinforce how Augmentations work in your setting or as a sort of mechanical balance against the SFX (especially if some or all are free) attached to various systems.

Some RPGs separate out different types of augmentation—genetic engineering from cyberware or organic augmentations, for instance. If that is the case in your setting, you may want to use different Limits to represent the specific nature of the augmentations that comprise a particular System. For additional complexity, you could restrict certain SFX to certain classes of augmentation, ruling that a character must choose one Limit when first selecting that System and that, if the character wants to add an SFX that has a Limit related to a different class of augmentation, the character must have both applicable Limits added to the System. So for instance, if a character started with a “wetware”-based System, they would have the corresponding Limit. If that character’s player wanted to add a “cyberware”-based SFX, the Limit related to cyberware would have to be added to the System as well.

For a simpler approach, you could simply assign set Limits to each System, potentially using one or more Limits to offset the automatically-granted SFX associated with the System.

Digression 1
Again, the more complexity you put in this system, the more you need to think about whether the benefit of the added complexity is really worth it. As a concrete example, I started a Cortex Plus/Prime conversion for Shadowrun some time back on this blog (to which I’ll likely return). To capture the feel of Shadowrun, at least the way I’ve approached it, adds a good deal of complexity to the Cortex Prime system, taking it somewhat away from what it was intended to be. Does it end up as complex as Shadowrun? No, but it is substantially more complex than Cortex Prime, and, at that point, it may be worth thinking about whether this is the right system for a conversion, or whether so much of the complexity needs be converted into your Cortex version. With Shadowrun in particular, there already exists a simplified version of the ruleset (called Shadowrun Anarchy) that may fit the bill for you. For me, that system swung the pendulum far too far and ended up with a system that feels inadequate to account for enough complexity to capture the feel of the Shadowrun setting in a streamlined manner.

Digression 2
As best I can tell, in reality, it looks like, by the time human augmentation because truly available, augments will combine both biological and technological aspects of design into a unified whole, making the sorts of distinctions Shadowrun cares about in its treatment of Augmentation a mostly moot point. Of course, there’s a good argument that humans will resort to wearable devices for augmentation rather than surgical intervention (except in the case of prosthetics, injury or lack of natural function, of course), but that’s not quite as fun to imagine, is it? If that suits, though, this mod could be adapted to different Signature Assets to represent that reality.

With those (admittedly characteristic) digressions taken care of, here are some discussions of potential Limits to use with this mod.

Essence
Since I’ve already opened the Shadowrun can of worms, let’s start here. There are a few ways to handle Essence as a Limit. The simplest is to add the highest System die to the opposition pool of someone trying to use beneficial magic on the augmented character. For a harsher scenario, add each Augmentation die, or, like Dehumanization below, create a single Complication die based on the steps of the System dice.

Dehumanization
If you want to incorporate the idea of lost humanity as well (something I’m personally not a fan of in RPG treatments of augmentation—lookin’ at you Cyberpunk and Shadowrun), then use one of the following: (1) When the first System die reaches d10, the character gains a permanent Complication die at d6 that is added to social tests. For each additional System at D10 or increase to a d12, step up the Complication die. If the Complication die exceeds d12, the character becomes a cyberzombie. Adjust the die step at which the Complication comes into play or is stepped up to suit; or (2) Simply add any System die at d12 to the opposition on social tests.

Hackable
A few options here:

  • A character with this Limit may have Stress or Trauma to both physical and mental tracks caused by hacking attack;
  • Hacking may be used against this character to create Complications or Conditions;
  • A System with this Limit may be stepped down like an Asset or Complication through the use of hacking. You’ll need to choose a method by which the die is recovered;
  • If you have a specific Stress/Trauma track for Augmentations or being hacked, you could tie steps down or shutdown of Systems dice to that; or
  • Some combination of the above.

Complex Biology
Add the highest System die to the opposition against tests to recover or heal from damage through medical intervention.

EMP Vulnerability
This could likewise be modeled several ways:

  • EMP devices that affect this character can apply Complications or Conditions;
  • A System with this Limit may be stepped down like an Asset or Complication through exposure to electromagnetic interference. You’ll need to choose a method by which the die is recovered;
  • When exposed to electromagnetic interference, shut down this System to gain 1 PP;
  • Some combination of the above.

Conscious Activation
As written.

Glitchy/Prototype/Bleeding Edge
Convert the System die to a Complication for a roll to gain 1 PP.

Systems Stress

You may want to consider giving characters a Systems Stress Track, particularly if using rules for Stress/Trauma Tracks like those I mentioned in my series on adding grit to Cortex Prime. If you do, a few additional options may open up to you. For one, you get a way to track the condition of Systems, whether they’re affected by overuse, by hacking, by electromagnetic interference, or some other factor. If the Systems Stress Track is filled, you lose access to Systems dice. You can set up Complication/Condition dice for various stages along the Track and/or step down all Systems dice at various points along the Track, depending on the effects you want to achieve. As an additional benefit, you can allow characters to “push” their augmentations, activating associated SFX, by adding a point of Stress to the Systems Stress Track in lieu of paying a PP. In such a case, you can allow a PP to be spent as usual, or, if you want a “push your luck” sort of system with augmentations, you can require Systems Stress to be used to activate augmentation SFX. If you choose this path, you’ll have to determine how Systems Stress is recovered.

Conclusion

So there you have it, a system for handling (para)human augmentation in the Cortex System without resorting to the Powers/Abilities given in the core game. I’ve tried to include enough options in my write-up to let you fine-tune this system to suit your particular setting. I’d love to hear your thoughts on all of this, see the additional SFX you add to your lists, and generally hear about how the system works out for you if you use it!

Back to the Mud: Putting some Grit in Cortex Prime, Part II: General Difficulties

faithfictionfatherhood Leave a comment

In Part I of this series, I offered some methods for modifying the core rules options in the Cortex Prime Handbook for damage and injuries to get a grittier feel. In this follow-up, I’m going to talk about some hacks for difficulty in general, because “grit” is about far more than death and dying.

As I mentioned before, Cortex Prime favors generally capable characters from the get-go and that I believe that making characters inept is the wrong way to add grit to mechanics. So we’re not going to change characters; we’re going to look at some alternative approaches to assembling pools, calculating results, and determining effects.

As a note of acknowledgment, the ideas about limiting the dice pool and the use of “Forced Dice” came from a friend of mine during a conversation we were having about adapting Cortex Prime to serve as a ruleset for my Avar Narn setting. If he gives permission, I’ll update this article to give him credit by name.

No Effect Dice, Expanded
The Cortex Prime Handbook offers a mod that removes Effect Dice from the mechanics. Unfortunately, the mod as described gives no replacement method for full degrees of effect, simply replacing all Effect Dice (where they would be used) with a d6, stepped up for a heroic success. There are plenty of games that offer varied degrees of success based on a single roll, and we could also point back to Rob Donoghue’s note about five steps stacking with the five die sizes of Cortex Prime to fill in the gap.

Rather than dividing results into “normal” successes and “heroic” successes, we can simply establish four or five sections for a granular map to convert a roll total to an Effect Die where it’s useful or necessary to do so. If you want to skip d4 Effect Dice, then you’ll have four success categories, five if you include them. I think there’s a good argument to be made for starting with d6 as the “basic” success level for mechanical ease of use, as d4’s are only supposed to be used once and then removed. On the other hand, including more d4s in dice pools increases the likelihood of Complications and Opportunities (and may further reinforce the gritty nature of a system when basic results provide only fleeting advantages).

An additional benefit for mapping mechanics to grit is that higher Effect Dice are reached less often, but this can cut both ways. It might turn many conflicts into more attrition-based slogs than the faster-moving action of the core system. A statistical analysis of the core rules for Effect Dice against the “Degree of Success” conversion described herein would need to account for many variables–average pool sizes, relative frequency of the various dice types being in pools, etc. I have neither the training nor inclination to perform such analysis for my own end systems in Cortex, much less those you might formulate for your own games. There may need to be some trial and error here.

If you’re using one of the “Damage Track” mods from Part I of this series, you can address some of this with the length of the damage track. If using weapons that add to damage inflicted, you can further tune whether weapon selection or skill rolls are most important in determining the damage of an attack. Of course, if you’re willing to make things another step of fiddly, you could have particular weapons set the thresholds between Effect Dice results (or damage inflicted) for an interesting combination of weapon and skill as factor in end result.

Personally, I’d likely skip the d4 result, starting a “basic” result at the equivalent to a d6 Effect Die, with the step of the die increased according to the following degrees: “beating” the other roll by 1 or 2 is a d6 equivalent, by 3 or 4 is a d8 equivalent, by 5 or 6 is a d10 equivalent, and by 7+ is a d12 equivalent. If you don’t mind more complexity (and more “average” results on the whole), you could increase the range of each successive step (i.e. 1 or 2 would be d6, 3-5 would be d8, 6-9 would be d10, and 10+ would be d12).

In the core rules for Conflict (or the Action-Based Resolution mod), the advantage goes to the acting character, because the reacting character must beat the acting character’s result to be successful. Many “gritty” roleplaying systems (or at least RPG systems attempting to fall into the amorphous category of “gritty”), have ties go to the defender. It’s worth considering whether to use that approach or to keep the core Cortex approach that the acting character has the advantage. I don’t think there’s a right answer here, but because this ruling applies when things are down to the wire, I expect your players will recognize the difference, even if only intuitively.

Another effect of this system is that certain “dice tricks” available with the use of Plot Points or SFX collapse into one another. For instance, the ability the add a third die to your total would now both increase your chance of success and your degree of success (whereas, under the normal rules, adding a third die to your total would make that die unavailable to be used as an Effect Die).

Limited Dice Pools
Under the core Cortex Prime rules, a character may add one die to their pool from each applicable Trait category (with some additional judgment necessary for Signature Assets and similar Traits, where having a rating within that general Trait category does not mean that it will be universally applicable). But what if they can’t? What if a character can only use a maximum of four dice in a dice pool, even if there are five Traits that might contribute a die? If this only applies to characters (players or NPCs) but not opposition rolls from other sources, this allows a great deal more fine tuning of difficulties (again, with the complexity of statistics for the Cortex Prime system, the exact steps of granularity added by such a measure is not exactly known, but we can generally surmise the difference between adding an additional d10 versus adding 2d6 to the pool–assuming we’re still only talking about using the two highest-rolling dice for the result).

To best jibe with the way the Cortex Prime system works, dice that fall outside of the character’s innate Traits should not apply to the limit–essentially, an Asset (other than a Signature Asset), an opposing character’s Complication or Condition, etc.–don’t count.

This idea also creates a new space for Traits, SFX, or Plot Point expenditures that break the rule. The ability to spend a Plot Point to add a die to the pool over the normal limit of dice should, of course, be added. Certain Trait sets, if they apply, may not count toward the dice limit for the pool–this is a great way to put added emphasis on a particular Trait set–accentuating Signature Assets, Powers, or Abilities, for instance. For a more limited version of the preceding, consider an SFX with a non-Plot-Point cost as permission to add the die to the pool regardless of the limit. I’ll be working on a post with an approach to modeling human augmentation in Cortex Prime in the near future; it will include some examples of employing these ideas for breaking the Limited Pool Rule.

This mod, I believe, also adds additional power to having higher-stepped dice in a rating. Not only does a d12 increase the total result you might reach, but it brings up the average result as well–something that you can do by adding multiple dice of a lower step when there is no limit on the pool.

“Forced Dice”
This mod works only with the Limited Pool mod above, and it’s something that I’m still wrapping my head around, so it will likely be expanded in a future post. For now, I’m just going to mention it. The idea, in general, is to create situations in which a character must accept a d4 in their (limited) dice pool. Part of determining the ultimate usefulness of this approach is finding a reason to use this method rather than the normal methods for adding disadvantages and negative conditions to the opposing pool.

Where I’m currently thinking through using this idea is where certain conditions precedent must be satisfied to undertake a particular action at full effectiveness–a character can still take the action without having first (or simultaneously) satisfied those conditions, but they must accept a “Forced Die,” a d4 added to the pool that counts toward their Pool Limit, to do so. This could be employed for taking simultaneous actions during conflict (the “multiple-action” penalty used in other games) if relevant to the way you track initiative and your action economy. It may also be used to accentuate certain conditions from the “run-of-the-mill” conditions represented by Complications.

As I mentioned at the top, I’m working on a full set of mods for Cortex Prime to run games set in Avar Narn. I’m sure there will be additional posts on this subject and others related to that ruleset on the blog soon (with the referenced post about human augmentations first among them).

Back to the Mud: Putting some Grit in Cortex Prime, Part I: Damage and Injury

faithfictionfatherhood 3 Comments

Readers who’ve followed the blog for some time have likely picked up two things with regards to my favored approaches to roleplaying games. First, I prefer narratively-structured games, like Fate and Cortex Plus/Prime. Second, I like my settings gritty.

At first, these things may seem contradictory; both Fate and Cortex involve capable characters from the get-go with fairly high chances of success in their actions. They give players Fate or Plot Points to shift the narrative in their favor from time to time. I’m of the mind that this is a false dichotomy. To me, having low-powered characters with correspondingly-low chances of success is not gritty; it’s either frustrating or comical. This has been my experience with low-level characters in D&D and especially in the Warhammer (both Fantasy and 40K) percentile systems (especially when the GM thinks of unmodified roles as “easy” ones instead of following the rules guidelines that “easy” rolls should give bonuses–this is easy to forget in the thick of the game). To me, a gritty setting is one in which the characters are capable, but even skilled characters can get unlucky and suffer extreme consequences. It doesn’t happen often, but even an untrained peasant with a pitchfork can kill an armored knight when the chips fall just so. This is where, as with real life, skill alone is not always enough to prevail.

Philosophy of gaming (were that an established academic field!) aside, this post is going to be about adding some mechanical elements to Cortex Prime to increase the grittiness of the system. As one last note within this preamble, I want to point out that no mechanical changes are strictly necessary to run a gritty game of Cortex Prime–simply narrating the action to fit the feel of the game can accomplish this. But, for those who want to go further, to adapt Cortex Prime from a “generic” system to one that can be tailored to genre and tone, here we go.

In this post, we’ll talk about some ways to use the rules mods given in the Cortex Prime Handbook (sometimes with small changes) to adjust grittiness. In the next, I’ll offer some ideas that diverge more significantly from the mods contained in the Cortex Prime Handbook.

Being Taken Out
On my first readthrough of the rulebook, it struck me that the Stress and Trauma system suits a gritty setting best. Subsequent thought revealed that I may just be partial to that system because it feels a little more like “traditional” RPGs without going fully to the “Ablative Hit Points” mod. Reflection has led me to the thought that the basic rules for being taken out (spend a Plot Point to not be taken out of the scene) may be used to bring heightened tension to conflict that matches with a gritty feel. The key here is in addressing the consequence here suffered upon being taken out. For more cinematic games, the Consequence suffered for avoiding being taken out can be narratively (but not mechanically) lower–getting winded, winged by a bullet or otherwise put in a position that complicates things without being in real physical jeopardy. Conversely, these Consequences can be made more narratively significant without modifying the mechanics: if the character suffers a Consequence because of a gunshot, then the Consequence could be Sucking Chest Wound d10 or Gutshot d8. Even if no mechanics are altered, this will certainly put players on edge more than Flesh Wound d8. Of course, I’m not just going to suggest narrative changes here. My main point here is that, with regard to the base system for conflict, staying in the fight creates an additional pull on resources (in the form of Plot Points). Tough choices regarding resources is a core of mechanically-gritty systems–this naturally increases the dramatic and tactical strain on both characters and their players. Consider using the “core” system for being taken out with other rules systems to drive home risk and a need for resource conservation.

Stress and Trauma to Lethal and Non-lethal Damage
One alternative to the core system for being taken out of a conflict presented in Cortex Prime is the system for Stress and Trauma. Under that system, a character first takes Stress as a Complication to an attribute when losing a test in a confrontation. If the character has d12 Stress, this is converted into Trauma, which has the same mechanical complication as a Stress Complication but which is more slowly recovered. A character who takes “damage” that would push Trauma beyond d12 is removed from the game, probably because the character dies in the case of Physical Trauma (or is mortally wounded, put in a coma, etc.).

One simple shift in thinking here is to draw upon the World of Darkness/Storyteller damage system, thinking not in terms of Stress and Trauma but lethal and non-lethal damage. To be specific, replace Stress with Non-Lethal Damage and Trauma with Lethal Damage as with the original system, once Non-Lethal Damage is at d12, further Non-Lethal steps of damage are added to Lethal Damage. But where circumstances indicate the damage received would be life-threatening (the use of weapons, a fall from a height, fire, electricity, etc.), apply the damage to the Lethal Damage die, skipping over the Non-Lethal Damage die altogether. This would work well in systems where brawls (fisticuffs being treated as Non-Lethal Damage under the logic that punches and kicks can be deadly, but it usually takes more than, say, hitting someone with a hammer, to push from bruises to serious injury) are more common than deadly fights, or where the consequence of producing a weapon should be dramatically significant. This can easily be combined with the core Being Taken Out system to make conflict (especially physical conflict) an extremely serious event rather than a common and expected aspect of the game, suiting this especially to investigative or political genres.

A further question to be answered if using this system is how to apply the Complications of Non-lethal and Lethal damage. Do you apply both dice to the opposition test, only the higher of the two, or use some other method to determine effect on rolls?

For an additional complexity, you can allow appropriate armor to convert Lethal damage into Non-Lethal damage based on the armor’s step/rating. This gives characters some added protection without armor having the ability to completely nullify the effects of an injury.

Recovery Times
As the Dungeon Master’s Guide attempts to do in D&D, making things feel gritter may be a matter of increasing recovery times. As the various implementations of extended rest rules in D&D indicate, however, extending recovery times fails if it is the sole method of making a game “gritty.” If injured characters can still meaningfully participate in the style of game being played as they recover, then extended recovery rules may work well. If they only make it necessary to “fast forward” for weeks or months as characters recover, this doesn’t really provide you with any benefit.

If it fits–say one of the features of your particular game is that the characters’ situation gradually worsens until they manage to snatch victory from the jaws of defeat at the very last moment (which, if you believe the gaming philosophy espoused by John Wick in his Play Dirty books–controversies about his behavior as a person and RPG developer aside–is what players really want), then you might be served by extending recovery times. Unless truly necessary, though, it’s probably best to continue keeping recovery abstract without adding too many additional recovery rules. Consider having Stress (or its equivalent) recover between each session and Trauma (again, or its equivalent) recover between adventures. This provides dramatic increase in the tolls taken on characters as a story progresses without bogging things down. Combine with a Doom or Crisis Pool mechanic and you end up with a serious spiral of stakes.

To my mind, as a matter of game design, the best place for extended (or “realistic”) recovery times is in settings where some form of “miraculous” healing exists to circumvent normal recovery times, whether magical or technological. This bears in mind the realism of injuries while allowing characters to return to full status in a more player-satisfactory time frame. The only time the rule really matters, then, is when the players do not have access to such super-healing, allowing for an occasional point of higher stakes and drama if used sparingly.

“Ablative Hit Points” and the Condition Monitor
Above, I mentioned drawing inspiration from the WoD/Storyteller system for rethinking Stress and Trauma. Here, I’ll make reference to Shadowrun‘s “Condition Monitor” as a way for modifying the “Ablative Hit Points” system given in Cortex Prime.

Shadowrun calculates damage in “boxes” inflicted on a character’s “Condition Monitor.” A character has two Condition Monitors, really–one for “Stun” damage and one for “Lethal” damage. Each track typically has ten boxes, but this may be modified by a characters attributes, cyberware and other traits. As with Stress and Trauma in Cortex, “Stun” spills into Trauma when the Stun track is full. Where the Condition Monitor approach provides inspiration for Cortex is that it spaces out the mechanical penalties suffered for injury along the track (in more recent editions, cyberware or other factors can modify exactly where on the tracks these penalties are situated).

We can add a similar idea to Ablative Hit Points, assigning Consequence Dice to various segments of the Ablative Hit Points total. If you start with 10 “Hit Points,” perhaps a d6 Consequence is suffered when your remaining total reaches 7 Hit Points. This combines the “pacing” mechanic of Hit Points with more discrete and immediate effects. As with Shadowrun, and the Lethal/Non-Lethal damage system above, you could maintain two tracks, with excess “Stun” or non-lethal damage spilling into the Lethal category as it does in Shadowrun. If you use two tracks, you again need to decide whether penalties from the two tracks stack (or if only the Lethal track has penalties at all, which might allow a middle-ground between the cinematic and realistic).

To combine ideas from Shadowrun and World of Darkness, you could use a single track for both Non-Lethal and Lethal damage. To do this, Non-Lethal and Lethal damage are notated differently on the track (WoD used “/” and “X” to fill boxes). If the track is full and additional Non-Lethal damage is received, any Non-Lethal damage marked on the track is converted to Lethal damage before any points “overflow” into the condition that occurs (whatever that may be) when damage is received beyond a full track.

The number of Hit Points a character has is an important consideration. Thinking in terms of Dice Steps to numbers (see Rob Donoghue’s post on Evil Hat Games) mapping onto a 1-5 system (as in Fate), if you’re using an Effect Die, a maximum of 5 Hit Points of damage may be done with a single attack, perhaps one or two more if you use heroic successes for stepping up. The major consideration here is whether you want the possibility that a (player) character can be killed in one attack (depending on what having 0 Hit Points means). Additional considerations include how much damage can characters suffer overall and what is the hit point recovery rate.

If you want the additional mechanics, or a shift more toward the “traditional” RPG feel, you can add damage values for weapons (which should be a factor in determining the length of your damage tracks). Likewise, you can have armor prevent damage altogether, convert lethal damage to non-lethal damage, or some combination thereof. This shifts away from the core philosophy of Cortex Prime by moving toward a stricter accounting for gear and equipment, but if such a move suits your game, why worry about that at all?

Brancalonia: D&D Meets a Lighter-Hearted Blades in the Dark

faithfictionfatherhood Leave a comment

Those of you who’ve been with me for a while know that I’m not a big fan of the systems used for D&D. The older and wiser I get, and the more I come to understand game design, the more I see the justification for the choices the system makes. It seems that a lot of times, my upset with the design choices are amplified by traditional (mis-)interpretations of the intent of those systems. At the end of the day, D&D is a game people love, and there’s nothing wrong with preferring that system over others. For me, though, I prefer my games a little harsher and grittier, and while I think D&D should best be considered a toolkit along the lines of Fate or Cortex (certainly not marketed that way but treated that way by DMs by long tradition), I find that it would take as much or more work to kitbash D&D into something approximating what I want as to design a system particular to my tastes. In fact, a few weeks ago I got some of my gaming friends together in our first post-vaccination meet-up to discuss putting together a fantasy game using highly-modified D&D rules (for all my complaints about the system, I listen to actual play podcasts and get a desire to play all the same). Instead of spending a lot of time discussing changes and systems, as I’d expected, we relatively quickly came to the decision that they’d (and I don’t disagree) that I devote my time to setting and system for Avar Narn and that they help playtest rules.

That’s a long walk to the real beginning of this post, mostly to explain that I don’t usually review or spend a lot of time on D&D-related books or systems as part of the blog. Brancalonia, though, is just that captivating.

Brancalonia is a setting (with rules modules) for 5e D&D, taking place in a “spaghetti fantasy” version of late-medieval/early modern Italy. Those of you who know my background understand that my interest is immediately piqued. Even without my deep love for the Renaissance in Italy, a mashup of fantasy and the spaghetti western genres sounds like two great tastes that taste great together. In execution, the “western” influence gives way more to the Renaissance themes of misrule, the Commedia Dell’Arte, and the best parts of early-modern humor. The fantasy is low without being gritty (think of a greasier, sleazier, ne’er-do-well with a heart of gold sort of vibe).

The mechanics of the system accomplish this in several ways. First, the restriction of characters to level 6 (a common change to evoke “low” fantasy in D&D without much fuss), though there are character advances that may continue to occur after hitting maximum level. Second, the inclusion of subclasses that evoke the feel of the setting without requiring massive overhauls of the core D&D classes. Third, a bevy of rules additions (more than modifications) that reinforce the feeling of Brancalonia. Short rests are changed to a full night and long rests to a week in line with the suggested rules modification in the Dungeon Master’s Guide. The long rest is then incorporated into a downtime “Rollick” system.

Other rules include a system for Brawls (a non-lethal combat type indicative of both semi-good-natured contests between rivals and conflicts between criminals who know that drawing steel changes the context of the fight into something of interest to the authorities–to say nothing of lethality), methods for tracking characters’ bounties for their misdeeds (and the potential consequences thereof), the aforementioned “Rollick” system and rules for relationships to the characters’ band and company as well as an upgradable hideout. The standard D&D economy is changed not by complex changes to numbers in costs but by the vast lowering of the amount of gold characters are likely to have at any given time, limitations on magic items, a system for squandering winnings (reminiscent of Barbarians of Lemuria) and rules for “shoddy” equipment–what the characters will most often be using.

I make mention of Blades in the Dark in the title of this review not simply because it’s the previous game I reviewed, but because the systems in Brancalonia remind me of a (lighter) version of Blades in the Dark crew rules. Rather than managing the relationships between rival gangs as in BitD, the Knaves of Brancalonia are “Bounty Brothers” more often than deadly rivals. But the game does follow the same sort of job–downtime–job cycle as BitD, with a simple but perhaps more formalized system for managing the group’s hideout and its available amenities (described as Grandluxuries). The jobs set to a group of Knaves is implied to be a little more varied, both in context and geography, than the heists of Doskvol.

Also like BitD, characters regularly engage in their vices during downtime in Brancalonia, though the results in the latter are more often amusingly complicating than the self-destruction of the former. The best summary of the relationship between the two, I think is that Brancalonia takes itself less seriously, creating a picaresque tale of rowdy louts rather than a depressing story about desperate criminals.

Some notes about the writing itself: the game was originally written in Italian, and I get the feeling (or make the assumption) that part of the mastery of the feel of the setting is the immersion of the writers in both Italian culture and European history in ways that a Yank like myself can only dream of. The translation into English leaves a text that is clear and easy-to-understand–as well as very well-written. The book could have used some more editing, but the issues I find are typically minor mispellings and particularly the omission of certain letters in words (including within chapter titles!). Still, I found nothing that endangered comprehension or that reasonably compared with the first released draft of the latest Shadowrun rules.

I really can’t over-emphasize how well-written the setting material is. Not only from the standpoint of well-constructed and stylistically-impressive sentences, but also of language that evokes the feel the setting aspires to. I imagine both the original writers (the team of Epic Party Games) and the translator (Sarah Jane Webb) are to be commended for this feat. To boot, the artwork is amazing and highly evocative. I daresay that it’s worth the price of admission alone.

I must admit a certain forlorn agreement with all of the “What our party thinks it is/What our party actually is” memes when I see them, and herein lies another strength of Brancalonia–its tone is that sort of light-hearted foolishness often achieved by players of fantasy RPGs to begin with, so what may be considered a falling-short of the transcendent heights of “great roleplaying” in other conditions is right in with the theme and style of the game in Brancalonia. This alone is a huge strength.

If you’re a less-experienced GM looking for the style of BitD in an easy-to-run system, or a group who couldn’t care less about roleplaying as “Art” so long as everyone is having fun (always the first principle of committing free time to an RPG, I think, even if you want to make “Art” as well), a group looking for a grittier but light-hearted D&D setting, a new gamer wanting to learn to play RPGs, an aspiring designer looking for an excellent example of setting writing (rather than excellent worldbuilding–it may be that, too, but there’s so much material to draw on to create the setting that I’m not sure that it deserves that categorization), or a veteran gamer looking to do something decidedly fun and different, Bracalonia is definitely worth checking out.

Is it just me, or are we in something of a golden age for Italian game designers? I think of The One Ring as well and expect we’ll see more games of note from this group of designers as well.

Cyberware in Fate (Theory and Planning)

faithfictionfatherhood Leave a comment

In my previous post, I mentioned that I’m working on some Fate hacks for Star Wars and Shadowrun. As I continue to develop ideas for those hacks, I wanted to share some of my thoughts on handling cyberware in Fate (with some ideological commentary on handling cyberware in roleplaying games in general).

Let me begin by saying that I love the complexity and diversity of cyberware and bioware in Shadowrun, even if it verges on turning character creation into “Accounting, the RPG.” Without hesitation, I’ll state that it’s the character creation systems in the official Shadowrun rules that most draw me to that ruleset. Running the game with the Shadowrun rules, though–that leaves something to be desired. I’ve spent a few evenings reading through the Cyberpunk Red rulebook (having also spent a good deal of time recently playing Cyberpunk 2077–review forthcoming), and I find the cybernetics in that game limited–frustratingly so–when compared to Shadowrun.

(As an aside, since I grew up with Shadowrun and not Cyberpunk (even before I started reading all of the fiction of the cyberpunk genre), it’s hard for me to be satisfied with a cyberpunk setting that doesn’t also include magic and elements of the fantastic. I’m tempted to worldbuild my own, fantastic, post-cyberpunk setting, perhaps for use with the RPG ruleset I’m developing for Avar Narn. Since, without a Patreon, I have some more flexibility in my worldbuilding endeavors, and since I’ve already put down the cash for a lot of functionality in WorldAnvil–a result that in my mind has been worth the whole Patreon idea even though it didn’t pan out–this might be something you see posts directing you toward in the future.)

Back to our irregularly scheduled post. Is there a good way to capture the complexity of Shadowrun-style augmentation in Fate? Of course there is–I just have to find it!

Core Approaches
The “basic” system for handling cyberware in Fate simply uses aspects and stunts (see Fate System Toolkit p. 152). Really, these are almost mini-stunts, given the difference between “minor” augs and “major” augs. This is a good start, but the Fate system can do a lot more, and, as you know, I like to play with the system and see where it might reasonably and usefully be pushed. If you’ve looked at my partial attempt at a Tom Clancy’s Division ruleset in Fate, you’ll see that I’m willing to push the envelope of the Fate system beyond its initial intent. On the other hand, it’s the initial intent–narrative focus and efficient play–that draws me to Fate in the first place, so I want to temper rules mods and modules I come up with in light of that. There’s nothing wrong with creating a new system that uses Fudge/Fate dice, but I’d like my creations to still reasonably be called implementations of Fate rather than hybrid abominations distantly inspired by Fate.

So, how do we expand on the Toolkit system? We invoke the Fate Fractal, of course! There are a few things that this will assist us with:

(1) By creating an overarching Extra, we can apply some facets of augmentation across the board. This should help implementation of ideas like Essence.
(2) By the same token, making Augmentation an Extra allows us to fine tune some of the cost of cyberware with Flaws, conditions and other character traits that can be bundled in with an Extra.
(3) While the core of stunts and aspects will easily account for many (perhaps most) cyberware/bioware/geneware/nanoware items, we’ve got other interesting options to play with.

Other Tricks
Among those interesting options, weapon and armor ratings immediately come to mind. Once I sort out exactly how I’ll handle weapons and armor, it will be easy to address augmentations like subdermal armor, integrated weapons, etc.

Even better than that (in my mind, at least), is the use of the idea of Red and Blue dice. The Toolkit describes the Red and Blue dice system on page 72. In the form presented, Red and Blue dice are used for weapons and armor, respectively. But there’s no reason they have to be. We can use the idea of Red dice as a mini- (almost micro-) stunt. “Roll a Red Die when using the Athletics skill.” This gives you a 1/3 chance of having a +1 boost to the result. Far less than the typical +1 or +2 from a stunt, but it still represents a tangible benefit (actually it’s, in raw statistics, the same benefit as a +1 to X skill in core Shadowrun, though this plays out differently because of the reduced granularity in Fate). As an additional benefit, this allows us to spread around a lot more small bonuses, allowing for characters with many different augs without having an insane character budget for extras.

Some other rules tricks I’m considering using: increase the Shift value of a Condition/Consequence; add a new Condition/Consequence; add additional Stress track boxes; modify stress box values.

Tags, Traits and Aspects
I’m also thinking about modifying the idea of “tags” in PbtA games. In Apocalypse World games, “tags” tell you something about the narrative but don’t necessarily have a mechanical component. For instance, a firearm with the “loud” tag doesn’t change the numbers on a roll when it’s used, but it should influence the types of moves the GM takes in response to its use.

Transhumanity’s Fate (the official port of the Eclipse Phase setting to Fate rules) uses a similar concept, which they call “Traits.” Traits act as “sub-aspects” or reminders of the purview and scope of the aspect to which a trait is attached. In many ways, this is that the Toolkit’s description of some “minor augs” works, like adding “low-light vision” to your cybereye.

Depending on how you look at it (or upon specific implementation), what I’m thinking about doing is actually closer to PbtA’s tags than Transhumanity’s Fate’s “traits.”

This is because Aspects actually have (at least) two functions. While an Aspect can be invoked to gain a mechanical bonus, an Aspect in Fate is also “always true.” So, at least as I understand and run the system, if someone has a Low-Light Vision trait, the existence of that trait justifies a lack of increased opposition to a roll based on poor lighting, even without the Aspect being invoked and a Fate Point being paid. This is one of those things that seems to take some settling in before new players grok Fate RPG.

If that’s how you run things, then it would be possible to divorce that “always true” portion of an Aspect from the “invoke to get a +2 or reroll” part of an Aspect. What does that leave you with? If the statement is attached to another Aspect, then it’s really pulling the duty of a TF “trait.” If it’s not attached to an Aspect, but you still treat it as “always true” for narrative purposes (we might say “for narrative positioning”), then it’s closer to a PbtA “tag.”

Implementation determines whether this is a distinction without a difference. If the augmentation system ties these “always true” statements to a stunt and not an Aspect, we’re pretty clearly in the realm of “tags.” Why would that be useful? A few reasons. Let’s look at the Fate Toolkit’s cybereye example.

The Cyber-Eye is a “minor” aug (meaning three to a point of Refresh) that gives a stunt-like effect (+1 to sight-based Notice rolls). This can be expanded by adding Aspects to the Cyber-eye, of which Low-Light Vision is one. But these added Aspects are also “minor” augs, meaning you potentially get three Aspects for 1 Refresh. Any problems that arise from doing things this way are minor at best and probably negligible, because the fact that there’s going to be overlap between many of these “minor” aug Assets and because, y’know, common sense and fair play. On the other hand, the low cost of these additions is better justified if they have only the “always true” element without the ability to grant a +2 or reroll. This helps fight the (again, potentially non-existent) problem of “Aspect bloat” but still makes those little tag-like tweaks worthwhile, because they still provide narratively and mechanically-significant information about when a roll should be necessary, what can be accomplished by a roll, and what reasonable opposition to a roll should be, all in line with the fiction-first approach of Fate. Example: having Thermal Imaging as a “tag” on your Cybereyes allows you to get information about the heat coming off of a vehicle’s engine in addition to make and model with a Notice roll–no additional mechanics needed and keeps the Fate Point Economy in check.

The only concern I’ve got with this approach is where it may require additional parsing and whether that additional parsing will add enough complexity to the system that the detriment outweighs value. Example: you can choose the “tag” Low-Light Vision for your Cybereyes, or you can choose Zoom Magnification. Should Zoom Magnification be a “tag”, an Aspect, or a stunt? Is it too weird to have sub-choices on an augmentation that vary so widely in mechanical effect? To be determined.

Essence and Humanity Loss
Both Cyberpunk and Shadowrun indicate that human augmentation directly results in reduced empathy, reduced “humanity.” I understand the need for Essence as a balancing issue in Shadowrun; I understand Humanity Loss in Cyberpunk less, since all characters have equal access to cyberware.

From a setting perspective, or philosophical or theological perspective, I find humanity loss and Essence rules to be strange, unsettling, and somewhat offensive. The reasons are many, but let’s focus on a few:

It’s extremely difficult to determine the psychological effects of human augmentation. If you read my theological or philosophical posts, you know that I’m an existentialist in my approach to both pursuits. I believe that our experience as embodied beings is very important to how we understand the world and our place in it. Our experiences with and relationships to our bodies are very complex things–we can talk about BMI, magazine covers, messaging about “ideal bodies,” anorexia and bulimia, and many more indicators of the nuanced and often troubled ways in which we relate to our material forms. But I defy the belief that someone who has a prosthetic is somehow less human than I am–that humanness is an inalienable part of their self. The argument made in Cyberpunk and Shadowrun on these grounds is horribly ablist.

Yes, a person’s humanity can be twisted and corrupted, made hard by experiences or choices. But I’m not convinced that fitting a piece of metal or a cloned and genetically engineered organ to one’s body is, by itself, the kind of experience that leads to such a loss of self. People who are benefited by prosthetics treat their experience of loss and restoration (however partial) in different ways–just like we all take different approaches and establish different paradigms with regards to how we each think about our own body. This paradigm might involve feelings of depression, despair, uselessness, failure and many other negative feelings that touch and trouble our relationships with self and others, but that’s a far cry from the “I feel 15% less able to relate to you or to feel compassion because my arm is made of aluminum” that our leading cyberpunk roleplaying games seem to expect.

The books in the Altered Carbon series (and the TV show), and the Eclipse Phase game (in d100 or Fate form) both take a more believable, more philosophically defensible and–perhaps most important–more interesting approach to the psyche and human augmentation. In both settings, psychological trauma can arise as a consequence of resleeving for many different reasons, but these are mostly involved with the experience of embodiment itself, of suddenly looking different or occupying a body that feels very different from what you expected. This is not the same as being psychologically traumatized by what is, at its core, enhancement surgery. Moreover, the psychological traumas of Eclipse Phase and Altered Carbon are treated with as much nuance (and perhaps empathy) as other types of psychological trauma, rather than being this unavoidable downward spiral of emotional intelligence.

Shadowrun perhaps goes farther in making a spiritual argument as well. The value of this is in adding complexity to the way the magical and supernatural elements of the game function, but the core assumption: that voluntarily changing your body results in spiritual detachment between body and soul, is a tenuous one. I can’t with any definitiveness say that it’s wrong, but it strikes me, personally, as wrong. Your mileage may vary.

Fortunately, the Fate system is more resistant to balance issues than Shadowrun is (which, despite having Essence, is full of potentially game-breaking mechanical constructs), so Essence issues do not need to be treated in as much detail as in the official Shadowrun rules. That leaves me with a design question: (1) cater to my own beliefs, suppositions and predispositions, or (2) adhere to fidelity to the setting and mechanical conceits of core Shadowrun for sake of fidelity to the system being ported. At this point in time, not sure how I’ll go. Were I designing this hack with more of Cyberpunk in mind than Shadowrun, I have to say I’d be inclined to ignore Humanity Loss altogether and let cyberpsychosis be a thing that happens in the world, but not to player characters.