Three kinds of wealth abstraction rules

I don't always have the time or the energy to track currency in my elfgames, and although I see the merit in doing so when you're aiming for a specific kind of gamefeel, it's not a great fit for every game. So why is this so often treated as the standard? I mean, it can't be pure nostalgia or blind adherence to the old ways; a lot of the games that still stick with this have traded inventory weight for inventory slots, for instance. Gold for XP could be a plausible reason, but then again, there's no reason you can't implement this with abstracted wealth rules. 

Now, while I can't give you a definitive answer to this conundrum (if there even is one), I have spent some time trying to come up with interesting rules for wealth abstraction, just for fun. If nothing else, perhaps these will inspire some game designers to question why they're still sticking with the ol' Copper/Silver/Gold standard rather than experimenting with fun and less disruptive ways of handling wealth in their games.

WEALTH POINTS

You can spend your wealth points (WP) to add positive modifiers to negotiation checks.

When the party finds treasure, tell them how many wealth points they acquired. A small amount of coins would be worth a single WP for the whole party, while a golden statuette with emerald eyes could earn them as many as 5 WPs.

When you want to buy something, you can make a negotiation check by rolling a d20 vs a Difficulty Rating of...  

• 10 (mundane/cheap items)
• 14 (uncommon/expensive items)
• 18 (rare/exclusive) 

You can bypass a negotiation check entirely by spending a fixed amount of wealth points for each item tier, as seen below: 

• Common/cheap: 10 WPs
• Uncommon/expensive: 15 WPs
• Rare/exclusive: 20 WPs

If you still want to brute force your way through a purchase after a failed negotiation attempt, add +5 to the WP cost. Any wealth points spent on the roll are subtracted from the total cost.

✦ Design notes

So, these rules intentionally put a big emphasis on negotiations over fixed prices. This is meant to represent haggling, rather than how much each item is actually worth. Prices normally fluctuate between stores and different regions IRL, so I thought this was a nice way to incorporate that in a game. And since you always have the option of caving in and paying an exorbitant price even if someone is overcharging you for their wares, I added that bit about bypassing negotiations.

Finally, if I were to implement this mechanic in a game, I'd definitely want to prepare a reference list for treasure and another for typical items, just to keep things fair and easy to run.

WEALTH USAGE DIE

If you want to keep the Copper/Silver/Gold standard but don't want to bother tracking individual coins, you can simply assign an usage die for each. Then, make three item lists: one for things that can be bought with copper, another for items that can be bought with silver, and one for the truly expensive things that only gold can buy.

• Copper can only buy from the copper list.
• Silver can buy from the copper and silver lists.
• Gold can buy from all three lists.

When you want to buy something, roll a copper, silver or gold usage die, as determined by what you're buying. If you roll a 1 or 2, drop the die by a step (d12 > d10 > d8 > d6 > d4 > nil). If you don't have at least a d4, you simply can't afford to buy the things you want.

After completing a quest or exploring a dungeon, the party can potentially increase their wealth usage dice by a step, depending on how much they earned or pillaged. The standard odds for wealth improvement are...

• Copper: 4-in-6
• Silver: 2-in-6
• Gold 1-in-6

The odds above are subject to both positive and negative changes, per the fiction. If the party was promised a fortune in gold, they might have higher odds of improving their gold usage die. If they were simply out in the sewers killing rats, maybe they only get to try to improve copper or silver (not both), with gold being out of the picture entirely. Such is the life of an adventurer.

✦ Design notes

The biggest hurdle to implementing these rules in a game is deciding the starting wealth of PCs. Do you just give them a d4 in copper, in which case they're flat out broke? Are some classes (if you're using those) wealthier from the get go? Are some even poorer? Balancing this out can be fun, but it's the sort of thing that will directly inform how your game feels in play, at least until the party gets some experience under their belts.

GMs can play around with positive and negative modifiers to UD checks, by the way: depending on what you're buying (and from whom), the GM may assign you a positive or negative modifier. This is a good way to represent how cheap or expensive something is, as well as the seller's negotiation skills and their disposition towards the buyer.

WEALTH LEVELS

No rolls, no checks, just a simple Wealth Level (WL).

• At WL1, you can afford common gear, travel rations, simple accommodations, basic services
• At WL2, you can afford quality gear, specialized services, components, luxurious accommodations, weapons, armor, daily wages
• At WL3, you can afford property installments, magic items, monthly wages, horses, livestock

Characters increase their Wealth Level by getting paid for their services, plundering dungeons and undertaking financial ventures. There's no need for hard rules and parameters, either: if it makes fictional sense for a character to be on WL2, then that's their Wealth Level. If they go on a buying spree and overspend, they may drop down to WL1. Easy, clean, simple.

OPTIONAL RULE: if you want to mix gold for XP with these rules, characters can only level up when they reach WL3. Afterwards, they must invest most of their funds into training under a competent tutor, dropping back to WL1.

✦ Design notes

There's no denying that this is an incredibly high trust approach to wealth, bordering on FKR, and that's intentional. If you're completely burned out on currency tracking, this will probably be your favourite take on wealth abstraction in this post. Similarly, this is a great fit for games where wealth doesn't matter all that much, although the optional rule can give it a bit more heft, if that's what you're looking for.

ALL ABOUT THAT CASH

A funny thing happened while I was writing this post: I no longer know how I want to handle wealth in most of the games I'm currently developing. A few of these could be a great fit for some of my games, and indeed, they were built on ideas I initially had for the aforementioned games, but dropped for one reason or another. In a way, I guess this means I succeeded at what I set out to do with this post; I just didn't expect to be on the receiving end of it!

Now if you'll excuse me, I gotta go have a design-induced existential crisis. Those are always a lot of fun!

An exercise in dice pool-based game design

I love rolling large dice pools. Hearing all those shiny math rocks clink, eagerly hoping for a good roll and dreading those pesky 1s is way too satisfying. Sure, rolling lots of dice can be unwieldy and lead to dice clog, but years of playing Vampire: The Masquerade have conditioned me to enjoy the simple pleasures offered by dice pools.

