This is part 14 of 18 of the series: Hacking New Rules

Drowning in Armor Systems (Part 2)

Print Friendly, PDF & Email

A few weeks ago, I decided that, since I was starting a new D&D campaign, I might as well redo the entire equipment system in Dungeons & Dragons. Remember that? Well, I told you I was redoing the armor table. But I didn’t stop there. I redid armor and weapons, and I even changed the way the game handles spellcasting focuses. And that’s how a simple campaign ended up with a 60 page Player’s Guide. Seriously. And if you support me on Patreon at the Frienemy level and have access to my Secret Stash, you got to see just how bonkers I am. I shared the whole document in there.

All the rest of you know is that I was rewriting the armor system. And when we last talked about it, I had built an armor table that seemed really good. Except that it was utter crap. I pronounced it kludge. That’s the word for a solution that is too complicated for the problem it’s solving. Remember this table? Or something that looked like it?

Yeah. It’s ugly as hell, isn’t it? Imagine recording all of that on your character sheet. Unless the character sheet has spaces for all of those particular skills, that would all be a b$&*% to record, wouldn’t it? Okay, as we’ll soon see, that’s not the best measure. But it’s a good measure. Anyway.

When it comes to designing stuff, there’s more to it than just, well, designing stuff. There’s also testing stuff. And I’m doing that right now in my home game. I’ll let you know how it goes unless I forget. Which I will. Because I always do. But beyond designing stuff and testing stuff, there’s also cleaning stuff up. Because – and this is true of everything – the first draft of anything is s$&%.

In this second and final part of my two-part series on overcomplicating the armor system for reasons that seemed good when they were in my head, we’re going to clean up and finalize the design. And we’re going to focus on two things: elegance and extensibility. So, let’s clean up our s$%&!

Extensive, Elegant S$&%

I have talked numerous times about the twin game design concepts of complexity and depth. Complexity refers to how many things a player has to learn or know or remember to play your game or use your system. To choose a really easy and obvious example: in Dungeons & Dragons (5E) the fighter class is less complex than the wizard class. To play a fighter, you don’t need to keep track of as much s$&% as you do to play a wizard. Fighters have a very small number of simple abilities. Even that fighter with the stupid pile of dice and the weird abilities that are powered by dice is simpler than the wizard with his spell preparation, pile of spells to choose from, shorter pile of spells to prepare from, and short list of spells to cast using spell slots of various levels or using the ritual casting option if the spell allows. Wizard players have to know more, remember more, and keep track of more than fighter players do. In general, complexity makes your game harder to learn and more challenging to play. Higher complexity games demand more brain power and record keeping and have a steeper learning curve.

Depth refers to how many different ways the game can go depending on the decisions the players make. Chess is a deep game. There’s a lot of ways the game can go. Especially compared to a game like Candy Land. All games of Candy Land pretty much look the same. And Dungeons & Dragons is way deeper than Chess because it is so open-ended compared to Chess. Depth is what keeps a game interesting and exciting and what makes it worth playing over and over. Games lacking in Depth, like Tic-Tac-Toe, get boring quick.

So, you want depth, but you want to avoid complexity. And that’s a problem because, in general, complexity helps CREATE depth. Chess is deeper than Candy Land partly because the game is more complex. But it’s not always a one-to-one trade. Sometimes, you can get a lot of depth from a small amount of complexity. Consider Go. Or Othello, which is what they called Go when I was a kid, and my dad taught it to me. Othello was advertised with the tagline “a minute to learn, a lifetime to master” because the rules themselves were simple, but the game itself involved complex strategies. Which is why it lasted so long.

And that’s where elegance comes in. A game element – say a specific rule or system – is elegant when the element adds depth to the game without adding much complexity. A mechanic can be elegant for a lot of reasons. It can be simply because the rule is simple. Or it can be because the system is useful for lots of different things. When they brought out D&D 3E, they introduced the d20 Core Mechanic. That was a rule which said, “whenever a creature tries to do something, the player or GM rolls 1d20 and adds an ability modifier and then compares the result to a fixed difficulty number.” Previously, D&D had had different rules for attack rolls, saving throws, non-weapon proficiencies (if you were using them), reaction rolls, morale rolls, surprise, initiative, bending doors and lifting gates, and surviving resurrection. The d20 Core Mechanic was elegant because it worked for lots of different things. And because it didn’t require a whole lot of brain space. Though it could get complex when there were a lot of modifiers.

