Showing posts sorted by relevance for query shields. Sort by date Show all posts
Showing posts sorted by relevance for query shields. Sort by date Show all posts

Tuesday, 15 February 2022

Careful with that axe! Damage in D&D and RuneQuest - and a new house rule for shields


In the first edition of Dungeons and Dragons (1974), all player-character attacks did D6 damage. Strength bonuses were yet to be dreamed up - unless you were an ogre, in which case you did D6 + 2 damage, or a giant (2D6).

In many ways, this way of handling damage is superior to all that came afterwards, including the STR bonuses and varying weapon damages that came in later supplements and versions of the game - and in later games such as RuneQuest. And I'd argue that the rot had set in even with ogres and giants in 1974.

Why? Well, a single die of damage always allows the possibility of just a single point of damage being done - a light wound, in other words. And that's important. Even an ogre should be capable of just grazing someone as it swings its club. 

One thing I've noticed as our campaign has progressed through its Gloranthan phase is that many characters are incapable of not maiming the average unarmoured foe with a single hit. If you're armed with a dagger in RuneQuest, you do 1d4 +2 damage to start with. If you're only a bit bigger and stronger than average (STR and SIZ averaging 13), you'll be doing 2d4 +2. But the average human character has just 3 hit points in each arm. So the minimum damage from a normal human wielding a dagger will incapacitate that limb. A stronger-than-average character armed with a dagger or club can't fail to maim the average human's leg or abdomen with a single blow. And woe betide anyone in the path of a great axe (2d6 +2 damage).

Despite RuneQuest's reputation for lethality, these high minima get lost in the welter of huge damage totals that can result from impales and other specials hits. That's because RuneQuest characters tend to be heavily armoured and loaded up on protective magic. But for all the game's vaunted realism, something has slipped. Two unarmoured men in a knife fight could keep going through numerous light wounds before something more dangerous or deadly occurred - at least if Borges is any guide. D6 is better damage for a dagger than D4 +2.

For D&D house rules - or for a substantially rethought versions of the game - I'd be tempted to stick with 1D6 damage as the norm, with no strength bonuses (those I'd apply to the attack roll). But what about two-handed weapons? Well, I've seen house rules around that go with 'advantage' - roll 2D6 and pick the best. That's an elegant set-up - it increases the average damage without ruling out the possibility of a 1. 

Another option would be to use a D8. I'd probably keep that for ogres, though. Giants could deal out D10 or even D12, depending on their size. And D20 might be the preserve of dragons and their ilk. The important point is that all damage should have a minimum of 1. A single die is always preferable to multiple dice or single die plus bonus. 

Now, if two-handed weapons offer an advantage, shields need to offer a different advantage too. As many have acknowledged, a single point of armour class isn't much compensation. Trollsmyth's Shields Shall Be Splintered rule is great, but it does give PCs the knowledge that they can always avoid lethal blows when carrying an intact shield.

Why not just have shield-wielders roll to reduce damage? Opposed rolls don't slow the game down, as they can be rolled simultaneously.

So how about this for shields in old-school D&D games? 

Shields
A character equipped with a shield rolls 1D6 when hit in melee or missile combat for which he or she was prepared. The shield roll is deducted from the attacker's damage. If the attacker rolls a six and the shield-bearer rolls a 1, then the attacker can choose either to do the full 6 points of damage or to render the shield useless until repaired. 

Bucklers
Bucklers are small shields that are sufficiently small to be carried inconspicuously on a belt. They act as shields in all respects, but absorb only 1D4 points of damage. 

This rule should ensure that shields are valuable, but should also avoid characters benefiting from extra lives through their use. As the shattering of the shield is the attacker's option on the 6:1 roll, it's likely that most will go for full damage instead. So shields will break, but in considerably fewer than 1 in 36 cases. 

One more thing: hit points. There's no point in worrying about keeping minimum damage to 1 if lots of people are running around with only 1 hit point. Perhaps the minimum score for the first hit die of almost any creature should be 2. But a simpler solution might be that most people and humanoid monsters (and certainly all PCs) just have 6 hit points as the default.

There's a nice symmetry about all this. Most ordinary humans (orcs, dwarves, whatever) will survive a single melee attack. And a shield will improve their chances of survival considerably. But there's still chance that any single combat round could prove lethal - whether that's because someone slips a dagger through your visor or pulls off a perfect sword-stroke.

Saturday, 3 March 2018

Shields again





This post follows on from this one, in which I loosely marshalled some thoughts on tweaks to the d20 combat system (using Whitehack).

My proposal for shield was this: a character equipped with a shield can attempt to block an attack with an opposed d20 roll. If the character with the shield rolls higher than the attacker but equal or lower to his own attack value (AV), then the attack is blocked. Draws are resolved in favour of the attacker; critical attacks allow the attacker to choose whether to do a normal critical or break the defender's shield.

Of course, shields come in various sizes. Bucklers have considerable advantages, because they're so small. You could take one down the pub (in the 21st century or in a pseudo-medieval fantasy world) without causing alarm. And you could certainly climb and crawl with one. So, let's give bucklers a -2 AV penalty when parrying. That makes them pretty handy for an unarmoured or highly skilled fighter, and well worth having. The shield of a kobold or small goblin could be used as a buckler by a human-sized PC, but would work as a full-sized shield for its original owner (who has less body mass to cover with it).

Conventional round or "heater" shields use unmodified AV. But these will impose penalties on difficult climbs or similar manoeuvres (typically -1).