Here's a quick V.V. fact: I write when I'm stressed, and I've had a pretty stressful couple of days. Stressful enough for me to write a pretty solid foundation for a dice pool-based system. Right now, this is just an exercise in game design, but I could definitely see myself using this for a game someday. You can check it out below!

CHARACTER CREATION

One of your Attributes is great (d10), one is good (d8), one is average (d6) and one is poor (d4). Roll four d20s, then assign each result to a different Attribute, forming your Attribute Pools. If no result is higher than 10, discard all results and roll again.

TASK RESOLUTION

Every Attribute has a dice pool, and you can choose how many dice to invest in any given Attribute Check. After investing your dice, roll them. You always keep any dice that rolls at or above 4. When you're out of dice, you can't succeed with that Attribute anymore. 

Degrees of success are determined by how many dice were invested in the check.

• 1 die: you succeed at a cost, such as spending resources or facing complications
• 2 dice: you succeed by doing the bare minimum
• 3 dice: you solve the matter at hand cleanly and competently
• 4+ dice: you go above and beyond, succeeding with gusto. For each die above 3, add a flourish to your success: elegance, quickness, subtlety, precision, substance, surprise

COMBAT: VITALITY

When entering a fight, invest as many dice from your Attribute Pools as you want, forming your Vitality Pool for the combat. 

Every enemy attack has a matching Condition with a Resistance Cost. To avoid suffering a Condition, roll a number of Vitality dice equal to the Resistance Cost. Keep any dice that rolls at 4 or higher, and discard the rest.

If you can't or don't want to match the Condition's Resistance Cost, you suffer its effects.

When combat ends, any remaining Vitality dice can be freely reassigned to your Attribute Pools.

COMBAT: ATTACKING

To deal damage in combat, you need to spend <melee attribute> dice for melee attacks, <ranged attribute> dice for ranged attacks, and <magic attribute> for offensive spellcasting. Roll them normally, and keep any dice resulting in a number equal to 4 or above. Any dice spent this way can be used to assign Conditions to an enemy. Once you reach an enemy's Condition Threshold, you decide whether they're dead or simply defeated.

CONDITIONS

Optimally, a game using these rules would have a full list of interesting conditions, each with a matching Resistance Cost (or, in the case of PC attacks, Damage Costs) and some interesting mechanical flair to differentiate them. As is, this is just the skeleton of a system, and not a game at all. No harm in giving some examples, though!

• Vulnerable (5): -1 Damage Cost to all Conditions
• Weakened (4): Can't cause any Conditions above RC 3
• Wounded (3): Can be inflicted multiple times
• Dizzy (2): Can't attack for a turn (doesn't stack)

POTENTIAL SHENANIGANS

Designing powers for this system would be a blast, as there's so much room to play with dice pools and degrees of success. Hell, I almost bolted a skill system to this thing just for fun, but it felt like too much (skill points would allow rerolls on relevant Attribute Checks, furthering the system's dice clog problem).

At the present time, though, I have no plans on expanding this any further, as I'm already working on way too many games. Still, I'm curious to know whether this is as interesting as my stress-addled brain thinks it is, or just an excuse to roll a lot of dice at once.

Lemme know what you think!

The Wyvern Journals: The Six Masteries

I've been teasing a big post on expanded casting rules for well over a month now, and while I was finally getting ready to write it, the strangest thing happened. I remembered an old magic system I was tinkering with years ago. After re-reading it, I mean, oof. It was rough. There were some pretty cool ideas in there, but overall, I didn't love the execution, which relied on using six different dice to represent six different aspects of magic. Messy as it was, though, I started thinking that maybe, just maybe, it could be compatible with The Wyvern Hack; all it needed was some love and a much needed cleanup. 

I was right. It fit like a glove. Thing is, now I have two different, completely incompatible magic systems, so one of them has to go. 

I vented on Twitter about these first world problems of mine (oh, the irony), and the majority of my moots supported me going with this weird new thing I'm working on, rather than the Vancian-inspired magic system with a tweeeest I was planning on building.

I'm not pulling the trigger on either of them yet, but blogging about the former can't hurt, right? If it sucks, I'll just sweep it under the rug and blog about the latter, too. There's always the possibility that both of them will end up sucking, so I'm not gonna stress about it too much!

CORE ELEMENTS

The Six Masteries, as I've taken to calling this, are centered on two core concepts: a Magic Die, and the aforementioned masteries, named Forces, Divine, Aberrant, Essence, Chaos and Primordial, each corresponding to a different aspect of reality. 

When casting a spell, the magic user declares what they want to achieve with it and how they're going to achieve that, picking an appropriate mastery for their spell. Then, they roll a d6 on said mastery's table, which will determine whether that spell is a failure, a weaker version of itself, a success, a strong success, or if something weirder happens. Each mastery has different, thematically appropriate permutations.

If the spell was a success (regardless of degree), that's where the Magic Die comes in, as it is rolled to determine a spell's duration, damage, area and healing. For utility spells, you assign the results to duration (1/turn), area (2/square or 1,5m) and/or targets (3/extra target). For damage and healing spells, the roll's result determines how much damage you deal or heal, and it can be split between multiple targets. You can use Luck to boost this (I promise we'll talk about Luck Dice soon!).

SPELLCASTING CLASSES

Each spellcasting class handles magic quite differently, both fictionally and mechanically. Mages weave their spells through Arcane knowledge and means, Clerics rely on their Faith to bend reality to their will, while Spellswords use the Craft to shape the world around them. But we're here to talk about mechanics, so...

• Mages use a d12 as their Magic Die. They start the game with two masteries of their choice. They gain one more mastery on level 3, another on level 5, and a final one on level 10.

• Clerics use a d10 as their Magic Die. They start the game with mastery over Essence and the Divine.

• Spellswords use a d8 as their Magic Die. They start the game with one mastery of their choice, gaining another on level 5 and a final one on level 10.