The d20 Core Mechanic was also extensible. A mechanic is extensible when new stuff can be added to it easily to make it do new things. You could extend the d20 Core Mechanic by adding a new ability score to cover a whole range of new actions. Or by adding new modifiers for different situations. You could require multiple rolls before the success was really a success. Or the actual result on the die could mean something special in some cases. Or the difference between the result and the target number could be assigned a meaning. Right? D&D has used all of those options in different places in its rules.

A mechanic doesn’t HAVE TO be elegant. It doesn’t HAVE TO be extensible. But both of those are good things. Elegant mechanics add depth – making the game more fun – without adding much complexity – making the game harder to play. And extensible mechanics can do more than the one thing you designed them to do. Which means you get a lot more out of them. It means that the design work you put in now will allow you to design more stuff in the future more easily.

When a mechanic is both reasonably elegant and reasonable extensible, I call it a LOADED mechanic. It’s a mechanic that you can get a lot out of. Loaded here means that has a lot on it, like a fully-loaded pizza. It does mean the mechanic will accidentally kill people if you point it in the wrong direction, like a loaded gun.

And just like pizzas are always better when they are fully-loaded, mechanics are always better when fully-loaded. So after I’ve got a working first draft of a mechanic, I always try to load it up and see how much it can carry. It doesn’t always work. But I do try.

The Problem with that Crappy Armor Table I Made

So, what’s the problem with that crappy armor table I made? Well, frankly, the problem isn’t really with MY table, it’s with WotC’s. When they created their armor table, they decided that there were four basic properties that every suit of armor had. First, armor could be Light, Medium, or Heavy. And that means two things. But only one of those things actually matters. The thing that matters is how it interacts with proficiencies. That is, if armor is Heavy armor, you have to be proficient with Heavy Armors to wear it without penalty. Now, the weight class of the armor also determines whether you add your full Dexterity modifier to your Armor Class, whether you add your Dexterity modifier to your Armor Class up to a maximum of +2, or whether you don’t add your Dexterity modifier at all. But that is also part of the second basic property, the armor’s Armor Class. Simply put, they didn’t want to make you remember general rules for how your Dexterity modifier adds to your Armor Class based on the weight class of your armor and instead just listed it right in the table. That’s nice of them. But it also means that, in theory, I could design a suit of heavy armor that allows a character to add their full Dexterity modifier if I (a) didn’t notice the pattern or (b) didn’t care. And that’s fine. But it means that weight class doesn’t mean anything except what proficiency you need to wear the armor.

Third, some armors require the wearer to have a minimum Strength score to wear that armor without penalty. Which, honestly, seems like a waste. But what do I know? I’m just a blogger. Not a genius game designer like the folks at WotC.

Fourth, some armors impose a penalty on attempts to move around sneakily.

Now, the design is elegant enough. It’s not particularly complicated to understand that, to wear heavy armor, you need proficiency with Heavy Armors, and it’s not complicated to compare your Strength score to the minimum Strength score listed on the table. And to make note that you have Disadvantage on Dexterity (Stealth) checks when wearing certain suits of armor. It would be nice if the character sheet had some specific places to record this s$&%, but you can’t have everything can you. You wouldn’t want to add a couple of extra blanks to the character sheet. That would be so f$&%ing complex. It’s easier just to remember this s$&%. Or, more likely, to forget about it. As many players likely do.

But, where this design really fails is in extensibility. It’s easy enough to create a new suit of armor. I could create a suit of lightweight Heavy Armor, for example, that has no minimum Strength and imposes no penalty on Stealth just by adding a line to the table. But what if I want to add different game effects to armor. I’d have to add a bunch of extra columns to the table! And that’s precisely what I did. Hell, that’s all I did. Apart from coming up with a progression system for armor, that is.

