Go to Part 1

This is an equipment sheet designed to be used with the Encumbrance by Stone rules I posted yesterday.

(click for PDF)

USING THE SHEET

Using the sheet is really where this system comes alive, because it basically makes tracking encumbrance as easy as listing what you’re carrying.

Armor/Shield/Weapons: The assumption is that your currently equipped armor, shield, and weapons will be listed for reference on the front of your character sheet. You can jot down the current encumbrance values for these items in the spaces provided in the lower right hand corner of the sheet.

Coins/Gems: These are listed in the upper right and their encumbrance calculated as shown. (To quench the “I have one coin and it apparently weighs a ton” complaints, you can allow players who carrying 20 coins or less to list them as “loose change” in the miscellaneous equipment section.)

Heavy Items: This section is for listing anything that qualifies as a heavy item (i.e., weighs 1 or more stones all by itself).

Miscellaneous Items: The heart of the sheet. Simply list everything you’re carrying in bundles of 20 or less. When you’re done, you can immediately see how many stones of miscellaneous equipment you’re carrying. Bam.

Add Misc. Equipment + Heavy Items + Coins/Gems + Armor + Shield + Weapons = Total Encumbrance. In practice this is all single digit arithmetic and adjusting your encumbrance on-the-fly during an adventure is practically automatic.

Moved equipment to your horse? Picked up a bunch of treasure? Throwing away your shield in order to run away from the goblin horde at your heels? It can all be done in seconds.

TIPS AND TRICKS

Stored Items: This section of the sheet is for anything you own that isn’t currently being carried by your character.

Inventory of Gems: These are tracked separately to make calculating coin/gem encumbrance easier.

Containers: This area is used for listing containers in use (which don’t count against encumbrance). Empty containers should be listed as miscellaneous equipment. There are two easy methods for tracking which items are in which container:

(1) List miscellaneous equipment slot numbers next to the container.

(2) Put a symbol (star, circle, square, etc.) next to the container, then mark items in the container with the same symbol.

Tracking Supplies: The intention is that you list your supplies in the miscellaneous equipment section, but you can quickly check off supplies used on the trackers. At some point of convenience, you can go through your equipment list, adjust the totals, and then erase the supply checklists to start anew.

The Blank Space: After making the sheet I kept expecting something to crop up that I’d forgotten. (At which point I’d have this convenient blank space to slot it into.) After a half dozen sessions, nobody has suggested anything. (Let me know if you think of something.)

Go to Design Notes

This is a simplified method for handling encumbrance in OD&D and is designed to completely replace the existing encumbrance system. It’s indebted to both Delta’s D&D Hotspot and Lamentations of the Flame Princess. I’ll be posting full design notes in a few days.

Encumbrance, measured in stones carried, determines how much a character’s equipment slows them down, as shown on the table below:

This can be conveniently thought of as the 5-10-20 rule (which corresponds to the maximum movement rates of 12”, 6”, and 3”).

Mounts and Mules: Can carry three times as much, following a 15-30-60 rule. (The base movement for mounts and mules are given in Volume 2: 24″ for a light horse; 18″ for a medium horse; 12″ for heavy horses, draft horses, and mules.)

WEIGHT BY STONE

To determine the number of stones carried by a character, simply consult the table below.

Miscellaneous Equipment: Up to twenty items of the same type (scrolls, arrows, potions, rope) can be bundled together for the purposes of encumbrance. Items of different types aren’t bundled when determining encumbrance.

Stowed Weapons: Stowed weapons have been compactly stored in a way which makes them more difficult to draw (but easier to carry). Stowed weapons must be retrieved before they can be used, but they only count as 1 stone per 5 weapons.

Heavy Items: Anything weighing more than roughly 10 pounds can’t be effectively bundled. Estimate a weight in stones (about 10-20 pounds to the stone). When in doubt, call it a stone.

Clothing / Worn Items: Worn items don’t count for encumbrance, unless the individual items would qualify as heavy items.

Weight of a Man: A human can generally be assumed to weigh about a dozen stones. Halflings weigh only 2 stones. (Your own weight does not count towards your encumbrance.)

CONTAINERS

Weapons are assumed to be in sheaths, armor is worn, and you might have a wineskin or two strapped to your belt. But since there’s a limit to how much you can hold in your hands, everything else you’re carrying needs a place to live. As a rule of thumb, containers can carry:

Empty containers count as miscellaneous equipment. Containers being used to carry items don’t count towards encumbrance.

Larger sacks (often referred to as “loot sacks”) are also possible, but these cannot generally be stored on the body. They must be carried in both hands.

Go to Part 2: Encumbrance Sheet

One of my long-standing concerns with the D20 system was the skewed probabilities of opposed group checks. For example, consider the example of a PC making a Move Silently check opposed by an NPC’s Listen check where both characters have the same skill modifier. In this scenario, a single PC attempting to sneak past a single NPC has a 50% chance of succeeding.