DEPLETION

Rolling a 6 or a 1 on some masteries can deplete your Magic Die. When that happens, you knock it down a tier, and if it is depleted as a d4, then you're deprived. When deprived, you can't cast spells until you take a long rest, after which your magic is completely recovered. Depleted Magic Die are increased by a single step when you take a short rest, up to their original form.

INGREDIENTS AND ARTIFACTS

Ingredients are things like a dragon's petrified gallbladder, graveyard fruits, a nobleman's fingernails or the bottled whimper of a dying man, and they can be spent to adjust a mastery check by 1/each. If an ingredient has a high synergy with the spell you're casting, it can adjust the mastery check by 2.

Magical artifacts can be drained to raise a Magic Die by a step, up to d20. More powerful artifacts can raise them multiple times in a single use. They all have different recharge triggers (blood, sunrise, death, storms, etc). Mages use talismans as artifacts, while Clerics prefer relics and Spellswords are innately acquainted with instruments.

THE SIX MASTERIES

Fucking finally, eh? I won't include all of the mastery tables here, but two should be enough to help y'all visualize how they work, yeah? Read on, fellow wonder weavers.

Forces Mastery

Fireballs, magic missiles, thunderstorms, psychic blasts

1. Your insecurities and fear take hold of you, and you fail to fully exert your mastery over magic. Your spell works, but it is weaker than it should have been. [Roll your Magic Die as if it was one step lower.]
2-3. Everything works exactly as you willed it!
4-5. Some might call it arrogance, but your confidence allows you to surpass your limits, casting an even more potent version of the spell. [Roll your Magic Die as if it was one step higher.]
6. Such greatness is exhausting even for the most revered masters of magic. Your spell has a colossal effect, but you have to knock your Magic Die down a step, lest you lose control of the Forces you're playing with. [If you lower your Magic Die by a step, its resulting roll is tripled. If you don't, the Referee rolls on the disaster table.]

Mastery over Forces deals with pure, raw power, molding magic without a hint of subtlety. No other mastery captures the destructive potential of magic as profoundly as Forces does.

Primordial Mastery

Turning light into darkness, rewinding time itself, teleportation, true resurrection

1. Disaster! Reality refuses to surrender to you, and this spell can never be invoked again.
2-3. You are not yet powerful enough to achieve the desired effect, but your confidence is admirable. Use another mastery to successfully simulate a weaker version of that spell, or give up and temporarily raise your Magic Die by one step.
4-5. The elements are transmuted, gravity is lifted, day turns to night — whatever you intend, it comes true. For now.
6. You reach into the very fabric of reality, and it fights back. Choose between carving your spell into perpetuity and permanently lowering your Magic Die by two steps, fully recovering your Magic Die and failing, or paying a price of the Referee's choosing and achieving temporary success.

In the metaphysical hierarchy of the universe, some elements belong to the surface, while others form the very foundation of reality. Formidable and imperious, Primordial mastery allows its users to shape the essence of all that is, with all the consequences that brings.

FINAL CONSIDERATIONS

I have no idea if this is balanced or fun, but I'm 100% sure some of y'all would (will?) find ways to abuse and break it, much to your Referee's chagrin. That's fine! I wanted to give casters a lot of utility, and I feel like I achieved that goal. Their damage potential, on the other hand, can't compare to a Fighter's, which is completely intentional. I'm bored of combat casters. I'll take reality warpers any day of the week, because I want my magic to feel alive, weird and expansive. 

This feels like a step in that direction.

The Wyvern Journals: Dissecting the Character Class Model

The Wyvern Journals is the title of what is (hopefully) going to be a series in which we dissect several aspects of my OSR fantasy heartbreaker, The Wyvern Hack, while discussing the decisions behind them. Theoretically, this is already part 2, since the "announcement" post already introduced TWH's core combat rules, but I'm sure we'll revisit those later on. This post, though, will focus on the character class model. I have already posted a couple of class spreads on Twitter, but rather than diving in the specifics of those classes, this is a more general take on how every class in The Wyvern Hack is structured.

CORE ELEMENTS

When push comes to shove, dividing the character class model into its core elements is a lot more efficient than discussing it as a whole, so that's where we'll start. Afterwards, we'll do an individual dive into each element.

1. The Intro Blurb
2. Class Icons
3. Traits
  3.1. Starting Hit Points
  3.2. Trait: Key Attributes
  3.3. Trait: Starting Dice
  3.4. Trait: Typical Backgrounds
  3.5. Trait: Starting Bonuses
  3.6. Trait: Experience Triggers
4. Starting Weapon
5. Special Abilities
6. Personal Table
7. Background Table
8. Starter Kits
9. Progression Table

If you're like me and love visual references, you can find the numbered elements above on an example spread right here.

1. THE INTRO BLURB

Apocalypse World did it best, but I've always been a fan of intro blurbs for classes, playbooks and even clans (or tribes, traditions, kiths and all the rest of WoD's not-classes). They're often essential in helping my AuDHD-ass pick something to play, breaking that damn decision paralysis. Adding these to TWH was a no-brainer! 

The goal here was to give the reader a quick look into the class' flavour, while also setting the tone for everything that comes after, even for myself. If you liked the intro blurb of a class, odds are you're gonna like its Traits, Special Abilities, starter kits and progression. This is usually the part I write first, and aside from everything else, it's supposed to build some hype. For the reader, that is. I'm definitely not hyping myself up with these. Scout's honor.*

2. CLASS ICONS

Much like the intro blurb, this serves the purpose of letting the reader know the kinds of characters they could reasonably play with any given class, while also potentially giving them something to get excited for. Spotting a reference to one of my favorite characters in an RPG tends to instantly get me in the mood to play a similar character, and I'm hoping this applies to some readers, too.

3. TRAITS

This is a meatier section than the previous ones, and although it carries a lot more weight when it comes to gameplay, I personally find it a lot easier to write. Starting Hit Points, for example, are just a matter of either combining two Attributes, using the class' starting Hit Dice's highest possible result, or comparing that with an Attribute (usually Constitution) and picking the highest/lowest, depending on the class.