Consider, alternatively, if I wanted to add a new mundane weapon. Say, a mancatcher. That’s a polearm that’s designed to ensnare or restrain someone. I’d just have to invent a keyword like Ensnaring and then write up the specific rule chunk for it to go alongside the rules for Finesse and Versatile and Reach. And then, if I ever wanted to add another weapon that could do the same thing, I could just add it to the table with the Ensnaring keyword.

By the way, I also did exactly THAT for my campaign. It allowed me to take that stupid “Special” keyword off the net. For whatever reason, there are exactly TWO weapons in the PHB that have the “Special” keyword instead of just having keywords that describe their traits. Why? Who the f$&% knows?

The weapon table is much more extensible than the armor table because the properties for the weapons are self-contained rules chunks contained in keywords.

Armor Keywords

And the solution, after that, is simple. Most of the columns on my table are about imposing Disadvantage on particular skills. I can get rid of all of those columns – INCLUDING STEALTH – by inventing a single trait. Say, “Impeding.” And then, just like the “Versatile” weapon trait, added a parenthetical note to define the effect. And that would look like this:

Impeding (Skill). While wearing this armor, you have disadvantage on ability checks related to the listed skill.

And now the armor table looks a lot cleaner. And all you have to record on the character sheet is the trait. Or you can just star the skill in question. Or whatever. I don’t know. It’s not like the designers figured out how to record Stealth disadvantage anyway. So why should I do any better?

And frankly, the Cuttable and Layered traits can go the same way.

Cuttable. The armor is held together with cords or straps that are easy to cut. As an action, you can use a knife or light slashing weapon to cut the armor off. Once cut, the armor cannot be worn until it is repaired at nominal expense or with smith’s tools or leatherworker’s tools.

Layer (Under/Over). You can simultaneously wear a suit of armor with the Layer (Under) trait and the Layer (Over) trait at the same time. You only benefit from the Armor Class of one of the suits of armor, but you benefit from and suffer from the traits of both types of armor.

And now we’re down to just one column. The swimming thing. See, swimming doesn’t just roll into the Impeding trait. Because swimming is a specific application of the Athletics skill. So it would need its own mechanics. And technically, it would need two traits: one to impose disadvantage on Strength (Athletics) checks related to swimming and one to make swimming completely impossible. Is that really worth it? Do I need that amount of nuance? Frankly, I don’t. It’s enough to have armor that drags you down to the bottom of the briny deep and to allow the Impeding (Athletics) mechanic to cover the rest. After much struggling, I invented the keyword “Leaden” for armor that drags you down to the depths.

Leaden. You cannot swim while wearing this armor and sink in the water. If you have a swimming speed, it is reduced to 0.

Admittedly, by economizing like that, some of the armor becomes a bit undifferentiated. Two of the Rank 0 light armor entries are identical. Either, I can delete one or I can differentiate them some other way. Maybe one is a quilted gambeson that will get waterlogged quickly and drag someone into the depths as surely as a waterlogged blanket wrapped around them might. That might make the armor itself useless as a Layer (Under) option. But, as I mentioned last time, it’s okay to leave some holes and garbage on the table. You never know when it might be useful later. Especially because you can build things out further.

Extending the Extension

Realistically, I COULD stop with that table. Fill in the names, fill in the weights, figure out some f$&%ing wealth and cost progression because WotC’s designers couldn’t be bothered. But the thing about a loaded system – and this trait system IS a loaded system – is that you quickly start to see other possibilities.

First, my final table doesn’t matter much. I mean, it matters for MY campaign. But my campaign is about seafaring and swashbuckling, and swimming and mobility issues are big. But your campaign might not be about seafaring and swashbuckling. Imagine a game that combines D&D action and courtly intrigue. You might have social penalties if you show up to court wearing peasant armor. Or if you’re in a highly lawful setting, wearing heavy armor might draw attention from the law. You could invent traits to describe those things and build your own armor table just the way I’ve built mine. Don’t worry, I will show you my final armor system for my game. You can take it if you want. But, by all means, use your own.

Second, though, my final table is just the tip of the iceberg even in my own campaign. Because I realized something else: the ranking system combined with the Armor Class increases and the various negative traits creates a progression that isn’t much different than a magic item progression. After all, what’s the difference between trading up from Bronze Plate (AC 16) to Steel Plate (AC 17) to Adamantine Plate (AC 18) and trading from Bronze Plate to Bronze Plate +1 to Bronze Plate +2? Mechanically, it’s all the same.