Compare this to a situation in which 5 PCs are attempting to sneak past 5 NPCs (with, again, all of the characters involved having the same skill modifiers). This effectively becomes a check in which the 5 PCs are rolling 5d20 and keeping the lowest result, while the NPCs trying to detect them are rolling 5d20 and keeping the highest result.

The average roll of 5d20-keep-lowest is 3. The average of 5d20-keep-highest is 17. That 14 point differential means that it’s virtually impossible for a party of characters to sneak past a group of evenly matched opponents. (And even sneaking past a single watchman is difficult as the average party roll of 3 is opposed by an average roll of 10.)

Of course, the odds are actually worse than this: A successful stealth attempt will also usually require a Hide vs. Spot check, so you need to succeed at not one but two checks at these outrageous odds. And this assumes that the PCs all keep their stealth skills maxed out (which in practice they won’t, particularly since it’s so pointless to do so).

The argument can certainly be made that this is realistic in some sense: A large group should have a tougher time sneaking past a sentry than one guy and more eyes means more people who can spot you. But I would argue that the probability skew is large enough that it creates results which are both unrealistic and undesirable.

In practice, the effects of the skew are obvious: Group stealth attempts quickly drop out of the game. When stealth is called for, it takes the form of a sole scout pushing out ahead of the rest of the group. And when the scout becomes too fragile to survive when the check finally fails, stealth stops being a part of the game altogether.

Since I’d prefer stealth to be a potentially viable tactic, a solution is called for.

QUICKIE SOLUTIONS

DISTANCE / DISTRACTION PENALTIES: A guideline that can really help the stealther is the -1 penalty per 10 feet that is supposed to be applied on Listen and Spot checks. Keep about a hundred feet away from the guy trying to spot you and you can quickly cancel out the probability skew of the dice.

Unfortunately, these modifiers become kind of wonky, particularly when it comes to Spot checks. On the open plains, for example, the “maximum distance at which a Spot check for detecting the nearby presence of others can succeed is 6d6 x 40 feet”. The minimum distance of 240 feet, therefore, is supposed to impose a -24 penalty and the maximum distance of 1,440 feet impose a -144 penalty.

I’ve tried a few different ways of fixing these modifiers, but am currently just using an ad hoc sense of what the range of the check is.

TARGET NUMBERS: Instead of making these opposed checks, set a target number for the PC’s skill check of 10 + the NPC’s skill modifier. (This essentially halves the probabilty skew.)

GROUP CHECKS: Make only one check for each group. But what skill modifier to use? Using the average value is cutesy, but impractical at the game table. Using the lowest value still effectively takes group stealth off the table. Using the highest modifier means that everyone except the rogue ignores the stealth skills entirely and also creates issues with determining surprise.

And how big can a group be? One guy with a decent Hide check shouldn’t be able to sneak an army of ten thousand soldiers under the nose of a watchtower, but where do you draw the line?

Maybe you could limit the number of people covered by a check to equal the skill leader’s skill ranks? Or impose a -2 penalty per person in the group?

COMBINE STEALTH / PERCEPTION SKILLS: I’ve been folding Hide/Move Silently into a Stealth skill and Listen/Spot into a single Perception skill intermittently since 2002, so I wasn’t particularly surprised when both Pathfinder and 4th Edition went in the same direction. It cuts down on dice rolls and eliminates the undesireable “need to succeed twice” feature of stealth checks.

This does create some interesting oddities around trying to resolve invisibility, and while I haven’t found the perfectly elegant solution yet, this slight corner case is (in my experience) preferable to the constantly degrading effects of splitting the skills.

Using some combination of these solutions tends to mitigate the problem, but I’ve generally been unsatisfied with the hodgepodge fashion of it all. So taking my unified Stealth and Perception skills in hand, I’ve been looking for a more elegant solution.

GUMSHOE’S PIGGYBACKING

I found the roots of what I think may prove a usable mechanic in the GUMSHOE system:

When a group of characters act in concert to perform a task together, they designate one to take the lead. That character makes a simple test, spending any number of his own pool points toward the task, as usual. All other characters pay 1 point from their relevant pools in order to gain the benefits of the leader’s action. These points are not added to the leader’s die result. For every character who is unable to pay this piggybacking cost, either because he lacks pool points or does not have the ability at all, the Difficulty Number of the attempt increases by 2.

Obviously the point-spending mechanics which underlie the GUMSHOE system can’t be translated directly into the D20 system, but the basic structure of a lead character making a check onto which others could “piggyback” was inspiring.

D20 PIGGYBACKING

When the whole group needs to perform a single task collectively (like sneaking past a guard or using group-climbing techniques to scale a cliff) they can make a piggybacking skill check.