Key Attributes are a little trickier, and they represent the two Attributes that always have a chance of being improved when a character levels up — the player rolls a d20 for each, and if the result is higher than the Attribute's current value, they increase it by 1. Players can also roll a third Attribute of their choice, but we're getting sidetracked! Levelling up and progression deserve their own blog post, and this ain't it.

Starting Dice are already outlined in the progression tables (the very first thing I did for every class, back when I first started fiddling with TWH's combat). Want to kick some ass in melee/ranged combat? A higher Attack Die will go a long way towards that. Want to recover from an ass-kicking in a timely fashion? Well, that's what your Hit Dice are for. Luck will get its own blog post in the future, but suffice to say that Luck Dice are pretty versatile; the higher, the better.

Typical Backgrounds are pretty much just flavor. So far, I don't have any plans to meaningfully implement these backgrounds as a mechanic in The Wyvern Hack, and I'm not sure I see the need to. As is, they can give the players some ideas for character concepts, and that's good enough for me.

Starting Bonuses are part of the "ctrl+c + ctrl+v" family, in that they're already available in the progression tables. Still, these can be useful for knowing straight up how much damage you can count on dealing/resisting right out of the gate.

Experience Triggers are the hardest Trait to get right, and they're also something I love doing! Again, I won't get too deep into levelling up and progression here, but you can expect an experience track similar to PbtA and FitD games, which will be filled by hitting your class' triggers once a session. While I'm generally wary of any mechanic that incentivizes players to take certain actions just for the sake of gaining experience (or any other in-game reward), my aim with these was to stay close to what someone playing a certain class will want to do anyway. Fighters, for example, will get experience when they get new scars (something that's more likely for characters on the frontline) and when they win a battle. Limiting trigger activation to once per session also helps prevent intentional experience farming.

4. STARTING WEAPONS

Some players will hate that, while others will love it, but I personally really enjoy randomly generated equipment. The Wyvern Hack doesn't randomly generate every piece of equipment, though (see: starting kits), since this can slow character creation down to a crawl, depending on the amount of items you're generating and the number of tables you're consulting, but a random starting weapon can be a lot of fun, and it might surprise you! Getting a high roll on a starting weapon's damage is a nice treat, after all. If you really hate what you rolled, though, no biggie. All classes have starter kits with extra weapons and/or some coin for you to spend on equipment in-game.

5. SPECIAL ABILITIES

This is where you'll find the very soul of each and every character class. Sure, classes have plenty of differences besides these, but Special Abilities are the things that make them truly unique, presenting the players with the tools through which they'll interact with the world. All of the Fighters' Special Abilities are related to combat, for example, while the Dungeoneer is exclusively focused on utility, exploration and, well, dungeon crawling. These not only communicate what the class will excel at, but also let the players know which class will be better suited to their preferred playstyle.

6. PERSONAL TABLE

My absolute favorite part, right there. These are a combination of a personal question and a d6 table, which will always award the character with something, while also fleshing them out a bit. Giving mechanical weight to these tables is loads of fun, too!

7. BACKGROUND TABLE

While not nearly as involved as the previous step, this is just as fun. The key part here, though, was to give every character a cool hook, while still being open enough to avoid getting boring if you're frequently rolling up characters of the same class. Challenging, sure, but I'd like to think I'm doing okay so far.

8. STARTER KITS

I have a love/hate relationship with these damn kits. They're mostly made to fit typical/iconic character archetypes, but coming up with the archetypes themselves is a pain in the ass. Once I have a clear idea of what I want out of each kit and what they're meant to represent, though, the process becomes surprisingly enjoyable!

9. PROGRESSION TABLE

Back when I was still trying to figure out what The Wyvern Hack's combat was gonna be like, before I even knew this was gonna be a thing at all, the first thing I did for fun was a bunch of progression tables for the more famous classes (Fighter, Spellcaster, Rogue and Cleric). These have changed a little since then, and I've cleaned up some of the math (huge thanks to @BourassaSam for spotting a massive issue with the modifiers), but the work itself is already over and done with.

Design-wise, these aren't a big mystery, right? They were inspired by classic OSR progression tables, and while the contents are different, the purpose remains the same. The most challenging part of making these was preventing character progression from feeling "samey" across the classes. Special Abilities are a big help, of course, but if a Rogue had the same basic progression as a Fighter, then they'd both lose a bit of what makes them special. Luck played a key role in this!

CLOSING THOUGHTS

I'm on the fence on whether this raised more questions than it answered or not, but I hope this helped shed some light on the process behind creating The Wyvern Hack's classes, and on the purpose of each of the aspects we dissected above. The next few parts of this series will probably focus on specific classes (or maybe even heritages/ancestries, who knows), and I'm looking forward to discussing those!

* I've never been a member of the scouts.

I started writing my own fantasy heartbreaker, and it's all Prismatic Wasteland's fault!

The title says it all, really. Have you ever been so inspired by a blogpost that you immediately started writing a brand new elfgame? Because folks, that's where I'm at right now. Prismatic Wasteland's rehabilitation of the To-Hit roll touched on an aspect of TTRPG combat that never quite worked for me. Automatic hits are cool, don't get me wrong, but they often still produce low/no damage hits, depending on the system, and that's almost as unsatisfying as missing. 

The ambiguity of Hit Points only makes things worse, in my experience. Some people see them as a character's health and damage as wounds (which is unfeasible in the long run), but personally, I like them better as Hit Protection, as exemplified by Cairn. This abstraction of how long a character can safely avoid a truly serious hit is much more satisfying to me than actually treating each and every lost point of HP as an injury.

And with that in mind, I started tinkering just like Tony Stark in that damn cave, but instead of scrap, I had pure gold to tinker with. Thanks, Warren.

ATTACK CHECKS

To make an attack check, roll your character's Attack Die. If the result is higher than the opponent's Defense, they lose an amount of HP equal to your base damage. If the roll’s result is lower than their Defense, you only deal half your Base Damage to their HP, rounded down.


Enemy attack checks are made with their Attack Die against the PC’s Base Defense. Rolling above it deals their full Base Damage to the character’s HP, while rolling below it does only half their Base Damage, rounded down.

Sometimes, it will be impossible to overcome the opponent's Defense with your attack die (e.g. d4 against 6 Defense). In this case, just apply half your damage to their HP normally, without rolling dice. The same goes for enemies.

Quite simple, yeah? What I tried to achieve with the rules in the excerpt above was a compromise between to-hit and auto-hit, while removing those pesky whiffs. You're always gonna deal some damage to the enemy's Hit Protection, you're always gonna soften them up a little. Defense, then, isn't a way of negating hits, but an abstraction of how good someone is at delaying the inevitable, and how much their armor can help them with that.

For clarity's sake, Base Damage is determined by adding the character's Attack Bonus (tied to class-based progression) to their weapon's damage. Base Defense works much the same way, adding the character's Defense Bonus to their armor's defense. That, of course, brings us to weapons and armor rules.

WEAPONS, ARMOR AND DURABILITY

To determine a weapon’s damage or a piece of armor’s defense, simply roll its damage/defense die once after purchasing, forging or finding it. The result is not permanent and can be increased by blacksmiths or decreased by excessive use.


At the end of a combat, if you rolled a 1 on any attack check, roll your weapon's Usage Die. If you suffered damage during combat, also roll the Usage Die for your armor and/or shield. Results of 1 to 2 reduce the damage or defense of the equipment corresponding to the die. 


The base price to recover defense points lost by a damaged weapon or armor is equal to ⅓ of its total value, rounded down. The price for improving the damage or defense of a weapon or armor by 1 point is equal to ½ of its total value. Blacksmith skill and special circumstances may increase or decrease both the price and the efficiency of the service.





Have I mentioned how much Prismatic Wasteland's blog influenced this? The coolest part of these rules was lifted straight from his blogpost! I just added durability and some tables. Speaking of which...

Fresh off the layout test!

Now, what use would those rules be without a list of weapons, armor and shield?

Kindly ignore the gibberish placeholder prices, please. I'm postponing those for as long as I can, lmao.

While writing this post, I realized I have yet to translate my armor and shield tables to English. Oops. I might update this later with them. Or not! My memory is rubbish.

INITIATIVE, DYING AND TACTICAL DEPTH

If you're curious about how I'd handle Initiative with these rules, then look no further than my previous blogpost! I'm still not 100% set on how I want to handle death, though, but one thing's for sure: lingering wounds after 0 HP are gonna be a thing, with "negative" HP being added to a roll on a lingering wounds table.

As for tactical depth, well, those of you who follow me on Twitter may be aware of my plans for a big two-parter post on expanded combat maneuvers and magic rules. Those are still happening, rest assured, and they're gonna play a big part in whatever comes out of this lapse in judgement (which has a tentative name already).

THE WYVERN HACK? REALLY?

I swear to god this came to me in a dream or something. It's (probably) not final. It's not original at all. I'm not even sure if it's good! 

So, what is The Wyvern Hack? Above all else, it's a marriage between my two favourite playstyles. NSR sensibilities with a PbtA bent. It's also a collection of procedures and random tables I made throughout the years, and an opportunity to put my own spin on some classic elfgame classes (check out the Dungeoneer!). And it's yet another fantasy heartbreaker with a generic name.

Still. A name is a powerful thing. It gives things purpose. Drives them forward. It inspires. If this project has any chance in hell of taking flight, that's what I'll need to be: driven and inspired.

And you know what? I always thought wyverns were much cooler than dragons anyway.

Momentum Initiative: because combat can be strategic *and* fast!

The Initiative discourse is doing the rounds on Twitter again, but rather than chime in with a thread, I opted for something a little more permanent. Still, this will be a quick one!

Let's get the obvious out of the way: individual initiative feels like what @SprintingOwl aptly named dice clog. Side-based initiative, meanwhile, tends to sacrifice some tactical depth for speed. Popcorn initiative, while cool, can be easily abused. All of this has been discussed to death, but what about solutions?

Personally, I'm fond of what I've taken to calling Momentum Initiative. It's pretty simple:

• At the start of each round, roll a d6 to determine which side gets to act first (1-3, it's the PCs, 4-6, it's the enemies).
• If the player characters got the first round, they get to pick which PC will act first. If not, the Referee picks an enemy to act first.
• Whoever got to act first will then pick who goes next, regardless of side — a PC could pass the torch to another PC or to an enemy, and vice-versa.

"Wait a sec, V.V.", you might be thinking, "that's just a mix of popcorn and side-based initiative!". And hell, you'd be right... that is, if it wasn't for The Twist™ below!

• All enemies start the combat with a number of Momentum charges equal to their HD.
• Momentum charges can be spent to 1. act immediately, 2. inflict Disadvantage to an attack roll, 3. activate powerful abilities*, or 4. take an extra action at the end of the round.
• Enemies regain charges when 1. they get a critical, 2. they kill a character, 3. they succeed in a morale check, and 4. when they are attacked by multiple PCs in succession. Only a single charge can be recovered each round, no matter how many times this is triggered. Enemies can never have a higher number of charges than their HD.

The addition of Momentum is meant to prevent the players from abusing popcorn initiative and turning it into just another version of side-based initiative. In my experience, this actually gives them an incentive to avoid ganging up on a single enemy, lest they fill them with Momentum charges. 

Now, one might argue that these Momentum charges are yet another thing for the Referee to track, and while that is indeed true, the tactical depth they add to combat can be worth the extra bookkeeping. Besides, if you're already tracking HP, this shouldn't be such an increase in cognitive load, anyway.

* I'm very fond of making a d6 list of possible actions an enemy might take in combat, which usually includes lower odds for activating specific abilities than for attacking or doing some weird, enemy-specific shit. Momentum allows enemies to spend charges to trigger these abilities whenever they want, though, bypassing the bad odds. If you're not using anything even remotely similar to this, please ignore that option!

Better Rules for Maritime Adventures

To be brutally honest, I don't think I've ever read any OSR/NSR rules for naval combat and seafaring turns that didn't feel like a) they belonged in an ancient wargame or b) the designer's heart just wasn't in it, and they just wanted to get over and done with that part of the game as soon as possible. And as a fan of vikings and pirates, I always felt like this was such a disservice to something that could be just as fun as regular overland travel or dungeon exploration, both of which have been done superbly in several OSR/NSR games. 

The great thing about the OSR and the NSR alike (I'm still trying to figure out whether there really is a need for such a distinction, but I digress), though, is that when something hasn't been made yet, there's this strong encouragement to go ahead and do it yourself. So I went and did exactly that. Now, the title is presumptuous as hell, I know, but I really do believe these rules are pretty cool. They were heavily inspired by classic dungeon crawling procedures (such as OSE's) and by Apocalypse World 2e's vehicle rules and moves — a weird combination, for sure, but then again, most of my stuff is a mix of classic OSR and PbtA anyway. 

Time to dive in, mateys.

BUILDING YOUR SHIP

All seafaring vessels are described through the following attributes: Size, Speed, Handling and Hull. By default, every vessel has a score of 0 in these attributes. A ship’s Size category also affords it with a number of Armaments and Improvements, as seen below.

Size 0: Boats or rafts, for example. 1 Improvement, no Armaments.
Size 1: Small longships or sailing ships. 2 Improvements, 1 Armament.
Size 2: Transport ships or small galleys. 3 Improvements, 1 Armament.
Size 3: Large longships or sailing ships. 4 Improvements, 2 Armaments.
Size 4: Large warships or large galleys. 4 Improvements, 3 Armaments.
Size 5: Heavy warships or longships. 5 Improvements, 3 Armaments.

Any ship larger than Size 5 gets +1 Armaments for each number above that. Armaments can always be traded for further Improvements, and vice-versa.

Improvements are used to increase the ship’s attributes (except Size). Aside from its use in naval actions, Speed is also factored as an abstraction of how many hexes (or how many increments of 6mi) a vessel can cross in a day. Much the same way, Hull can be used as an abstraction for the ship’s maximum number of passengers and its cargo limit, with each point of Hull counting as 10 to 50 passengers (crew included) and 20 to 100 tons at most.

For the purposes of naval combat, Size counts as Hit Dice and should be rolled to determine the ship’s Hit Protection. Armaments start at d6 damage, but one can spend an Improvement point to increase that damage by a step. Speed is used to determine combat Initiative, and ships with the same Speed rating act simultaneously. Speed can also be used to determine the amount of squares a ship can cross in a combat grid per turn, if one is being used.

NAVAL ACTIONS

There are a number of actions a ship’s crew can take during their turns at sea. These actions can be undertaken by any member of the crew, but it is a good idea to assign functions among the party, such as captain, boarding leader, navigator, engineer and quartermaster.

• Undertake a journey: For each six miles of travel, the crew should make the following checks: Dexterity, to deftly keeping their ship on the right path, Wisdom, to properly determine what path that is, and Charisma, to keep all spirits high.

Failing any of these checks results in a 2 in 6 chance of triggering an encounter (DEX or WIS) or an event (CHA). In addition, failing the Dexterity check also halves the distance traveled, while failing the Wisdom check has a 2 in 6 risk of leading the ship the wrong way (roll a d6 to determine direction: 1. north, 2. northeast, 3. southeast, 4. south, 5. southwest, 6. northwest). 

Encounters should be rolled on an appropriate maritime encounters table, while events function much like a normal encounter, but with a table of situations pertaining only to the ship’s crew and their circumstances.
 

• Navigate perilous seas: In order to safely navigate troubled waters or obstacles, a crew member must roll under either their Dexterity or Wisdom, whichever is higher. They subtract the ship’s Handling from the result.
 

• Attack: When naval combat is initiated, the crew can make one attack for each of their Armaments. Crew members operating ballistic weapons must succeed at a Dexterity check, while ramming requires a Constitution check from the navigator in order to prevent their own ship from suffering any damage. Unconventional weapons such as Greek fire should trigger Wisdom checks. 

Although the brunt of the damage is always suffered by the ship itself, the enemy vessel’s crew always has a 2 in 6 chance of individually suffering half of the total damage dealt to their ship.
 

• Defensive maneuvers: When trying to avoid or minimize the effects of an enemy ship’s attacks, the navigator can check Dexterity to outmaneuver the attacks, or Constitution to bear the brunt of it. Succeeding at a Dexterity check ignores the damage entirely, while succeeding at a Constitution check halves it and eliminates the possibility of damage spillover to the crew (2 in 6 chance of individually suffering half of the total damage received by the ship, as above).  

Defensive maneuvers can also be used to avoid boarding. To do this, the navigator must pass a Dexterity check.

• Board: All it takes to board a ship is being close enough to it and passing a Dexterity check (done by the navigator). Once a ship is boarded by a crew, maritime adventure rules cease to be the focus, being replaced by regular combat procedures in the case of a fight or by a diplomacy challenge.

• Emergency repairs: When plugging holes, tying ropes or putting out fires, a crew member can check Intelligence to devise a workaround for the ship’s current maladies. Succeeding at that check restores d8 HP to the ship.

• Overtake & outdistance: When trying to overtake or outdistance a ship or sea creature outside naval combat, the navigator checks Dexterity if relying on their vessel’s Speed, or Wisdom if betting on its Handling. They subtract either Speed or Handling from the result.

SAMPLE SHIPS

Below are some examples of ships built with these rules.

• Skeid longship

Size: 3
Speed: 2
Handling: 1
Hull: 2 (45 passengers, 80 tons at most)
Hit Protection: 17 (3 HD)
Armaments: Archers (d6), spearmen (d6), ram (d6)

• Man-o'-war

Size: 5
Speed: 1
Handling: 2
Hull: 3 (200 passengers, 300 tons at most)
Hit Protection: 28 (5 HD)
Armaments: Heavy ballista (d8), light ballista (d6), ram (d6)

• Trading cog

Size: 2
Speed: 2
Handling: 1
Hull: 2 (60 passengers, 240 tons at most)
Hit Protection: 10 (2 HD)
Armaments: Archers (d6)

ON ABSTRACTIONS

There are a lot of abstractions here, and that's intended. Personally, I feel like trying to simulate the exact speed with which a ship travels in a good or bad day is a losing battle. There are just too many variables, and rather than making the game feel grounded, this just grinds it to a halt. At the end of the day, those "exact" measurements are still abstractions. They're just crunchier and less intuitive than they need to be, oftentimes for the sake of appearing realistic.

And with that said, I'll leave y'all with an epiphany I had while writing this post: these rules can be just as easily used for airships, with little to no adjustments.

Fair winds and following seas to all!

Adding Procedures & Random Tables to Vampire: The Masquerade, Part 3: Court Creation & Faction Play

You can't have courtly intrigue without a court, and the truth is, Vampire: The Masquerade barely provides you any tools to create one. Time to change that. While part 1 of this series gave you the tools to create a city of your own and part 2 made it easier to populate it, part 3 is where your sandbox will truly come to life. We'll start from the very bottom, diving into the personal connections that weave webs of intrigue and moving up to coteries before finally exploring some procedures and mechanics for faction play.

THE TIES THAT BIND

Every important NPC should have three personal connections to other NPCs (or even the PCs): one with a powerful figure, one with a coterie-mate, and one with someone from a different faction. At least one of those relationships needs to be negative, and at least one needs to be positive. Roll or choose on the d66 table below.

Here's an example:

Vincenzo Vallone is a Hecata fledgling with the Thrill-Seeker Archetype. He is just and greedy, favouring trendy fashion, and he craves revolution. He was a disgraced gangster before the Embrace, which was an act of hate. His appearance is marked by thick hair, venomous eyes, and his friendly tone.

Figure of power: He is a thrall to his sire, Giancarlo Putanesca, entrapped by a full blood bond.
Coterie-mate: Vincenzo is indebted to Sniffer, a Nosferatu detective, who welcomed him into their Anarch coterie.
Inter-faction connection: The Toreador Prince, Alanis Whitehall, considers the fledgling an inconvenience, as his clan's very presence is unwelcome in her city.

Establishing these relationships can be tedious, but the payoff is worth it. Once you know who a character's enemies and allies are, it becomes a lot easier to involve them in your city's conflicts. If anyone threatens Sniffer, Vincenzo will be there for him. If the PCs need support against the tyrannical Prince Whitehall, the Hecata fledgling may be willing to stand with them. Instantly gameable, right?

Do note that this isn't meant to be the first step of court creation; it's better to do this once you've already generated all coteries, at the very least. The only reason we're discussing personal connections before coterie creation and faction play is scale — as in, it feels more natural to start at the personal level before moving on to the big stuff.

COTERIE CREATION

Before we start working on your city's coteries, let's get one thing out of the way: while PC coteries should always strive to have functional relationships between all members (as Vampire is still a collaborative storytelling experience, in spite of its themes), the same isn't necessarily true of NPCs. A little inner strife can do wonders for making NPC coteries feel alive and vibrant.

The first thing you should do when creating a coterie is decide its size and its political importance. Naturally, I made a table to help you out with that. Roll or choose away!

Once that's over and done with, it's a good idea to find what the coterie's purpose and focus is. The table below should help you with that, but if you want a coterie to be something else that isn't included in the table, no biggie! As long as there's common ground and/or a shared goal between the coterie's Kindred, it's all good.

And that's it! You can now start creating the individual members of each coterie. My Perchance generators can help you with that, and part 2 of this series goes more in depth into that process, too. If you're following the tables and procedures from part 1 while creating your sandbox city, it's a good idea to stay below (or at least around) the maximum number of Kindred that can be safely sustained by your city's population, but overpopulated and underpopulated cities can both be very interesting, too.

FACTIONS 101

Credit where credit is due: these mechanics were heavily inspired by Mindstorm's blogpost on the subject, as well as Remember Tomorrow's faction mechanics. It's a remix of those, really, with a bit of tailoring for Vampire. 

Now, "faction" is sort of a loaded word when it comes to Vampire: The Masquerade. It could mean anything from the sects, to blood cults and even powerful coteries. My personal definition of "faction" includes all of those things and more, as a politically-aligned group of people (or Kindred) who share the same goals. Ideally, you should only turn a group into a proper, statted out faction if they hold at least some sway over the city, or if they have the potential to. Otherwise, they're just a regular coterie or group, instead of a faction.

FACTION ANATOMY

When developing a faction, you should start by looking at your city's lore, its Domains and their rulers, the main coteries and interesting connections between NPCs. Following the procedures from part 1 will automatically give you a few factions to start with, but if you're only interested in faction creation, you can roll or pick on the faction table¹, using the Appetite table to find a goal for your faction. 

Once you have at least an idea of what the faction is and what they want, you're ready to stat it out. Giving it a cool nickname/title is always nice, but that's optional. Each faction is comprised of three Fronts: Warfare, Influence and Capital. They each have an associated d10, which is what you'll be rolling during faction play (more on that later). Faction strengths and weaknesses are represented by Assets and Flaws, respectively, which can add Advantage or Disadvantage to certain faction actions (and that works exactly like you expect it to work).

Here's an example of a faction stat block:

• The Broken Tower (Camarilla offshoot)

Members: Prince Alanis Whitehall, Paris Johnson, the Sheriff, Daisy Mae and Wilhelm, the Harpies, and Primogens Wayne, Callum and Jazz.
Goal: The complete subjugation of every other faction in the city.
Fronts: Warfare [-1] Influence [0] Capital [0]
Assets: Popular Elysium [Diplomacy], Blood Trafficking [Bribe]
Flaws: Weak Sheriff [Attack], Unlikable Prince [Recruitment]

Don't worry about balance. Kindred society is unfair by design, so why should faction play be fair? If you feel like a faction should be far stronger than the others, then give an Asset to each of their Fronts; as long as they still have a Flaw, that's peachy keen. If you feel like a faction should be weaker, stat it with several Flaws and perhaps a -1 on a Front or two. When in doubt, use the fiction to dictate the stats.

FACTION ACTIONS

Each Front can perform three distinct actions, as seen below.

 

Warfare actions are invariably offensive, representing direct attacks against enemy forces and strongholds, strategic surveillance of their movements, numbers and plans, and the underhanded destruction of their troops, equipment and bases. If the Sabbat storms an Elysium in the middle of court, they're launching an Attack against the Camarilla. When they use an infiltrator to spy on the Prince, they are engaging in Reconnaissance. If they plant explosives in the Sheriff's haven while he's out, they're partaking in Sabotage.

Influence actions cover key aspects of social maneuvering, such as forming alliances, bolstering the faction's ranks with fresh blood and spreading (mis)information through the city. If the Camarilla appoints a dissenting Toreador ancilla to the Primogen, they are using Diplomacy. If they allow each Kindred on the Primogen council to Embrace new childer, they are starting a Recruitment drive. When they spread footage of the Anarch Baron mistreating a fledgling, they are disseminating Propaganda.

Capital actions concern the management and application of a faction's resources, like investing in worthwhile endeavours, acquiring any equipment, building or services deemed useful, and buying favours, information or even loyalty. If the Anarchs offer to lend some of their guns to the local Duskborn, they're making an Investment. If they buy a huge supply of blood bags from a neighbouring city, they decided to Procure it. When they pay the neighbourhood's security firm to turn a blind eye to their comings and goings, that's obviously a Bribe.

ROLLING AND REWARDS

When one of a Front's actions is used, roll a d10. A result of 6 or above is a success, while a result below 6 is a failure (the consequences of which we will discuss in a bit). Before a faction executes an action, though, you should first determine which Reward they want, selected from the list below.

Rewards should always be rooted in the fiction. If a faction is trying to neutralize a Flaw, then that needs to be reflected in the fiction somehow. If you can't justify how a certain action results in a specific Reward, then perhaps it would be better to choose a different, more fitting reward for that action.

Failing a roll doesn't result in catastrophe; rather, the faction simply doesn't get the Reward they were looking for, and the fiction should reflect that. Sometimes, a failed attempt at assassinating the Prince's favourite childe can be even more exciting in play than a success.

GAME OVER, MAN

If one of a faction's Fronts ever falls below -3 and that Front already has a Flaw, then that faction is eliminated from faction play. That doesn't mean they simply vanish from the fiction, although that is a possibility. What this is meant to represent is that they simply don't have enough political power to keep playing with the big kids. The faction's remaining members could opt to join other factions, perhaps even becoming prime recruitment targets. 

Or, you know, they could all meet the Final Death. Whatever tickles your fancy. 

QUICK REFERENCE

• To execute a faction action, choose a Reward and roll a d10
• If the Front used for the action is damaged, subtract the modifier from the result
• If the result is below 6, the faction simply doesn't get the chosen Reward

• When a Front suffers damage, the faction adds -1 to any further rolls with that Front
• Factions can only remove damage from Fronts without Flaws
• Fronts can only be damaged up to -3
• If a faction's Front is damaged at -3 and it already has a Flaw, the faction is eliminated

• Relevant Assets grant Advantage (roll 2d10, keep the highest die) to an action type
• Each Front can only have one Asset
• Assets can only be destroyed when their associated Front is already damaged

• Relevant Flaws grant Disadvantage (roll 2d10, keep the lowest die) to an action type
• Each Front can only have one Flaw
• If a Front doesn't have a Flaw, the faction can take one to negate incoming damage
• It is impossible to remove a faction's last flaw

FACTION PLAY

There are a few ways to go about faction play, and none of them are wrong, per se. Call it a matter of taste.

The first is keeping faction play as a side activity for the Storyteller, something they do between sessions to spice things up in the city, allowing a few factions to pick an action. There shouldn't really be any hard rules to which factions should get an action, though the fiction will often inform these decisions. If the PCs are part of a faction taking an action, you can give them the option to support that action. They count as an Asset for the purposes of that roll.

The second is allowing the players to take control of a faction, while you control the others. Their PCs should ideally be part of the faction they're controlling, in order to avoid conflicts of interest. If you go with this option, you should probably engage with faction play either before or after actual play (that is, at the start or end of the session). You could do both, too. Whatever works for you and your troupe!

The third is a spin on the second; rather than controlling a single faction as a group, each player gets to pick one faction. Conflicts of interest are probably going to be inevitable, but this has the potential to be loads of fun! Other than that, this should work exactly like the alternative above.

FINAL NOTES

On occasion, it might not be immediately clear which action fits what a faction is attempting in the fiction, and the best way to ascertain that is by looking at their desired rewards. Going back to one of the action examples, if the Anarchs wanted to Develop the Duskborn coterie as an Asset (like, say, Duskborn Shocktroops), then they wouldn't really be Investing, they'd be Recruiting. But if they wanted to Accomplish something in the fiction (like diverting the Camarilla's attention towards the well-armed Duskborn), then that's definitely an Investment.

Faction Fronts, Assets, Flaws and even goals are inevitably going to be altered in the fiction due to the PC's actions outside of faction play, and that's okay. Make any necessary adjustments and move on. Faction play is meant to be an add-on, not the main course, and anything that happens during actual play takes precedence over it.

¹ The offshoots from the faction table are meant to represent local schisms — rolling a Camarilla faction and a Camarilla offshoot, for example, could represent a city contested by two Princes. This could also be interpreted as deviations from sect norms, resulting in things like Anarchs with wildly different political structures (think a Parliament rather than a Baron) or unusual traditions.