Consider too that, once you have a trait like Impeding (Skill), you could also have a trait like Enhancing (Skill). A suit of blackened leather armor with padding in all of the joints might have a trait like Enhancing (Stealth). And that would be worth bumping up the armor a rank as surely as a +1 to AC is worth bumping up the rank. You could have armor that resists certain types of damage, like red dragon hide that resists fire. Or you could have armor that is vulnerable to certain types of damage. Like bronze armor being particularly vulnerable to lightning damage. And those properties could be mundane, or with the addition of a Magic trait, they could be due to enchantments. And with the addition of an Attunement trait, you can have magic armor that requires attunement to work.

In short, you could roll mundane and magic armor into one system and have an easy way to compare normal armor and magic armor, allow players to buy and sell and craft magic armor, and so on. And if you want to build a crafting system, you also now have a space to stick modifiers for the quality of the work. You could have a Masterwork trait, for example.

And that’s precisely what I did. I created my armor table, but I also created a few extra traits that I could use to layer on magical effects. That way, I could easily create something like a +1 Elven Gambeson that grants advantage on Dexterity (Stealth) checks with the Magic, Exceptional (+1), and Enhances (Stealth) traits. And I would know that armor was roughly equivalent in terms of power to a mundane jerkin made of perfectly normal manta skin.

In the end, this is what my table of commonly available armors looked like:

And if you want to see the list of keywords and the descriptions of the armors, here’s an excerpt from my campaign guide describing armor in detail.

Picture something equally awesome for weapons and for spellcasting focusses.

Cost and Wealth Progression

As for pricing this s$&%? F$&% if I know. I’m still working it out. And you can pretty much just make up whatever the hell you want because D&D has no good, consistent standard or pricing model. I’ll come back to the question when I’ve figured out what the hell to do about it. In the meanwhile, as near as I can tell, Rank 0 equipment should be under 50 gp and should be available as starting equipment. Rank 1 equipment should be available at 5th level or higher. Rank 2 equipment should be available at 11th level or higher. And Rank 3 equipment should be available at 17th level or higher. But, personally, I feel those cutoffs are too high.

I’ll let you know what I figure out.