(1) One character takes the lead on the check. This character makes the skill check using their normal skill modifier, just like any other skill check.

(2) Other characters can “piggyback” on the lead character’s check by succeeding on a skill check. The Piggyback DC of the check is equal to half its normal DC. (So if the leader is making a DC 30 check, the other characters must make a DC 15 check to piggyback on the check result.)

(3) The lead character can reduce the Piggyback DC by 1 for every -2 penalty they accept on their check. (They must make this decision before making the check.)

(4) The decision to piggyback on the check must be made before the leader’s check is made.

OPPOSED PIGGYBACKING CHECKS: The DC of the check is set by the lead character’s check. Just like any other piggybacking check, only characters who succeed on the piggybacking check benefit.

(To simplify the resolution, you can start by rolling only the lead characters’ checks. After you’ve determined which lead character succeeded, you can call for the necessary piggybacking checks. Anyone piggybacking on the failed check, of course, will fail no matter what their piggybacking check would have been.)

A couple months ago I mentioned that I had created counter-intelligence guidelines for the Gather Information skill. Confanity had mentioned that he was intrigued by them, and I promised to get them posted sooner rather than later. For certain definitions of “sooner” and “later”, I suppose that this has now been accomplished.

Counter-Intelligence: A character can attempt to detect other characters gathering information about a particular subject in the area by making a Gather Information check. The DC of the counter-intelligence check is opposed by the original Gather Information check made in the attempt to gather the information.

Avoiding Suspicion: If a character is attempting to avoid suspicion, it becomes more difficult to detect them. Although the character suffers a -10 penalty on their Gather Information check for the purposes of collecting the information they seek, they gain a +10 bonus to their Gather Information check for the purposes of opposing the counter-intelligence check.

In addition, cautious characters can voluntarily increase the penalty on their original Gather Information check, granting an equal bonus for the purposes of opposing the counter-intelligence check. (For example a character could decide to be extra cautious and apply a -15 penalty to their Gather Information check. Their unmodified check result is 30, which is modified to 15 (30 – 15) for the purposes of determining what information they actually glean. But if another character attempts to detect their presence, they would have to make a DC 45 (30 + 15) counter-intelligence check to do so.)

Modifiers: Apply a -2 penalty to counter-intelligence checks for every week that has passed since the original Gather Information check.

USING THE GUIDELINES

For PCs, these guidelines aren’t only useful to find out if someone is asking questions about them. In fact, they’re generally more useful for identifying competing interests. Who else in town is trying to find out information about the Vault of the Dwarven Kings? Or investigating the Baker’s Street Gang?

Resolving these types of checks requires the GM to know two things:

(1) Who else is looking for that information?

(2) What should the DC of the check be?

The answer to the former question, of course, is situational. For the latter you could either set simple, static DCs as you would for any other Gather Information check, or you could actually resolve the opposed check.

FACTION

I generally find it useful to know what kind of information-gathering capacity factions have in my campaigns. For smaller factions (like an opposing group of adventurers or a small gang of bad guys), this is as simple as looking at the highest (or most appropriate) Gather Information skill modifier in the group.

For larger factions, I simply assign a Gather Information modifier to the group. (This number is essentially arbitrary, although I base it on the size, nature, and resources of the group in question.)

When trying to figure out how suspicious a particular group is (i.e., whether they’re performing counter-intelligence to make sure anyone is asking questions about them) or how pervasive their surveillance is (i.e., how often they’re making counter-intelligence checks), I’ve generally just relied on common sense to make a ruling whenever the question needs to be answered. But if you’re running a campaign where intelligence and counter-intelligence is likely to be fairly common (for example, a modern espionage campaign), then codifying those factors might be useful.

(For example, a Paranoid group might check 1/day; a Suspicious group every 1d6 days; a Cautious group once every 3d10 days; a Naive group might never check. In other words, if the PCs investigate a Suspicious group then there would be a counter-intelligence check made 1d6 days later.)

Faceless rage is a magical disease of evil and chaos that affects only humanoids. It transforms its victims by erasing their face and turning them into murderous savages.

TRANSFORMATION: Whenever a victim of the faceless rage suffers ability score damage from the disease, they must succeed at an additional Fortitude save (DC 18) or be transformed according to the faceless rager template.

Fortitude save (DC18); Infection contact/injury; Incubation 1 day; 1d6 Int/1d6 Wis, plus transformation (see above).

TEMPLATE: FACELESS RAGE

Noppera-b? (??????, faceless ghost) from the Buson Youkai Emaki (??????)

“Faceless rager” is a template that can be added to any humanoid or giant (referred hereafter as the base creature).

Size and Type: The base creature’s type does not change, but the creature gains the shapechanger subtype.

Hit Points and Hit Dice: Same as the base creature. To calculate total hit points, apply the faceless rager’s bonus to Constitution.

