Friday, 29 September 2017

Saga of the Goblin Horde: Setting Book

I started working on Saga of the Goblin Horde back in December 2015, and I've released a lot of content for it since then, but now I've finally finished the full setting book! So without further ado...


The book contains the same information as the player's guide (introduction to the setting, 5 new races, 41 Edges, 20 Hindrances, weapons and armor, setting rules, deities, gazetteer, and map), but also includes the Game Master's section (setting secrets, a plot point campaign, a load of adventure seeds, an adventure generator, and a large bestiary).

Don't forget to grab all the other stuff for it, like the archetypes, One Sheets, etc. You can get them all here.

Monday, 25 September 2017

Chases in Savage Worlds

A lot of people seem to have difficulty wrapping their heads around the chase rules in Savage Worlds, either because they find the rules confusing, or because they have trouble connecting the game mechanics to the narrative. In particular, many people seem to view chases as a "race", when what they more accurately represent is a mobile combat encounter, in which the characters are exchanging attacks while rushing across the landscape.

The way I usually explain chases is by asking people to imagine a typical action movie chase scene, and then pick out five pivotal moments from the scene to represent the rounds in which the characters take their actions. The remainder of the scene would just be handled through the narrative.

For example, imagine this scene from Casino Royale:


In the above chase scene, I would probably define the five rounds as follows:

Round 1 (takes place at 0:26): James Bond makes a Driving roll in the first round (Agility rolls after that, once he leaves the vehicle). He has the Advantage, and uses the Force maneuver against the bad guy, but fails.

Round 2 (takes place at 1:15): James Bond has the Advantage, but drew the King of Clubs, meaning he's distracted by the explosion.