Large shields - like a Norman kite or a Roman scutum - give a +1 AV bonus when used to block. But these are even more cumbersome (-2 for most manoeuvres requiring agility, and more at the GM's discretion). And they may have to be discarded in certain circumstances (narrow tunnels, for example).

Huge shields - pavises, perhaps, or tower shields, or the shields of ogres - give a +2 AV bonus but rule out climbing or jumping across chasms.

Monday, 12 February 2018

Get behind the mule!

In a recent post, I went on at some length about shields. Armour and shields, I think, should be an important part of a risk/reward trade-off in RPGs with a traditional sword-and-sorcery or medieval setting. Both should be highly effective in fights, but both are cumbersome and often inconvenient. And this should force a welcome burden of decision-making onto players.

Cliff notes
Encumbrance rules, in my experience, rarely work well - simply because both players and GM tend to forget about them in the course of a game. They also tend to get lost in the scrawl of a character sheet. A better system, I think, is for obstacles and situations to act as 'encumbrance challenges'. So, when mapping out a narrow passage or a cliff face or whatever, I'm now inclined to note penalties for characters carrying heavy or awkward objects - polearms, shields, crossbows, longbows and the like - or wearing heavy armour.

These modifiers are cumulative, of course. So, in Whitehack (the version of D&D I'm most familiar with and like best), I'd make a note like this for a steep cliff face in a cavern:

DEX check; double negative roll for non-Deft PCs; held weapons -2, long weapons -1, shields - 2, armour - AC [Whitehack AC rises from 1 to 6 for armour], bow -1, crossbow -1, longbow -2, pack -1, heavy pack -2. A sword at the waist would be -1 too, though this would be avoided by a PC who thought to sling it on his back (as no one would carry a sword in normal circumstances, film-makers of the world take note!).

So, a thief (one of the Deft in Whitehack terms) might face the cliff carrying a spear (-3) and with a short bow (-1), shield  (-2) and heavy pack on his back (-2). If he has DEX 15, he's going to need a 7 or under to succeed - and 5 or under if he's wearing leather armour (AC 2). A player, presented with those odds, is going to leave stuff at the foot of the cliff. And a fighter who faces rolling 2d20 and taking the worst is going to be stripping off his armour pretty damn quick. Add a pursuing horde of troglodytes, and those PCs are going to be scaling the cliff with just a dagger and their most portable treasures.

This is an area in which I really like 'naked mechanics' - ones for which the players are fully aware of the modifiers. Knowing the modifiers forces them into realistic decisions - or taking genuinely heroic risks.

Mule variations
Another way to deal with encumbrance in a manageable way is to mandate the use of horses or pack animals for transporting heavy stuff any distance. No one marches day after day wearing plate armour. And treasure - chests, sacks of coin, significant loot of any sort - demands beasts of burden. The default assumption should be that when a party that contains warriors of 'aristocratic' type (heavy armour, multiple weapons, big shields, etc.), horses or mules are involved. Yes, a Roman soldier could march with all his gear and a heavy pack. And, yes, so can a modern soldier. But a 15th-century man-at-arms wouldn't be waltzing through rough country with his plate armour on and carrying all his worldly belongings with him too. That's what horses (and pages and squires and their horses) were for.

This has implications for encounters: no, you weren't wearing your full plate when the ambush struck (unless you were riding); it was on the mule, of course. It also makes attacks by wild beasts more interesting, because so much more is at stake. If a sabre-tooth tiger uses the opportunity of the goblin ambush to maul your mules, you'll be reduced to just what you can carry. And in the wilds, that may not be a lot. Overburdened parties are more likely to attract further predators ...

What's that smell?
Bill the pony from The Lord of the Rings is a fictional example here. And the dwarves in The Hobbit suffer from having various ponies (with gear) eaten, first by orcs and then by Smaug. Managing and maintaining pack animals should be a big part of an outdoor adventure - and also an important factor in an underground one - if, that is, they will go below ground in the first place.

Mules might enter a goblin den, but might bridle at entering a gnoll lair. Unnatural carnivores, animalistic humanoids and common-or-garden predators can all serve as frustrations for well-equipped PCs, given a reliance on pack animals to stay well equipped.

And how would pack animals react to the presence of undead - or of sorcery? Tonight, I started reading Susan Cooper's The Dark is Rising with my kids. The book - which loomed large in my childhood - has a brilliant opening in which animals start reacting fearfully to the hero as his birthday approaches - because magical power is awakening within him. Getting a pony to walk through an elf-haunted forest might be quite a task ...

Arms and the man
All of this is a means of facilitating of the GM's main functions - forcing the players to make difficult choices. A frontal attack on an orc village? Suit up in your finest plate and grasp your poleaxe! Crawling into the kobold tunnels? Maybe that gambeson will be the best compromise - and best take a dagger instead of the poleaxe.

The effectiveness of full plate armour is often underplayed by RPGs - Whitehack included - as it should render a warrior almost invulnerable. The fact that late-medieval men-at-arms abandoned shields and favoured two-handed weapons like the poleaxe demonstrates this pretty plainly: shields were only abandoned when they weren't needed. So for a fighter, giving up full plate should be a real wrench. But it just isn't designed for potholing ...





Saturday, 10 February 2018

Hack and slash - some thoughts on RPG combat systems

My first RPG was the second edition of Runequest, which I got when I was still at primary school - for my ninth birthday, I think. Runequest has a terrific combat system - so much so that other games often seemed a little flat in comparison. But Runequest combat is possibly too good - too detailed and too deadly - for an entirely satisfactory RPG experience. My abiding recollection of all those early games is that PCs were short-lived - and often short of a limb or two if they did survive.

Now, that sort of combat isn't necessarily a bad thing. The obvious implication is that PCs should seek to avoid combat where at all possible, because they never know when that puny trollkin will get lucky with a sling stone. Monster stats for the game tend to reinforce that; as virtually all creatures are playable as PCs, Runequest's standard villains don't have the default relative weakness that common-or-garden humanoid monsters do in D&D. The average broo is tougher and more dangerous than the average starting human PC, by dint of higher STR, CON and SIZ, natural armour and natural weapons (horns). So PCs have to be wary, at least until they're expert with their weapons and tooled up with magical items. Our characters never, ever survived that long.

Detailed combat of the Runequest sort also needs a lot of data. With its hit locations, variety of weapon proficiencies and damage modifiers, let alone the widespread access to magic, the average Runequest monster stats look little different from a character sheet. Preparing monsters used to take a lot of time, so there was a lot of reliance on the stat blocks in the Fangs supplement and other pregenerated stuff.

Things like Stormbringer and (I dimly recall) Call of Cthulhu simplified things by removing hit locations. That's a reasonable compromise, but you lose some of the grit and detail, which is half the point. All in all, I think Runequest is a great system for games that feature NPCs rather than monsters - the kind of game in which a single fight might be the climax of a session, or its centrepiece. Maybe something like The Unforgiven, or Kazuo Ishiguro's The Buried Giant: stories in which violence erupts only occasionally, but is swift and bloody when it does.

That sort of game sounds pretty good to me, but requires an alignment of approach of players and GM. And a lot of prep - just in case. And sometimes (and especially with kids involved), raiding monsters and stealing their stuff is precisely what's wanted.

That's where the D&D style - a pool of hit points that can be quite large, armour class and a feeling of relative safety for our heroes until their hit points run low - works much better. The game becomes a lot less about the odds (Will that trollkin get lucky? Probably not ...) and a lot more about resource management. And that's fun. In recent games I've run for kids and for adults, the strategies that arise when hit points run low have been exciting for the players and involving for the GM. If you're raiding a hobgoblin settlement to get as much plunder as you can, the ticking clock imposed by dwindling hit points and limited healing opportunities creates a nice bit of in-game tension. The Runequest equivalent - a raid on a trollkin gang as in The Rainbow Mounds - might be more dramatic, but in a sudden, messy and abrupt way.

So, while Runequest is far superior as a simulation of combat, the D&D approach can often make for a better game.

At the same time, most D&D systems could do better at simulating game combat without sacrificing the balance of the game. The most obvious example, I think, is the shield.

In medieval or ancient combat, a shield was a huge advantage. That's why most soldiers carried them. D&D doesn't reflect this very well: in BECMI, a shield gives a fighter a -1 adjustment to AC: half that of wearing leather armour. But in a fight, a man with a sword and shield is much better equipped than a man with a sword and leather armour. I don't many experts on medieval combat would disagree, and, historically, it's clear that equipping troops with shields generally took precedence over equipping them with armour. A man with a shield has a good chance of blocking a blow that would otherwise injure him; a man in leather armour (or, more plausibly in the real world, a padded jack or gambeson, has a chance that the blow will hurt him less. And if someone shoots a longbow arrow at you, a shield between you and it is going to be much more helpful than a few inches of thick cloth.

So, having shields as a small AC adjustment is underselling them significantly. It's also, I think, missing a trick for gaming. Shields should be a huge help for a fighter. But they're also big, bulky and awkward to carry around - especially when spelunking. That suggests a couple of things: bucklers would be a likely compromise (presumably less effective overall and especially against missiles, and possibly requiring more training to be used effectively - more like parrying with a weapon than instinctively blocking); and "proper" shields should often be involved in trade-offs - abandoned to allow more treasure to be carried, or to facilitate a quicker escape - albeit a riskier one, if combat ensues. There's a nice risk/reward dynamic in that, which I like, and it enhances the resource-management aspect of the game.

How could shields be done well in a D20 system? I suspect they ought to be separated from AC entirely - perhaps by giving a saving throw to be rolled simultaneously with the attack. And the chance to save should be high - maybe 50% or more. A fumble could lead to the shield breaking, perhaps - broken straps or split, or whatever. And a larger-than-human opponent might both reduce the save and increase the chance of damage. Bonuses for weapons that might disable a shield - pila or angons, perhaps - could be worked in too.

All this should have some interesting implications in a game. Fighters who are forced to abandon their shields because of potholing or cliff-climbing will feel exposed and are likely to seek replacements from slain foes. A kobold shield might work as a buckler for a human - and an orc shield should do just fine. So ordinary shields become treasure.

But what about heraldry? In a factional dungeon, you have to be a bit careful about which livery you're sporting. You might be able to persuade the hobgoblins of the Broken Fang that you're only carrying a shield made by the orcs of the White Eye because you've just killed some of them - but good luck with that. And if you walk back into the town you've just rescued from the ravages of the White Eye tribe? Well, we all remember Theseus, Aegeus and those black sails, right?


Thursday, 17 February 2022

More on my house rules for shields, hit points and damage

 


The other day, I set out my house rules for shields in D&D (BECMI, Swords and Wizardry, The White Hack, whatever ...). I want to expand on them a little, so here they are again:

Shields

A character equipped with a shield rolls 1D6 when hit in melee or missile combat for which he or she was prepared. The shield roll is deducted from the attacker's damage. If the attacker rolls a six and the shield-bearer rolls a 1, then the attacker can choose either to do the full 6 points of damage or to render the shield useless until repaired. 

Bucklers
Bucklers are small shields that are sufficiently small to be carried inconspicuously on a belt. They act as shields in all respects, but absorb only 1D4 points of damage. 

These are designed to work with the original D&D rules, in which all weapons do 1D6 damage (unless wielded by something like an ogre or a giant). So the best shield parry will stop all the damage from the most powerful (or most accurate) human blow, but may not be capable of stopping a heavy blow from a larger and more powerful foe. An ogre uses a d8 for damage (rather than the original D6 +2), so there's a 1 in 4 chance that an ogre's blow will cause damage through even the best-placed shield. 

As I set out in that post, I'm also tending towards a default 6 hit points for human-sized creatures (and first-level characters), although I might settle for a minimum score of 2 on a character's first hit die. 

The reason for this is simple. I want each combat to have plenty of elements of uncertainty. One thing I love about RuneQuest combat is the sense of danger. For all your character's armour, you never know when that humble trollkin is going to roll a critical or an impale.

But at the same time, I don't want well-armed first-level characters to be walking on eggshells all the time. I think well-armed men-at-arms (e.g. first-level fighters) should fancy their chances when faced with lightly armed brigands (or orcs, for that matter).

Giving first-level characters and their foes six hit points each means that combat is risky, but that better armour - and especially shields - are likely to greatly reduce that risk if only one side has them. So three men-at-arms in mail with shields can feel confident (though not safe) in taking on three unarmoured brigands with cudgels. 

With 6 HP apiece, D6 damage and a D6 absorption through a shield (unless the shield:damage ratio is 1:6), each attack has the potential to be deadly. But we're not in the situation where characters will inevitably fall if a blow connects. There's room for a little back and forth - with each wound received making the chance of a decisive attack more likely. And that ups the potential for derring-do, because a PC can take a calculated risk with their six HP in a way that's simply not possible when they only have 1.

But what about stat bonuses? After all, some people are tougher than others - or hit harder. I don't want to use STR-based damage bonuses, because those raise the minimum damage above 1. The strongest character can still cause just a scratch when they swing a sword.

Might an exceptionally strong character use the common 2D6-and-take-the-higher house rule (normally reserved for two-handed weapons) and roll an ogre-sized D8 when using a two-handed weapon? I quite like the sound of that - but it would have to be for very strong characters. There is a way of gradating this, though: characters with 16  or 17 STR might do a D8 with a two-handed weapon, and those with 18 might get the 2D6/take-the-higher rule with one-handed weapons and the D8 for two-handers.

I don't much like CON as a stat - and especially not as one that affects HP. It seems to me that strength (as reflected in muscle and bone size and density) is the physical characteristic that would boost HP; CON, as a nebulous measure of disease resistance, stamina and fitness, doesn't have an obvious role to play here.

But here's the thing. If HP are set at 6 for a first-level character (or NPC), then any bonus takes the character out of the danger zone for at least one round. If you have 7 HP, you're not going to be killed by that orc arrow or guardsman's crossbow bolt. 

Perhaps, then, 6 shouldn't be the starting point. What if we make 3 or 4 the starting HP and have bonuses to HP from STR? A starting score of 4 with STR 13-15 +1 and 16-18 +2? Or a starting score of 3 with STR 13-15 +1, 16-17 +2 and 18 +3?

In that case, monster HP can be altered slightly by type. If one is separating goblins from orcs in the (distinctly un-Tolkien) D&D style, then perhaps goblins have 3, orcs have 4 and orc leaders and hobgoblins have 5 or 6?

We could also have character-class penalties for HP. Perhaps magicians, withered by study and unnatural practices, have starting HP of 2 or 3 against 3 or 4. And creatures smaller than human size could be reduced to HP 2 or 3 (though not 1).

There's something satisfying, though, about the symmetry of 6 HP and D6 damage. And if we're assuming that 6 is a lethal blow for most people, we might assume that it's a blow that would be lethal for almost anyone. 

What, then, do we do with levelling up? The 6 HP/D6 damage symmetry immediately makes anyone with even 7 HP exceptional. So perhaps the increment is 1 hit point per level rather than 1 hit die. Or perhaps fighters get 2 HP while other classes get 1. That way, the second-level fighter is immediately a more awe-inspiring figure - one who can risk an arrow or a sword stroke without fearing death. And by fourth level, even a full-on hit from an ogre won't kill at a stroke.

Decisions, decisions ...

Tuesday, 28 August 2018

What if the monsters are adventurers too?




In an earlier post, I noted that the "numbers appearing" in OD&D's monster descriptions are very high - running into the hundreds in many cases. That's great when monsters live in tribes. But what if they operate in much smaller gangs? What if they're essentially adventuring parties?

Let's take "dungeon ecology". Having a vast area of subterranean ruins peopled by one or more tribes of humanoid monsters gets us into "number appearing" territory. That suggests the Mines of Moria as a default: large numbers of orcs (or whatever) that you definitely don't want to meet all at once, or at all if you can help it. Any small groups encountered are likely to be guards or scouts - and, unless extreme care is exercised, will probably summon more of their kind. There's excellent potential for the adventure as a chase - get in, get what you're after (treasure, knowledge, passage under the mountains) and get out.

But move away from the tribal model, and you get something different: a defined group of antagonists who become proper villains rather than faceless mooks. Rather than Moria, you get something more like The Texas Chain Saw Massacre. Or Kill Bill without the faceless minions.

There's a lot to be said for that. It's closer to the way a lot of RuneQuest games played out (because broos, trolls or tusk riders tended to be a lot tougher than the average PC), and it implies that the PCs aren't Achilles-style heroes who can cut down enemies by the barracks-ful.

Miniatures-based games incline towards this sort of play, for two reasons. First, the wargaming 'what you see is what you get' principle helps you to individualise monsters. Second, with many monster types, you won't have that many miniatures available.

Let's take this group of orcs. I painted them up to experiment with Spooktalker's method of just painting the jet-black skin black of a fire giant, without any highlights.


The one with the red band round his helmet looks more intelligent (and a little more human than the rest). So he's clearly the leader. Could he be a sorcerer? Probably. And why is he holding a relatively crude cudgel when he's got an ornate two-handed sword on his back. Perhaps it's a magic cudgel.

That gets us started. Let's give him three spells from the 1st-3rd-level list in The Black Hack: Fireball, Sleep and Magic Mouth. Sleep, especially, makes him very dangerous - and presents opportunities for the orcs to capture the PCs. Let's give him 3 hit dice, 6 armour points, a two-handed sword and a magic club that, if not parried, causes a CON save or 1d3 turns of unconsciousness - but just once per encounter (whether or not the save is made). We'll call it Brimir's Bludgeon. And we'll call him Ithrak. He carries a small amount of stolen gold and silver jewellery, all of which is of fine workmanship - demonstrating an unusual discernment for a monster. This includes two amulets which match the shields of Zrakil and Athrog (see below). He also has the Livre of Argumand, a spellbook written in a demonic tongue and bound in demon-hide. This contains the three spells he knows and several others he has yet to decipher. If the players meet him on subsequent occasions, he will may have learned more spells. Ithrak is driven by a desire to acquire more sorcerous powers.

What about the big guy roaring at the sky? (He's a Gremlin Miniatures orc and a shameless rip-off of Aly Morrison's superb Baron Brightgore miniature.) Let's call him Braalu. He also wields a mace despite having a two-handed sword, so let's add provide a reason for that. What could it be? How about a thunderclap effect on the first impact of each encounter that causes a WIS save for all foes within earshot or a turn of flight. But let's also say that each week of owning the mace drains a point of INT, permanently, to a minimum of 3. For every four points lost, the owner loses a language. Braalu has long since lost the power of speech, although he still responds to Ithrak's commands. Let's otherwise make him a 2nd-level fighter with high hit points and give him the berserker rule (disadvantage when parrying his attacks in The Black Hack). Braalu is driven by bloodlust, a resentful awareness of his descent into near-animal intelligence, and loyalty to Ithrak.

The top-knotted hobgoblin with the mace has an appointment with a Biostrip bath, so let's ignore him. But the savage-looking fellow with the horned helmet, axe and knife is fierce and heavily armoured. We'll give him 8 armour points and two attacks. He's a 3rd-level fighter otherwise and is Ithrak's lieutenant, now that Braalu has lost most of his mind. We'll call him Gathrak. He's even cleverer than Ithrak, though he knows no sorcery, and exceptionally ambitious. But he's clever enough to hide it well. He will, however, be perfectly happy to deal a deathblow to Ithrak if the opportunity presents itself. And he's cunning enough to present himself as a peacemaker to the PCs if such a situation arises. He's also Ithrak's brother and an enthusiastic torturer. And he's an excellent tracker, by scent. He carries little on his person but his weapons, a small kit of torture devices and a carved demonic idol about half a foot high. Gathrak is driven by a desire to obtain Ithrak's sorcerous powers.

The other two, Zrakil with the spear and Athrog with the sword, are ordinary orcs, though large and physically robust (maximum hit points). But Ithrak has bound a minor demon into each of their shields. This compels them to fight by his side and to use the armour points from their shields to protect him rather than them. Each shield is controlled by a corresponding amulet that Ithrak wears around his neck. Carrying the shield while you wear its amulet bestows no benefit. Gathrak knows how the magic works and covets the amulets. Zrakil and Athrog have 6 armour points each of their own, plus the 4 each that they will bestow on the amulet-wearer from their shields. NB: if Athrog or Zrakil is slain and someone else takes their shields, the armour points will immediately replenish themselves - and the shield-bearer will be compelled to put them at Ithrak's disposal even if trying to attack him. Zrakil and Athrog are driven by fear of their leaders and hatred of living things (including their leaders).

Actually, Athrog and Zrakil should be flanking Ithrak, not Braalu.


Ithrak's band will often be accompanied by other humanoids - or even humans - that they have pressed into service. Even  Zrakil and Athrog lord it over these unfortunates.

Who are they? Some might remember tales of the wizard Argumand, who bred a race of ebon-skinned, fire-eyed orcs to serve him. A few might recall whispers that he was eventually devoured by these treacherous servants.

Where are they? They might have established themselves in some ruin or isolated manor. If they have been there long, they will have underlings, guards and half-orc whelps. But they may also be abroad, seeking sorcerous knowledge and a temporary slaking of the thirst for violence that throbs in their black hearts.

What do they want? Whatever the PCs are after!

Monday, 4 January 2021

Megadungeon mechanics part five: the joys of one hit die and the implications of what has gone before


I mentioned in the previous post in this series that my forthcoming megadungeon campaign will be more like a wargame than our main D&D campaign. That could be  misleading, though, as I mean it in only one very specific sense: that combats will mostly be of the one-hit variety. This is going to be - for most players - a low-level campaign. A character that gets to level two will be cherished. And one that gets to level three will be prized. 

In part, this limited advancement will come down to player decisions. As I've noted before, I'm using gold for XP - but only if that gold is spent on unspecified advancement-related stuff: training, study, sacrifices, etc. I'm also going to make equipment - notably armour - much more expensive than it is in the common iterations of D&D. I want a mail hauberk to be a significant treasure item in its own right. Full plate harness might cost as much as levelling up. And then there's the process of hiring mercenaries that I've set out: the common way to do this is to have them fight for an equal (or double or triple) share of the expedition's loot, which will cut down the amount of gold available to PC. When they can be hired for a day-rate, that day-rate will be high. All of this means that the players will be constantly choosing between advancement, equipment and assistance. 

It also means that most PCs will be on a solitary hit die for much of the time. I'm toying with the idea of having PCs roll their hit dice for each expedition, although that might prompt a mutiny. But as monsters will be doing fighter weapon damage (d8/d10) for the most part, even second-level fighters will be vulnerable to a lucky stroke from a hobgoblin poleaxe (d10).

So characters will be more like Balin (taken out by one orc-arrow) than Boromir (pin-cushioned by countless arrows and still fighting to the last). This has three main implications.

1. Big battles can be handled easily. If the players hire 20 mercenaries to raid a goblin lair, we might conceivably have 50 or more miniatures on the table. But if we know that most of the goblins will be killed in a single attack and that many of the mercenaries (and PCs) will be too, we can look forward to an initial frenzy of d20 rolls and then a rapid clearing of the battlefield. Mass combat won't involve much more book-keeping than a typical skirmish wargame, and the deadliness should keep it exciting. I expect a lot of traditional PC activity (sneaking, stealing, trickery) to take place during large-scale combats as well as as an alternative to them.

2. Shields shan't be splintered. Because I want highly dangerous encounters, I won't be using Trollsmyth's excellent "shields shall be splintered" rule. We use that in our regular D&D campaign, and it's great. But in the megadungeon game of fully equipped expeditions, it will just lead to mules being burdened with umpteen spare shields. What I'll probably do to compensate is have larger shields modify AC by 2 or 3 rather than 1, which will be reserved for bucklers. So a tower/kite/buckler hierarchy of 3/2/1 modifiers is probably the way to go - although I'll be thinking about this a bit more. 

3. Tactical retreats will be common. When running our main D&D group through the Caves of Chaos last year, I though that one of the most satisfying sessions was when a raid on the hobgoblin caves utterly failed. It ended with some PCs badly wounded and the hobgoblins hunting for them with hounds in the forest. And of course, the PCs swore revenge - which was all the more satisfying when it was eventually achieved. If your characters have only one hit die apiece, you're going to be very sensitive to the turning of the battle's tide. And that leads on to the next point.

4. Game sessions may involve multiple expeditions. I really like this concept: that three or four hours of play might not be confined to a single raid, but could feature two or three. In running our 250+-session lockdown campaign, I've observed that the joy of the game comes as much from the story that emerges between the sessions as from the sessions themselves. I want to reproduce that even in an episodic and occasional campaign, so that grudges can form, vengeance can be taken and best-laid plans can gang aft aglae. And the best way of doing that is to have more story in a single session. For that reason, downtime will be almost instant. Once the PCs are out of the dungeon, we move straight on to preparing the next expedition: "Two months pass, and your wounds are healed. Assemble your new party! What's the plan now?". As the megadungeon will have many entrances, there should always be a different approach worth trying - whether that's launching a diplomatic mission to attempt to recruit another faction to your current cause, attacking from a different direction or hiring a squadron of stone-masons to block up some of the entrances of the dungeon altogether.

With the lights out, it's more dangerous ...

I've also been considering some other implications of my previous posts. Most obviously, the continuity conceit of the last lantern-bearer won't work if many of the PCs have infravision. So perhaps all PCs should be humans. That frees up dwarfs and elves to be villains, which is just as it should be. 

Then there's the presence of pack animals. I want these to be essential for expeditions to the megadungeon, for realism (food, blankets, water), to simplify encumbrance considerations and to allow for the removal of large items of treasure. They do, of course, make the party more visible, noisy and exposed - but I think that can be turned to the party's - and the game's - advantage too. If you're pursued by angry dire wolves, you might think about hobbling your mules and abandoning them to their awful fate so that you can get away. That's one option that the last lantern-bearer often has - and it's one reason that he always gets away.

The danger to mules also means that it's not only monsters that move around the dungeon, but treasure too. That provides a great boost to emergent narrative, I think. If the dire wolves dragged down your mules outside the hobgoblin stronghold, what has happened to the golden idol you looted from the troglodytes? The hobgoblins probably have it - but what have they done with it? Could you somehow play the vengeful trogs off against them? Or have they returned it to the trogs and forged an alliance with them as a result? Does that mean that their lair will now be guarded by chameleon-like stink lizards that you won't see until they're upon you? Or has a drooling ogre rescued the statue from the dire wolves' leavings and dragged it to his cave where he's now attempting to woo it by piling severed heads in front of it each day? 

That's for the players to find out ...



Friday, 2 March 2018

The scrum problem: more thoughts on RPG combat and some Whitehack hacks!

Stuck in the middle with ... yeugh!
A problem with D&D combat is that it's like a rugby scrum. Once you've engaged, you're stuck there until it ends. In rugby, that's when the ball emerges; in RPGs, it's when one combatant loses all their hit points. And that can be dull - a simple trading of d20 and damage rolls until one side wins out. It can also take much longer than the few seconds a scrum takes - even allowing for resets!

Other games do things differently, of course. Runequest's combat feels fast and realistic, but a consequence of speed is that the PC is highly likely to end up dead or maimed. As I've discussed before, that's great for a game in which combat is a last-resort, high-stakes affair - the climax of a session rather than part of its punctuation. But it's not so good for a dungeon crawl.

Tales of Blades and Heroes, the underrated RPG version of the classic skirmish wargame Song of Blades and Heroes, has a great risk/reward element. As in the skirmish game, players choose to attempt between one and three actions; two or more failures have unpleasant consequences - but two or more successes can be combined into more powerful attacks. And because the game has a "downed" or disadvantaged status for combatants, the balance of power can change quite quickly. It doesn't have hit points, though, so unlucky PCs can be killed quite quickly - they have a fate point or some such, if memory serves.

And Dungeon World really frees things through the Powered by the Apocalypse system, wherein descriptions trigger "moves". A combat description ("I slash at the orc's throat with my knife") might be the "hack & slash" combat move, but another ("I dive through the ogre's legs to get behind him") might be "defy danger". What's so great about this system is that it encourages the players to think creatively and doesn't limit them to combat mode - even when their characters are hard pressed by foes.

So there's a strong argument for greater choice in combat situations. But how to do this in D&D-style games without clogging the basic d20 system with  complexity?

The most obvious way is just to encourage players to attempt whatever they want. Most good GMs do this anyway. But it's a good idea to remind players at the start of a session that chandeliers are there to be swung on, chairs to be flung in enemies' ways and embers to be kicked in their faces. Mechanically, a sound rule of thumb is that any "stat-check" option (a DEX check to kick embers in faces, for example) doesn't do actual damage to foes, but inconveniences them or buys the PCs time. And the negative consequences for failure are some minor disadvantage - a missed attack opportunity, an negative (worst of 2d20) roll or a positive (best of 2d20) for the enemies.

Also, tactical retreats should be eminently possible. I'd allow a player to back away from a fight at half-move without any risk - and certainly no free hacks. Attacks would be forfeited, but defence would be unaffected - so, with the shield/parry tweak I'm going to propose below, a character could defend himself perfectly well against a pursuing attacker (who would suffer no penalties from following up). In the "scrum" combat of the recent Whitehack games I've run, players haven't retreated enough. They should be able to draw off attackers (perhaps so a colleague can achieve something in the meantime) and retreat to positions of strength (doorways, most obviously).

Then there are shields. As I argued in my earlier post, shields should matter a lot. They should be truly valuable in combat - much more so than a +1 increment to armour class - but they should be heavy, bulky and something that dungeoneers often have to discard in favour of treasure or escape.

My solution? Adding an opposed roll to d20 combat. I've no idea whether other iterations of D&D already do this, but for Whitehack, here's how I see it. In Whitehack's wonderfully streamlined d20 system, an attacker succeeds by rolling equal to or under his attack value (AV) and over his opponent's armour class (AC). Rolling the AV itself is a critical. In my games, henceforth, a defender with a shield matches the attacker's roll with one of his own. He's aiming to roll higher than the attacker's roll but lower than his own AV (broadened to be 'defence value' too).

So, if Vareesh the Red (AV 14) swings a sword at Tarya Twicefallen (AV 12, AC 3, shield), he needs to roll between 14 and 4 to succeed. But Tarya can block his blow with her shield if she rolls higher than his roll and lower than or equal to her own AV of 12. If Vareesh rolls 7, Tarya turns the blow with a roll of 8 to 12.

In the case of critical hits, the attacking player can choose to either disregard the shield roll (even if it exceeds the attacker's AV ) or break the shield. So, let's say Tarya ripostes after blocking Vareesh's blow. She rolls a 12 - a critical. She decides to do double damage (as with a regular critical) to Vareesh, but she could have opted to break his shield-straps instead.

A shield block can be used only against a single attack in a given turn. But let's expand the system too, to allow characters to fight defensively: forfeiting their attack for a weapon-based parry. This can't be used against the same attacker as a shield, but it could be used against a second attacker (or a second attack from the same attacker). And of course, it can be used by a character without a shield, to allow them to try to hold off an assailant until a friend can help. The same principles apply - including the choice on a critical of double damage or a broken weapon.

At the same time, we should abandon Whitehack's d6-based damage for all weapons and allowed two-handed weapons such as poleaxes and greatswords to do d12 damage (there might be nuances within that - perhaps a greatsword might do d12 + 1, while a poleaxe might reduce AC by 1, for example).

This, I think, gives the players significantly more choice - both within the combat round and without. Wield a two-handed weapon and gain greater damage capacity at the expense of a shield. Fight defensively, or retreat to a place of greater safety, but lose out on the potential to cut your enemy down there and then. These choices involve significant risk/reward tradeoffs - and that's just as it should be.

Shield and plate
Note that shields are of huge value in combat under this system. If you have AC 0, of course you're going to want a shield when a fight breaks out. Unless, that is, you're bedecked in plate armour (for which I'd propose a much higher AC than Whitehack does - perhaps as high as 10 for Wars of the Roses-style plate). In that case, you probably won't bother and will prefer the destructive power of the poleaxe - just as real 15th-century men-at-arms did.

But because shields are heavy, can get in the way and can break (particularly if a GM chooses to cleave one on a critical for narrative purposes), they involve tradeoffs of their own. Carry a shield, but be prepared to have to abandon it because of its bulk in certain circumstances. Grab a shield from a fallen foe - but risk being mistaken for them by a rival faction. Recall the words of Samwise Gamgee in Cirith Ungol:

'The Morgul-stuff, Gorbag's gear, was a better fit and better made', said Sam; 'but it wouldn't do, I guess, to go carrying his tokens into Mordor, not after this business here.'



Sunday, 5 April 2020

Elven swords as minor magic items

Decisions, decisions ...

Almost every GM must have at some point purloined the likes of Sting, Glamdring and Orcrist from The Hobbit. As a reminder, these are elven swords "made in Gondolin for the Goblin-wars. Their blades glow blue when orcs are near.

A neat magical item, then. But where's the catch? My view of magical items is that they're at their best when they bestow minuses as well as plusses. The best magic items in legends and literature are ambivalent: think of Stormbringer, Tyrfing or Andvaranaut.

Tolkien's elven swords don't have any obvious disadvantage in the books. Most GMs would probably include them as "+1 swords, glow when orcs are near" (or goblins - D&D's division of the species makes this tricky to translate!). Fair enough - but I think it's better to drop the bonus and make their magic more minor.

After all, a sword that acts as an early-warning system is a considerable advantage in its own right. So here's how I treat "elven swords" in our D&D games:

1. They glow when non-human and non-demi-human chaotic creatures are near. So they'll help detect a disguised demon but not an evil priest or chaotic bandit.
2. They give no mechanical advantages in combat; they are, however, elegant and well made.
3. They have to be fully drawn to glow (you can't just loosen one in its scabbard to check the edge).
4. As a result of 3 above, you have to have the sword readied as you advance with it. That means that you can't use a bow or crossbow, or a two-handed weapon, at the same time.
5. As elves are on the small side in D&D (unlike Tolkien), elven 'swords' are short swords or 'normal' (i.e. arming) swords. They do not come in bastard or two-handed varieties. Daggers are much rarer than swords.
6. You can carry a drawn sword in your shield hand, but you'll have to drop it to use the shield in combat; in our D&D games, shields are highly desirable thanks to Trollsmyth's tremendous 'shields shall be splintered' rule. So, if you have a better weapon for combat (a one-handed bastard sword, say), you'll need to weigh up whether the early warning trumps optimal combat readiness.
7. While you get an early warning, you also give an early warning: the blue light from an elven sword is fierce and bright.

There are still ways to optimise situations, of course. A shield-armed character might carry the drawn sword in his shield hand and a spear or axe ready to throw before switching to the sword. And an adventurer sneaking round the underworld with an elven sword might duck down empty corridors to inspect the blade safely. But characters still have to make decisions of minor difficulty. And that's just as it should be.

And it's always worth remembering that some people react to such swords very badly indeed:

The Great Goblin gave a truly awful howl of rage when he looked at it, and all his soldiers gnashed their teeth, clashed their shields and stamped. They knew the sword at once. It had killed hundreds of goblins in its time, when the fair elves of Gondolin hunted them in the hills or did battle before their walls. They had called it Orcrist, Goblin-cleaver, but the goblins called it simply Biter. They hated it and hated worse anyone who carried it.



Wednesday, 8 August 2018

Ten RPG principles that I like

Having read and played various RPG systems over the past month, I thought I'd jot down some of the rule principles that I really like. Why? Who knows - but these are the things that occur to me, even if some of them are slightly contradictory.

1. Stats should matter.
A strength of 12 should be significantly better than a strength of 11. So I prefer systems that use the stats themselves, rather than modifiers derived from them. That's the major strike against Dungeon World for me. I've no quarrel with systems that just have modifiers as stats. The "roll equal or under" or "roll under" systems of Whitehack, The Black Hack and Into the Odd handle provide a great way of using the character sheet to the full. I like the Mythras/RQ system of adding stats together to get raw percentage abilities too.

2. Shields should matter.
I've rambled on about this extensively, but for me it's a crucial part of making an ancient/medieval combat system feel realistic. Shields should be sufficiently useful that the choice of a two-handed weapon presents a risk/reward dilemma - unless the character is decked out in full plate like a fifteenth-century man-at-arms. Shields are cumbersome, of course, so there should also be risk/reward decisions on whether to attempt climbs or leaps with them.

3. Encumbrance should matter.
As I've said before, no one would fight with a backpack on if they could help it. Carrying stuff is a pain, and should also involve risk/reward, tactical and resource-management decisions. If you're looting a dragon's hoard, you're probably going to have to leave some of your gear behind so that you can carry more plunder. Now, most games have fairly detailed encumbrance systems - but so, so many of them get ignored or forgotten in practice. Encumbrance can only matter if the system is clear and up-front. Major props to The Black Hack here.

4. Hit points work best as a barometer of fatigue and morale
Hit points are obviously an abstraction and are probably best kept that way. For all my RuneQuest bias, I increasingly feel that the erosion of hit points in a specific location is actually quite unrealistic.  In real life, the accumulation of cuts and bruises to a limb in successive combats wouldn't be equivalent to getting that limb gradually sawn off - but that's how it can go in RQ and similar systems. So, perversely, the more abstract systems can often give a more realistic feel than the "gritty" ones.

Now, obviously, what applies to limbs also applies to whole bodies - unless hit points are blood loss, I suppose. For that reason, treating falling hit points as representing increasing fatigue or flagging morale seems the most sensible approach to me. "Fatigue" can incorporate all sorts of minor wounds too, of course. But the Into the Odd approach - where STR starts to fall and saves are required once HP are gone - handles this very well. The Fantasy Trip's STR as HP does a similar thing, of course. And The Black Hack's table of out-of-action results is good too. With Whitehack, we always roll a saving throw (vs death!) when HP fall below zero - I forget whether that's the official approach or not - with precisely zero representing unconsciousness.

5. Weapon damage should be swingy.
Now that I think of it, a fatigue/morale approach to HP makes this one less crucial, but I don't really like the idea of minimum damage above 1 HP. In Whitehack, I rule that one-handed weapons do 1d6, spears, longswords and battleaxes do 1d8 when wielded in two hands and dedicated two-handed weapons (greatswords, poleaxes, halberds) do 1d10. So players get an incentive to use big, nasty weapons, but they're not guaranteed a lot of damage (a poleaxe is a thoroughly nasty weapon, but it could still just scratch you as a one-handed warhammer might, if you managed to get largely out of its way).

6. Damage by character class is a good thing ...
At the same time, I think there's a lot to be said for abandoning weapon damage in favour of character-class damage - as The Black Hack does (I think the concept has been around for aeons, though). I like the idea that a trained fighter armed with a dagger is a lot more deadly than a pasty scholar armed with the same. And even if you give that pasty scholar a poleaxe, the trained fighter with the dagger is still likely to cause more grievous wounds if they go head to head.

7. But character classes are a bad thing.
This is the RQ player's classic sneer. But I do think character classes are, by and large, a terrible idea. Whitehack has the best presentation of them I've seen, as the Strong/Deft/Wise classes are so flexible (you might well have all three represented by knights in a party, for example). I've always loathed class-based weapon restrictions, though. While RPGs don't generally do a great job in emulating fantasy literature (and books based on RPGs merit their own circle in Hell), stuff like wizards being unable to wield swords, battleaxes or maces is just abominable. The same objections I had in primary school still hold up: um, Gandalf? Elric? Jagreen Lern? The Witch-King? Thulsa Doom if we throw in film references - and so on. And don't get me started on clerics not using swords (Templars, Hospitallers, Teutonic Knights, Friar Tuck ...).

8. Stats can benefit from condensing (or correlating).
I've always been suspicious of WIS and INT. And I'm more than a little cautious about STR and CON - which is why I like the Fantasy Trip/Into the Odd STR-as-HP approach. More on that here. After all, DEX seems to cover a wider span than STR and CON (and SIZ in RQ): actual dexterity, agility, speed of thought, reaction time ...

Into the Odd, with just three stats, scores highly here.

9. Skill systems are a bore.
OK, there are exceptions here. RuneQuest handles this sort of thing pretty well. But on the whole, I think it's smoother and slicker to just rely on stats. Whitehack, with its groups system (write down your vocation/species/affiliation next to a stat or two and tell us why this means you're good at whatever you're trying to do) is really elegant here.

10. Magic isn't to be trusted
I don't like magic as technology. But I do like technology as magic (Into the Odd's arcana; ancient energy weapons; that sort of thing). And there's something about "magic systems" that I don't really like (least of all in fiction!). I'm generally inclined for magic to be something that players only access through artefacts (made by dwarves or whatever) and is otherwise wielded against them but not by them. But Whitehack does handle things well by allowing spells to be negotiated with the GM in advance and by having them cost hit points. That latter point is very simple, elegant and powerful, I think: if you must cast spells, they should come at a corporeal price.



Wednesday, 8 April 2020

Strength, shields and spears - my house rules for Basic D&D

While in lockdown, I've been running D&D for my kids and some friends. We've got a seven-strong party with player ages ranging from nine to a fair few decades past that. And it's been great - not only as a way for the kids to see their friends every day but also as a gaming experience. I've been taking them through The Keep on the Borderlands, which I've never run or played before, and it's been a blast.

We're using Basic D&D (as contained in the Rules Cyclopedia). Although the red-box Basic set was probably the second RPG I ever read (after Runequest), I don't think I ever played it. I did play a bit of AD&D, but - as children - we disdained Basic as childish!

Clearly, that was absurd. The rules contained in the Cyclopedia are well constructed and sturdy, and they seem nicely modular. In choosing them over the superb Whitehack, I wanted three things: a proper 'rules as written' game of D&D with simple choices (against Whitehack's more freeform approach), an instantly available common reference for the players and a very well-defined system of character progression. After all, who knows how long lockdown will last?

Nevertheless, I had to tweak a few rules. We're now eight or so sessions in, and I'm quite pleased with the tweaks. So here they are.

1. STR as HP/STR and HP
I've blogged about this before, but I've never been able to get over the possibility that a first-level fighter might have STR 18 and HP 1. The Fantasy Trip's use of ST(R) as HP gets round this elegantly. And Into the Odd takes a similar approach by combining HP and STR as HP. When characters run out of HP, they take wounds off STR and have to save under their remaining STR to stay in the fight/conscious/alive. I love this system. As in The Fantasy Trip, I have characters take STR damage off a running total that leaves the 'true' STR stat unaffected for lifting portcullises, 'to hit' and damage bonuses, and so on.

It works really well because it preserves HP as the classic Robin Hood vs the Sheriff of Nottingham store of cunning parries, shaken-off light wounds and narrow dodging of death. And it means that characters who roll 1 for HP don't feel too aggrieved. Perhaps they're just green, clumsy or plain unlucky - all conditions that can be cured through advancement. And it means that the STR 18/HP1 fighter is still much hardier than the average fighter; even after taking a 6HP blow, he'll be much more likely to stay in the fight than the STR 6, HP 4 magician would. That's just as it should be, I think.

At the same time, the fragility of first-level characters (and others) is preserved. There's no need at all to fudge your initial HP roll (my son's thief has 1HP and only 10 STR, but has made both his STR saves so far!).  Low HP mean that you'll be taking STR saves sooner rather than later. But they don't mean that you'll always die or pass out on being struck by a goblin slingshot or hit with a kobold cudgel. Combat becomes less predictable, which can't be bad.

2. PC and NPC deaths
Now, the chances of a PC death with this system are reduced somewhat. I've generally ruled that if you fail your STR check, you're out of the fight (not necessarily unconscious, but groaning and unable to do anything useful), but if your comrades rescue you, you can be revived with proper care (say, a week of rest and the attendance of physicians or equivalents). If your friends get you back to base immediately, you'll probably be OK.

That helps with party continuity and plausibility, and also with forcing the PCs to adjust their plans. If someone breaks their leg in a fight, you can't take them with you. And if you leave them, they'll die. Decisions, decisions ...

Similarly, if you're forced to retreat from combat without rescuing your friend, he's dead. So far, such injuries have made our campaign more episodic, which is a good thing. Raids on the Caves of Chaos are all fun and games until someone gets hurt ...

And there's also a risk of immediate death in certain situations. Our sole death so far came when a PC tried to leap through the gnashing portcullis-mouth of a living tower (pinched from Return to the Keep on the Borderlands). I warned him that this was a DEX save with death as the consequence, and he still attempted - and failed - his roll. Splat!

I'd apply the same warning in a focused combat like a duel to the death with a master swordsman, but not to a sudden skirmish with orcs. It means that the battlefield is strewn with the dying as much with the dead; the orcs don't get the STR save, but their leader might. Important NPCs get STR saves, but faceless minions don't.

In proper wilderness adventures (the Caves of Chaos are too close to the keep to count!), a failed STR save probably entails death. So running out of HP is no laughing matter - but it's something that the strong can usually shrug off.

All in all, this system makes combat more interesting. Maimed companions demand decisions - and death always threatens but isn't always instant.

3. Target 20
I've shamelessly stolen this from Delta. It's great - no need for THAC0 and all that. It makes combat and other stuff much faster. Hooray!

4. Shields shall be splintered
And I've nicked this from Trollsmyth too. I have a more complex house rule for Whitehack, but it doesn't work in a roll-high system. The point is that shields should be valuable in combat - just as they were historically. And I just love the heraldry-driven complications that can arise from carrying the Broken Skull's tokens into the Bloody Tusk's territory ...

5. Spears go first - and polearms can be spears
I'm just about OK with Basic's individual-initiative system, in which two-handed weapons attack after others. I can rationalise certain things with reference to cramped dungeons and sudden ambushes. But it becomes laughable when a dagger-wielder takes on a halberdier in the open and goes first. So, the way I fix this is to allow spears to win individual initiative (whether wielded in one hand or two), which makes them the natural weapon of choice for soldiers. And of course they can be thrown too. So the archetypal spear-and-shield-wielding guardsman makes a lot of tactical sense.

On top of that, I allow polearms to be used as spears or as two-handed weapons in any given round. So, if you want to hold your foe at bay with the pointy bit of your halberd, you'll win initiative against a foe with a sword, axe or knife, but you'll only do d6 damage. If you want to swing it for the full d10, you lose initiative.

I'm well aware that this isn't strictly accurate - you can swing a polearm at a foe long before they get a chance to close with you. But there might be a glimmer of truth in it for a 'killing blow' - especially if we're assuming that most fights take place in fairly cramped conditions. And it makes for nicely balanced decisions.

I'm not quite sure what to do about poleaxes. It's fairly clear that the authors of Basic had little idea of what a poleaxe actually was (up to 15' long? And no spike? Cheaper than other polearms? Really?). As the poleaxe is the descendant of the Danish axe, they might both be covered by the battle-axe category - but then the poleaxe was the weapon of choice of the heavily armoured knight, so it should be the best thing on the battlefield! I suspect it's easiest for now just to group it with other polearms - although poleaxes are generally significantly shorter than halberds, so would be more wieldy in close and less good at the speary stuff. I probably have to accept that D&D just doesn't do that level of detail!

6. Magicians are rare
This is less of a rule than a tonal note. The only magician in our party is an elf. I'm keen to have sleep spells and magic missiles be awe-inducing interventions - not something that most bandits or guardsmen will have seen before. So magic-users are rare, distrusted and generally keen to conceal their powers.

Friday, 22 June 2018

Whitehack and The Black Hack

Whitehack's been my go-to RPG for some time now. I use it for regular games with the kids and their friends, for family sessions (my wife can occasionally be persuaded to play) and for occasional games with my old RPG muckers. It's great - sleek and elegant, and with nice, intuitive mechanics. The "roll equal or under" system sits nicely with those of us who were raised on RuneQuest rather than D&D, as does the freedom afforded by the flexible character-class system. I've tweaked it a bit with regard to shields and weapons, and it works very well.

I've heard good things, though, about The Black Hack, another take on old-school D&D. Astonished to find that the rules cost less than two quid on DriveThruRPG, I bought them the other day. And I'm very pleased I did.

So how do the two compare? At the most superficial level, Whitehack is more expensive (and not for sale as a PDF). It's also edited to a professional standard, which The Black Hack isn't. Editing aside, though, both are well written and clear. There's nothing in The Black Hack that's hard to understand, and my quibbles about the editing could be resolved in a quick sweep for run-on sentences and awry punctuation.

But what about the systems? Both use a "roll under" mechanic, and both make extensive use of a character's actual stats - STR, CON, DEX and so on. I love this: it very quickly gives the characters some "shape", and means that a DEX 13 thief is not identical to a DEX 15 one when it comes to fiddly tasks. A reliance on modifiers, rather than raw stats, is a weakness of Dungeon World, another re-imagining of old-school D&D that I like.

Where The Black Hack differs from Whitehack significantly, though, is in its combat system. Where Whitehack has an "attack value" stat modified by STR, The Black Hack uses the STR score itself. DEX is used for dodging and shooting, and INT or WIS for spell-casting. Saving throws are also done on the six stats rather than class-based derivatives.

Some might find this simplistic (while being strong helps in hand-to-hand fighting, surely the best swordsman isn't always the strongest?), but I can see it working just fine on the table. And it's easy to rationalise STR as including "strength-related skills" as well as raw brawn.

Like Dungeon World or Ganesha's Sellswords and Spellslingers skirmish game, The Black Hack has only the players rolling dice. Monster attacks are resolves by attempts to parry or dodge with STR or DEX; failure leads to the players rolling damage against themselves. Stronger monsters (i.e. those with more hit dice) give penalties to the roll. Like Whitehack, the Black Hack compresses a lot of information into the hit-dice number, but it goes further, so that armour, damage, hit points and penalties are all directly derived from a single number.

Spells are a major point of difference between the two games. Whitehack's "miracles" are created by the player through negotiation with the GM during character creation and cost hit points to cast. I like this; it captures the sense found in Tolkien and elsewhere that magic is physically draining (think of Gandalf after his initial encounter with the yet-to-be-revealed Balrog in Moria). The Black Hack has a spell list; a conjurer's chance of casting further spells that day falls with each casting. I like this too: it's got a nice unpredictability about it, so that you can't plan the use of magic too precisely.

The Black Hack also has a modern, dice-based system for encumbrance and supplies, including ammunition. You don't have to worry about counting individual arrows, but you'll know when your quiver's getting light. This is a bit like Dungeon World, I suppose, and a nice abstraction that might work well if imported to Whitehack.

Perhaps the most innovative element of the game is its approach to armour. Whitehack uses ascending armour class (0 is none, 6 is plate), which is clear and intuitive. In The Black Hack, traditional armour class is abandoned; instead, armour and shields act as a bank of "buffer" hit points that must be whittled down before wounds can be inflicted. This is highly abstract, of course, but no more so than hit points themselves. I like it: it means that heavily armoured warriors are more or less invulnerable at the start of a combat but become susceptible to injury the longer it lasts - and the more tired they get. Armour points regenerate after an hour.

It's easy to think of situations where this will strain realism; imagine, for example, two plate-armoured fighters who are just about to deal with the last of their orcish opponents when more orcs reveal themselves and start shooting. By the rules, I think, those fighters would be effectively unarmoured against the arrows if they've used up their armoured points. But of course you can easily rule that armour points renew themselves in such situations (perhaps fresh combatants replenish armour point automatically).

So what are the respective strengths of the systems? I think I'll stick with Whitehack for campaigns. It's a more subtle system, and its less rigid character classes allow for less stereotypical roles in the party. I'm increasingly flexible with the players, so that a Deft character can have a Wise miracle in return for forfeiting his attunement or something similar; a Strong character might forego one of the special fighting abilities in return for a miracle or a sneak-attack specialisation.

But I can see two clear roles for The Black Hack. First, we often play one-off family games on holiday or with visiting friends, and The Black Hack is perfect for that. Character creation is very quick, and the game has a tremendously no-frills approach. The set spells will work much better for occasional players than Whitehack's creative approach, and "time to table" is extremely short.

The other thing I'll be using The Black Hack for is out-and-out dungeon-crawling - games where the excitement comes as much from the rapid dwindling of your hit points as the coherence of the setting.  We've dabbled a bit in Descent, but I increasingly think that looking for the platonic dungeon-crawler board game is a fool's errand. Full-blown role-playing games simply do the job far better, giving you more opportunity for character individualisation and innovative problem-solving. Although The Black Hack is written primarily as a "theatre of the mind" game, with abstracted distances and ranges, it would work tremendously well as a miniature-based tabletop game. I occasionally lay out dungeon tiles for the kids on the premise that their characters have a map of the setting, and then let them work through it, with surprises coming from secret doors, treasure and - of course - inhabitants. The Black Hack looks ideal for that.

There are whispers, too, of demand for a one-off RPG session in my office. The Black Hack might just cater for that too ....



Wednesday, 26 December 2018

Some speed-painted orcs

Fast 'n' dirty!

I've been meaning to finish off a few skirmish warbands for the children of some of our friends - a project I started far too long ago. So getting a few more finished quickly was the key thing. Here's how I did them.

The first step was to undercoat the orcs in black gesso. After that, I drybrushed them in mid-grey:




I then drybrushed them in white. The two layers of drybrushing create a rough gradient that provides highlights and shading through thin coats of colour.


I painted in the metals next. Metallic paints are the worst for polluting other areas of the miniature, so I wanted them in before the colours.

The colours for other areas are heavily diluted with water, so that the greyscale gradient shows through:


Then come the washes (Citadel washes in this case). If I'd been particularly pressed for time, I'd have used a single wash of sepia over everything. But as it was, I went with brown over metals, leather, hair, fur and weapon hafts; yellow over yellow cloth; red over red cloth; sepia over the green skin; and watered-down Blood for the Blood God over the pinkish areas of skin.



I then painted the tusks in buff, then highlighted them quickly in white. I used the same dab of white to pick out the eyes and brush lightly over the hair.



Next came a very few highlights in Vallejo silver-grey (which is the same as GW's Wych Elf Flesh). It's a nice 'universal' highlight as a kind of non-descript off-white that works on almost any colour. I highlighted only the pinkish flesh and the odd bit of the yellow clothing and fur, where raised areas had become too dark.


After that, I painted the eyes red and then added a dot of yellow, washed the shields in watery black, which I also used to black-line any messy delineations between colours, and roughed out a shield design in buff. I also used a bit of silver to roughly highlight the metal (an obvious stage to skip if time were short).



A few last touches finished them off, and then it was time for the bases.



The paintwork is pretty rough, but it is (I hope!) roughly pretty too. The advantage of this approach, apart from speed, is that you need take very little care. Most areas are painted by simply washing first a paint and then a purpose-made wash over the greyscale effect created by drybrushing. Only the faces and the shields get any real attention.

It occurs to me that this colour scheme - the same that I used on my pig-faced orcs - is very close to the Monster Manual's description:
Orcs appear particularly disgusting because their coloration — brown or brownish green with a bluish sheen — highlights their pinkish snouts and ears.
As Gygax said that he conceived of his orcs as less porcine than Sutherland's illustration, these fellows may come fairly close to the original conception of the D&D orc. Whatever - at least they're done now!