Attacks: A faceless rager loses the bite attack of the base creature (if any), but retains all other attacks of the base creature and and gains a slam attack (1d6 damage for Medium-size faceless ragers).

Special Attacks: A faceless rager loses the gaze attack of the base creature (if any), but retains all other special attacks of the base creature and also gains the special attacks described below.

Disease (Ex): Any creature struck by the natural attack of a faceless rager (including its slam attack and steal visage abilities) is exposed to faceless rage. The save DC is Constitution-based.

Improved Grab (Ex): To use this ability, the faceless rager must hit a natural attack (including its slam attack).

Steal Visage (Su): If a faceless rager succeeds at a grapple check against any humanoid, its victim must make a Fortitude save or have its face removed. The victim is left blinded, deafened, and mute. As the victim has no mouth, it will risk starvation if its face is not restored. Restoring a victim’s face requires a regeneration spell, just as if it were a severed limb. The save DC is Constitution-based.

Special Qualities: A faceless rager retains all special qualities of the base creature, and also gains those described below.

Blindsight (Ex): A faceless rager has blindsight 60 feet.

Incurable Disease (Ex): A faceless rager can no longer recover naturally from the faceless rage disease that afflicts them. Only magical treatment can restore the victim, specifically a remove disease spell followed by a greater restoration. Once cured, the faceless rager loses this template. A faceless rager’s face can only be restored after the disease has been magically cured, and requires a regeneration spell, just as if it were a severed limb.

Mindless Rage (Ex): A faceless rager must seek out and attack the nearest humanoid. If no humanoids are present, it will attack the nearest creature. If no creatures are present, it will wander randomly until it finds one. In this mindless rage, a faceless rager gains a +2 morale bonus on Will saves, but suffers a -2 penalty to Armor Class. They cannot use any Charisma-, Dexterity-, or Intelligence-based skills (except for Balance, Escape Artist, Intimidate, and Ride), the Concentration skill, or any abilities that require patience or concentration, nor can they cast spells or activate magic items that require a command word, a spell trigger (such as a wand), or spell completion (such as a scroll) to function. They can use any feat they have except Combat Expertise, item creation feats, and metamagic feats.

Abilities: Faceless ragers gain +4 to Strength and +4 to Constitution.

Challenge Rating: Same as base creature + 1. However, levels in a spellcasting class count only one-quarter towards their challenge rating (since the faceless rager cannot use spells). (For example, a faceless rager based on a 4^th-level wizard would be a CR 2 challenge.)

Alignment: Always chaotic evil.

SAMPLE FACELESS RAGERS

DISEASED CARPENTER (CR 3) – Expert 3 – CE Humanoid (human shapechanger)
DETECTION – blindsight 60 ft., Listen +3, Spot +3; Init +1
DEFENSES – AC 9 (+1 Dex, -2 mindless rage), touch 9, flat-footed 8; hp 23 (3d6+12)
ACTIONS – Spd 30 ft.; Melee slam +4 (1d6+2 and disease); Ranged +3; Space 5 ft.; Reach 5 ft.; Base Atk +2; Grapple +2; SA improved grab, steal visage (DC 13)
SQ blindsight 60 ft., incurable disease, mindless rage
STR 14, DEX 12, CON 14, INT 12, WIS 10, CHA 10
FORT +3, REF +2, WILL +5
FEATS: Skill Focus (Craft (carpentry)), Skill Focus (Craft (carving)), Skill Focus (Knowledge (wood))
SKILLS: Balance +1, Craft (carpentry) +8, Craft (carving) +8, Diplomacy +8, Escape Artist +1, Hide +1, Knowledge (architecture/engineering) +6, Knowledge (wood) +8, Move Silently +1, Ride +1, Search +6, Sense Motive +6, Use Rope +1

DISEASED SOLDIER (CR 5) – Warrior 5 – CE Humanoid (human shapechanger)
DETECTION – blindsight 60 ft., Listen +3, Spot +3; Init +0
DEFENSES – AC 8 (-2 mindless rage), touch 8, flat-footed 8; hp 33 (5d8+10)
ACTIONS – Spd 30 ft.; Melee slam +8 (1d6+3 and disease); Ranged +5; Base Atk +5; Grapple +5; SA improved grab, steal visage (DC 14)
SQ blindsight 60 ft., incurable disease, mindless rage
STR 16, DEX 10, CON 14, INT 12, WIS 10, CHA 10
FORT +6, REF +1, WILL +3
FEATS: Alertness, Improved Unarmed Strike, Run
SKILLS: Appraise +1, Bluff +1, Climb +3, Craft (wittling) +1, Forgery +1, Gather Information +3, Innuendo +1, Intimidate +8, Jump +3, Listen +3, Search +1, Sense Motive +2, Spot +3, Swim +1

D20 Rules by Justin Alexander
This material is covered by the Open Gaming License.