Round 3 (takes place at 2:40): The bad guy has the Advantage, and makes a Shooting attack at short range, but rolls a critical failure (his gun jams). James responds with an Agility trick (he doesn't need the Advantage for a Trick), and causes the bad guy to become Shaken.

Round 4 (takes place at 3:00): The bad guy has the Advantage, and attacks James, causing him to become Shaken.

Round 5 (takes place at 5:05): The bad guy has the Advantage, and reaches the safety of the embassy.

Everything else would just be part of the narrative, described by the players and Game Master.

Simplifying the Rules

Some people understand how to narrate the chases, but find the rules overly complicated, and/or dislike the way characters cannot attack without Advantage. A suggestion I've made in the past is to streamline the chase rules by removing the attack range and complication tables - even I have to look those up, and to be honest, having to reference table entries every round isn't very FFF.

Streamlined Chases

Each round, each character makes their maneuvering trait roll, drawing one card for each success and raise (as normal). The characters then take their actions in sequence, however:

1. You suffer -2 to attack (or 'Force') someone who has a higher card.
2. You suffer -2 if you have a dot card (2-10), and must use ranged weapons.
3. Complication (Clubs): Make another roll at -2 to avoid Fatigue or a collision.

So face cards would allow melee attacks, while spot card would require ranged attacks, and you'd have a penalty of between +0 and -4, which the Game Master or players could narrate as range, cover, distractions, etc.

Note: Savageblog Italia have translated this post to Italian, read it here.

Monday, 4 September 2017

Invoking Hindrances

When designing my Swift d12 system, I wanted to keep the rules streamlined, so I decided to introduce a simple mechanic for handling Flaws. The approach I used was to make them primarily descriptive, and allow players to "invoke" each Flaw once per session in return for Karma Points.

It struck me that the same approach would also work rather well for Hindrances in Savage Worlds, so I came up with a quick conversion:

Invoking Hindrances

Players can invoke each of their Hindrances once per session. This must be done before making a trait roll, and the player should explain how their Hindrance gives them a disadvantage in this particular situation. If the GM accepts the explanation, the player earns a Benny, but also suffers a –2 penalty to their roll, and must draw a card. If the card is Clubs, there is a further complication; the penalty increases to –4, and failure is treated as if it were a critical failure.

Players cannot spend a Benny to reroll an invoked Hindrance.

Example 1

The Game Master tells everyone to make Notice rolls as they approach the cave. Lexi invokes her Overconfident Hindrance; she's not scared of some smelly old cave, so she'll just go marching straight in without bothering to look for signs of danger! She draws the Five of Hearts, and makes her Notice roll with a –2 penalty, but Aces her roll and succeeds anyway.

Example 2

Rylan disturbs a dragon while exploring its lair. The Game Master decides that this scene will be resolved as a Chase, and asks for a maneuvering trait roll. Rylan invokes his Greedy Hindrance in the first round, and announces that he's been distracted by the dragon's treasure hoard. He draws the Seven of Spades and makes his Agility roll with a –2 penalty, failing the roll. Looks like he's going to need that bonus Benny for a Soak roll!

Example 3

Big Brak launches a furious attack against a human adventurer, and decides to invoke his One Eye Hindrance; the player describes how the human ducks around Big Brak's blind side, putting him at a disadvantage as he tries to swing his axe. He draws the Ace of Clubs and suffers a –4 penalty to his attack – failure! The GM declares that Big Brak loses his grip on his axe, and accidentally tosses it away into the river!

Summary

This rule obviously turns the "fluffy" Hindrances into more of a benefit than a drawback, but it works extremely well in Swift d12, where I've found it really encourages the players to add some interesting narrative to the game. I see no reason why the same solution wouldn't work just as well in Savage Worlds.

My older Hindrance Cards idea also gave players a more direct means of earning Bennies, helping to take some of the pressure off the GM, but it always felt a bit handwavy during play. By contrast, the "invoke" rule feels more like the players are paying a fair price for their bonus Benny.

Saga of the Goblin Horde: Quick Start update

Following feedback from a few more playtests (those posted here and here, as well as one run by a friend of mine for his local group) I've updated the Quick Start rules to incorporate several changes.

Get it here: SotGH Quick Start

The initiative rules have been rewritten to follow a new approach (described in more detail here): There is no longer a wits-based Guile check. Instead, the players and their minions now automatically act before enemy NPCs, but the characters can "rush" if they wish to act faster. Although the old initiative system worked fine, I found myself becoming very conscious of the extra roll every round, and it was starting to feel a bit tedious.

Goblin gang members no longer receive Agility +1, instead they just get a +1 bonus to Speed (so they still move quite fast), but have +0 in all their abilities. This makes them more comparable with their Savage Worlds counterparts, and also simplifies the combat scenes by reducing the number of modifiers commonly in play (as the Agility bonus meant an extra bonus to the gang members' attacks, and an extra penalty to all attacks made against them).

The Trapmaker Feat works a bit differently. Instead of just causing 2d6+Guile damage (comparable with a normal success), the trap is now treated as an attack roll (giving it the possibility of a critical success or failure) or a stunt (introducing the option for traps that stun, trip, or push people around).

The Cunning Feat no longer adds +1 to wits-based Guile checks (as those have been phased out with the new initiative rules), instead it gives +1 to Guile-based damage rolls (i.e., for ranged attacks).

The Chase rules have been redesigned. They still work in roughly the same way, but should now be more intuitive.

Friday, 1 September 2017

Swift d12: Rethinking Initiative

One of the problems I've currently got with the Chase rules is that, because only pursuers make initiative rolls, the fleeing character never triggers a complication. The obvious solution is to make the fleeing character roll as well, but that would make it inconsistent with regular initiative.

However if everyone rolled initiative in regular combat, it would add even more rolls, and the more I think about this issue, the more I feel that initiative is already overly intrusive. Savage Worlds manages to get away with calculating initiative every round, perhaps because the cards feel like such a different game mechanic to trait checks, but in Swift d12 the extra roll can become annoying.

The main design goal for the original initiative system was to ensure that one side didn't always get to act before the other (because there are often large numbers of combatants on the battlefield, and one side could cripple the other if they all got to attack first). Any alternative system would still need to address that original design goal.

One interesting initiative system I've read about is the one in Shadow of the Demon Lord, where characters can choose to take either a "fast turn" or a "slow turn". Players act before NPCs within each turn, and those in the fast turn take one action while those in the slow turn take two actions, so acting first comes at a price. This is a quick and clever mechanic, and feedback from players seems to be generally positive. While the solution wouldn't work as written in Swift d12, it's given me inspiration for something along similar lines.

Alternative Initiative Proposal

At the beginning of each round, the Game Master asks if any players wish to "rush" their actions, and those who rush automatically act first. After that, the Game Master may decide to make any NPCs rush their own actions, and they act next. Then the remaining players get to act, followed by the remaining NPCs.

However characters can only rush if they're not Staggered, and they become Staggered when they rush. Of course they can still use the recover action to immediately remove the Staggered condition as usual, but recovering is a simple action, so it'll cost them an action die.

Interaction with Other Mechanics

The Lightning-Quick Feat already allows characters to spend a Karma Point to take a simple action as a free action, so with the alternative initiative they could "rush" and then spend a Karma Point to recover.

In a surprise situation, the surprised characters always start combat Staggered, and this would prevent them from rushing.

The All-Out Attack maneuver gives characters +2 to attack and damage, but they also become Staggered. What I wanted to avoid in the original initiative system was a situation whereby players could choose to act last with an All-Out Attack, then act first in the next round and recover before anyone could take advantage of them being Staggered. But as Staggered characters cannot rush, this wouldn't be an issue with the proposed rule.

Thursday, 24 August 2017

Swift d12: Two More Playtests

I ran a couple more playtests this week. The first was a Saga of the Goblin Horde playtest with Manuel Sambs and his girlfriend, the second playtest was just Manuel and I, using my notes for modern-day settings.

Goblin Playtest

Although this wasn't a "proper" session, we went through the character creation process, and then I ran Bone of Contention. Character creation was reasonably fast, although the players spent a few minutes browsing through the Flaws and Feats for inspiration, as this was their first time creating characters (previously they'd just used pregens).

Once again we used the Shenanigans setting rule, and the results were hilarious. I will definitely be converting this rule across to Swift d12, so that it doesn't rely on the use of cards.

We tested out the opposed roll concept I proposed after the last playtest (where the opponent's ability is added to the TN instead of being subtracted from the roll as a penalty), and unanimously agreed that we didn't like it. It was confusing, one more thing to keep track of, and it felt particularly clunky when it came to critical successes.

While I still wasn't too happy with the current approach (treating your opponent's ability as a modifier to your own ability check), Manuel's girlfriend said that she found it about as easy as tracking modifiers in Savage Worlds. As she has a lot less experience with Savage Worlds than Manuel and I, we discussed if the main problem might be due to familiarity. Perhaps the Swift d12 system will start to feel more intuitive after a few games.

In the Savage Worlds version of Saga of the Goblin Horde, goblin gang members have Agility d8, which is average for the goblin race. So when I converted them to Swift d12, I gave them Agility +1. The problem is that Agility +1 in Swift d12 also gives the equivalent of a Savage Worlds d8 in all Agility-linked skills (including combat skills). Not only does that make goblin gang members far more competent, it also makes them more complex to track in combat, as they all have +1 to hit, and foes all receive a -1 penalty to hit them. So I think I will reduce their Agility to +0, and consider some smaller advantage to represent goblins being more agile (such as +1 Speed).

Modern Playtest

The second playtest was just myself and Manuel, so we used the Mythic GM Emulator, allowing us both to play. As a pair of independent repo men in an urban setting, we'd decided to take on a little "side job" for a wealthy gentleman, and a few days later he was brutally murdered. It was originally going to be an urban fantasy adventure, an introduction to my Primordial Horrors setting, but the GM Emulator has a habit of throwing curveballs, and this was no exception.

The initial pitch for the adventure involved an occultist and a stolen spellbook, but the former turned out to be the front for a criminal organization, and the latter ended up being a notebook filled with blackmail material, so the supernatural clues were nothing more than a smokescreen for an elaborate con. It wasn't exactly what we'd planned, but it was a pretty good story with a nice showdown at the end (a big fight outside a bar followed a car chase).

In the modern setting characters have devices rather than knick-knacks, and influence instead of gang members (although the appropriate influence can be used to recruit temporary minions, for example if you have underworld contacts, or friends in a street gang). While we did get into a couple of fights, without all the gang members combat moved much faster.

Overall I was very pleased with the feel of the mechanics, they were fast and intuitive, and supported the narrative without getting in the way.

Monday, 21 August 2017

Saga of the Goblin Horde: Updated Player's Guide

The Saga of the Goblin Horde setting book is now getting very close to completion. I'm currently working on the tenth (and final) Plot Point episode, and there are a few extra monsters that I'd like to add to the bestiary, but after that it's on to the proofreading and finalizing a few outstanding layout issues, and then it'll be ready. The PDF is currently 102 pages, I expect the final book to be around 110 pages.

I released the player's guide six months ago today, but I've added a couple more setting rules since then (Quick Skirmish and Shenanigans), and also ended up dropping the Critical Failures setting rule. As a few people have expressed an interest in using the new setting rules, I thought I'd take the opportunity to update the player's guide (and fix an embarrassing typo at the same time).


As always, you can grab all the other freebies (34 archetypes, 12 adventures, 8 adventure cards and 5 battle maps) and check out the 3 Actual Plays along with my Wild Die interview here.