38 thoughts on “Drowning in Armor Systems (Part 2)

  1. Nice work with the armor table. I was thinking about tweaking the system to have mundane armor that is resistant/vulnerable to some kinds of damage, and your “keywords” method seems great!

    As for pricing, I’m ditching the DMG guidelines for a system of my on.

    Basically, I was trying to make Gold relevant again by having treasure grant XP. I figured that the treasure should be 1/3 of the total XP of an adventure. So I calculated that, at the start of the 2nd level, the players should have 100gp each. So I’m redoing the price tables for mundane and magical​ items with those parameters.

    As aways, thanks for the inspiration!

    • I am doing the same thing. As it stands right now, I’m just planning a treasure progression where PCs should have 100 gp per level of “equipment.” The problem is, I also need to plan for my players to buy a ship and upgrade it.

      • the most elegant way to do something like that would be to have two currency types. It might require some player buy in but even just something like player gold vs “crew” gold is separate and they use crew gold to pay sailors and build the ship

  2. *faint applause*

    Not using keywords for the armour table was a bad decision on WotC’s part. My only issue with your table is that is a ton of keywords to remember. Looking at the weapons table in the PHB (though I can’t say it’s a stellar example of game design), there’s exactly one weapon with more than three keywords (heavy crossbow), and half the keywords on that are intuitive or unnecessary.

    I will definitely be stealing this for future campaigns. I’ve always hated the armour system in 5e. It’s so useless.

    • Agreed… and if I weren’t doing swashbuckling and seafaring, I could get by with a smaller number of keywords. Hell, you could probably wrap Athletics, Acrobatics, and Stealth into one keyword: Clumsy which gives disadvantage on Strength and Dexterity based ability checks. That would cover everything without even having to refer to skills.

    • It is a lot, but at least it’s available and defined. I never even thought of the fact that there isn’t a clear spot to mark out that kind of thing near the armor. Even the damage calculator box doesn’t give room for you to write “finesse” or “special” as a reminder. When I’m a player, I go crazy with index cards for spells and notes and things. But that’s also because I’ve been a GM so long; I keep track of my own stuff so the GM doesn’t have to. And I know my character. Everyone should. BUT for WotC to not leave space for stuff like that just seems really off.

      • It IS kind of funny when you look at it. How much the character sheets were created as an afterthought. I think that’s backwards. Personally, I think mechanics should be designed with the fact that some will have to be recorded and tracked on sheets in mind.

  3. This is definitely a concept that I can make good use with. Bouncing off agentcarr16’s idea that the number of keywords on any one piece of armor is high compared to the standard weapons list of keywords, what about making “cuttable” and “layer (over) synonymous? It could be inferred that any armor that can quickly be cut off would also be loose enough to wear a less-bulky light armor under it. The Layer (under) could still apply, so that not every light armor could be worn under heavy armor.

    Also, the “Leaden” property may be replaced with something as simple as a maximum armor weight that allows swimming vs sinking. Then in designing a new armor type you could vary the rank of the armor just by adjusting the weight slightly.

    Or to make it even more interesting (this may add more complexity than it’s worth, I don’t know). Make the characters strength (or constitution?) dictate swimming vs sinking. Strength modifier * 10 equals the maximum armor weight that the character can swim in. That would allow character level to come into play in regards to wearing armor and swimming. A higher level character with a higher strength score could swim in more armor than a low level character.

  4. One of the things that I really dislike in the magical armor table is the +1, 2, and 3 armors. Seems like such a… mundane thing to have in a magical armor table. So I came up with a “Quality” system, which could easily just be used as keywords with your table or whatever, and you even touched a little on it by suggesting the Masterwork keyword. My quality modifiers went: Poor (-1 AC), Decent (– AC), Good (+1 AC), Excellent (+2 AC), and Masterwork (+3). It just seemed unnecessary to me to have those modifiers be on the magical items list when, in my mind, a skilled smith should be able to craft better quality armor for the players.

    Anyways, this is good stuff. I’ll definitely be using the foundations you’ve laid out to develop a table for my own campaign.

  5. When I first started playing 5E I used the DMG’s XP system for building encounters but it really bugged me that I applied multipliers to the XP for groups to determine difficulty but didn’t use the multiplier when it came time to hand out XP. It felt like I was dramatically slowing down progression any time I had the players face off against a group of monsters rather than just 1-2. So, I changed the way I handed out XP and just gave XP equal to the difficulty. The DMG suggests that players can handle a certain amount of XP of difficulty per encounter, and a certain amount of XP of difficulty per day, based on their level (the “Adventuring Day”). What’s interesting is that if you round up the number of Adventuring Days it takes to level to a whole number, it takes exactly 45 Adventuring Days to reach level 20…which just happens to be the exact amount of Treasure Hoards the DMG recommends you hand out. I don’t usually hand out Treasure Hoards in one lump sum, but I do use them to figure out how much to give over the course of a level.

    So, I created a spreadsheet that calculates average Treasure Horde monetary value (ignoring magic items) and shows how much the group/individual acquires per level and how much they have accumulated in total. Here is how much equipment should cost if you want it to only be available at certain levels.

    2nd: <100gp
    5th: 500-2,000gp
    11th: 10,000-20,000gp
    17th: 100,000+gp

    Players will be able to acquire items a little earlier than the indicated level if they save all of their money up to purchase that specific item, but most players will find stuff to spend their money on in intervening levels, and I don't think it hurts things too much for a character to save all of their money to purchase something at level 9 that they normally wouldn't afford until 11.

    • Oh, if anyone wants to know how much money a group acquires on average per level, here it is. Personally, I enjoy rolling the dice which can be dramatically different from these numbers, but it tends to average out over time. These numbers are for an entire group, so divide by 4 or 5 for individuals (you might want to hand out a little bit more/less treasure for groups of other sizes).

      1st-2nd: 375gp/level
      3rd: 750gp/level
      4th: 1,100gp/level
      5th-10th: 13,700gp/level
      11th-16th: 73,000gp/level
      17th+: 675,000gp/level

    • “it takes exactly 45 Adventuring Days to reach level 20…”

      Guard: Sire, remember those vagabonds that `agreed’ to retrieve That Item for you in exchange for us dropping the charges for what happened at the Inn?
      King: Yes.
      Guard: They have returned with That Item.
      King: Excellent, let them in.
      Guard: But sire, it took them almost 2 months to return.
      King: Well, in that case… abandon kingdom!

  6. Firstly, thanks for the article, I actually gasped at the magic/mundane item thing, because I’ve been trying to fix/ignore magic items for so long in my games.

    Secondly, the only place I remember seeing the special keyword other than in the equipment list was somewhere in the monk weapons (possibly Kensai), I think it was to prevent them from using lances or something as monk weapons for some reason. Not a good reason to have it, but might explain its existence.

  7. I’m having trouble getting the gist of layered armor. If you can only take advantage of the best AC and suffer all disadvantages (and advantages), does the main benefit lie in having the under-armor as back-up if the over-armor is cut/removed?

    • You can cut off your outer layer if you suddenly find yourself desperately needing to swim, like if you fell off a boat. Angry prepared this for a nautical themed campaign.

    • I believe the intention is you can also stack special properties

      So wearing a bronze cuirass normally gives vulnerability to lightning, but wearing a gambeson underneath acts as an insulating layer to remove that bonus damage (because it doesn’t have vulnerability)

  8. I feel like your tiering thing is just remaking 3.5e’s magic item system but in 5e

    for those that don’t recall or haven’t used it, an item had 0-10 enhancement, giving it +1 gave it 1 enhancement, +2 gave it +2, adding a d6 of fire gave it +2, etc.

  9. “Two of the Rank 0 light armor entries are identical.”

    Actually, It looks like you forgot to mark one as Leaden, but had it fixed by the next table, so you’re all good there.

    I had poked at something like this for my own ocean setting, but never got this far. I might have to get the gang together and give it another go now…

  10. So I don’t mean to be a smart ass here but what happens if some opponent cuts a cuttable armor? It could be interesting.

    • Yes, it could. Granted, given how difficult it would be to do that, the opponent would be infinitely better off just stabbing the person. I mean, realistically, you’d have to cut a minimum of two straps over the shoulders of someone who is trying to kill you with a weapon. And you have to get a blade INSIDE and UNDER the straps to cut them. Imagine trying to cut a backpack off someone, except the backpack included armored plates that covered most of the straps themselves, while the person was trying to kill you.

  11. The impeding Athletics/acrobatics effect discourages grappling, shoving and the like, while also making it more likely to be successful against the character wearing the armor. Is this a bug, or a feature?

  12. thanks angry, this armour table has inspired my entire campaign, it starts in two week and it will be a seafaring campaign, the comments section will probably be closed by then but if there’s anything glaringly wrong with the system I’ll let you know

    P.S. any tips for pricing? you only have the prices for the first few items listed.

  13. Another awesome post Angry, as always. I have been lacking excitement about the weapon and armor tables in 5E for a while and started thinking about tinkering with it after looking at other systems and how they handle these. The additional properties that you added for the armor, as well as getting rid of the “magic” bonus and working that into the normal item properties got me inspired for creating a sensible weapons table. The system I created would work the properties of the item into the cost and allow the GM to basically engineer any weapon they wanted by adding or removing properties like you did with the armor. Below is a list of the properties, my cost/property estimate and some example weapons. Compared to the DMG the cost is off a little but generally close. The biggest thing it removes is any random differences in price (shortsword being 10 gp and scimitar being 25 gp but having no difference in functionality in game). Sorry if this post gets to be too long. This is still a work in progress and has not been tested by any means. I haven’t added magic item properties but that would be a simple addition and cost multiplier.

    Ammunition: Requires ammunition to use.
    Concealed: The weapon is designed to be easily hidden on the body, for example as a piece of normal jewelry or in a boot strap. A successful active perception check will be needed to find it.
    Finesse: Can use strength OR Dexterity modifier for the attack AND damage rolls.
    Fragile: On a critical fumble the weapon has a 50% chance to break.
    Heavy: Small creatures have disadvantage on attack rolls with heavy weapons. Requires a minimum strength value of 15 to use. Damage tier increase by 1
    Inferior: The weapon is made of inferior materials, the workmanship is shoddy, or the weapon is simply worn with use and age. This grants a penalty of -1 to hit and damage up to a -3.
    Improvised: A mundane object used as a makeshift weapon. Damage tier is reduced by 1.
    Light: May be used in the offhand in order to dual wield without penalty. The weapon damage is one tier lower.
    Loading: May only fire one piece of ammunition from the weapon when using an action, bonus action, or reaction to attack regardless of the number of attacks you can have in a round.
    Martial: Requires specialized training to gain proficiency in order to use this weapon.
    Masterwork: The weapon has been crafted with the highest quality of materials, honed to perfection, and is very well balanced and easy to wield. This grants a bonus to hit and damage of +1 to +3.
    Range: The weapon has a maximum range at which it can be used. The weapon has disadvantage on attack rolls beyond the normal range. Unable to attack beyond the long range.
    Reach: The weapon adds 5 feet to its reach when attacking.
    Short: The weapon is short and may be drawn or stowed turn as a free action.
    Simple: The weapon is not difficult to utilize and does not require special training in order to wield. The weapon damage is reduced one tier.
    Thrown: The balance of the weapon is designed so it can be thrown in order to attack enemies at range. The ranged attack uses the same attribute as the melee attack would with the same weapon.
    Two-Handed: The weapon requires two hands to wield. The weapon’s damage is one tier higher.
    Versatile: The weapon can be used with one or two hands. The damage die increases by one when used with two hands.
    Weapon Cost
    Weapon Base Price: 10 GP
    Additional property = base price x2
    Masterwork property = base price x 100 – 500?
    Negative property (simple/light/inferior/improvised/fragile/Heavy) = base price / 5

    Sample Weapons cost and damage
    Dagger = 10/5 (simple) /5 (light) = 4 sp 1d4
    Long Dagger = 10 /5 (simple) /5 (light) x 2(finesse) = 8 sp 1d4
    Throwing dagger = 10 / 5 (simple) /5 (light) x 2(finesse) x2 (thrown) = 16 sp 1d4
    Wood Axe = 10/5 (improvised) /5 (simple) x2 (two handed) = 16sp 1d6
    Hand axe = 10 /5 (light) x2 (finesse) = 4 gp 1d6
    Throwing axe = 10/5 (light) x 2 (finesse) x2 thrown = 8 gp 1d6
    Battle axe = 10 x2(versatile) = 20 gp 1d8/1d10
    Club = 10/5(simple) / 5 (light) = 4 sp 1d4
    Quarterstaff = 10 /5 (simple) x2 (versatile) = 4 gp 1d6/1d8
    Walking staff = 10/5 (simple) /5 (improvised) /5 (fragile) x2 (2 handed) = 16cp 1d6
    Throwing hammer = 10/5 (simple /5 light x2 thrown = 8 sp 1d4
    Glaive = 10 x2 (reach), x 2 (two handed) = 40 gp 1d10
    Great sword = 10 x2 (heavy) x2 (two handed) = 40 gp (1d12)
    Halberd = 10×2 (reach) x2 (two handed) x2 (heavy) = 80 gp (1d12)
    Bastard sword = 10 x2 (versatile) = 20 gp 1d8(10)
    Long sword = 10 gp 1d8
    Short sword = 10 / 5 (light) x2 (finesse) = 4 gp 1d6

  14. Thanks for this, your first comment on my site. Feel free to make it your last. This site has room for exactly one asshole. And since I pay the bills, I get to be that asshole. If you can’t express your opinion without insulting, ranting screed, you will be banned. You dick.

  15. Hey Angry, any chance you give us a breakdown of the math you used to determine the costs of weapon and armor properties? I mean, how much are “finesse”, “resistance to fire”, “increased weapon die” and other such things worth in terms of enhancement ranks? I’m trying to do my own table based on yours, and even though I can probably figure something out on my own, it would be way easier if I had any guidelines to begin with.

  16. Hey Angry

    This is awesome and gives me some great ideas for my current campaign and possibilities for all my future campaigns.

    Did you mean for clothing to not have the Layer (Under) trait?

Comments are closed.