On long journeys we always forget to track supplies so I am looking for a way to make supplies actually matter in D&D 3.5.
The starting point should probably be to take efforts to not forget to track supplies. To help with that, you could, say, print out/write down the Starvation and Thirst rules on a note and stick it to your DM screen.
That being said, supplies generally don't matter in 3.5. There are just too many ways to trivialize it, even if rigorously tracked. Here are some reasons:
If you wanted to make rations matter, you'd have to start cutting these down, one by one. And I wouldn't recommend it for most games - it's all too likely to end closer to "ration accounting 101" than the "gritty survival horror" houserules like this tend to be aiming for. You may want to check out a different system if that's what you're after.
|show 1 more comment|
I like the other answers, but an alternative approach is to focus on logistics and role playing.
The bottom line, as others have pointed out, is that minute bookkeeping is very rarely fun. A logistical challenge can be interesting though.
I should say, I have never made food a major mechanical issue in any game. But it can be a good flavor issue and a major logistical challenge can be interesting (I haven't done this in 3.5, so it might just be too trivial there).
In a game where supplies are meant to be an issue, make sure the party has a supply plan in place. I don't track every bit of food and I rarely make it a mechanical thing at all, but it makes them think a bit about the combination of magic, foraging, and carried supplies they will use. I then mention (but don't keep track of) of what they found, their use of magic. When things are lean, I mention the hunger pains, the way lack of supplies gets on nerves (especially if there are NPCs with them). A successful hunter or forager could easily be the hero of the day. A significant source of rations might be a major plot point, even if it isn't tracked mechanically.
But of course, all of that is only interesting if there is something making it challenging. In a post-apocalyptic world where food is scarce and something another group will fight you for, then its interesting. If they have magics that let them generate food or sustenance they might easily get attacked for that. If they managed to get a rare large animal, they might have to fight with other two legged scavengers to be able to keep it. Even in a campaign that isn't survival driven, it can be interesting for them to need to carefully defend that donkey that is carrying their provisions when they get ttacked. But its interesting as plot points, background, and a conflict driver, not in fine bookkeeping with mechanical effects.
The other way its interesting is if you have a truly large group, like say a large army unit, or your enemy does. Many wars in the real world have been won or lost based on logistics. Sure scavenging for a small group is easy in many environments, and a few magical items or spells to sustain a small group might be trivial. But if you have an army you need to worry about keeping and maintaining your logistical line. Scavenging for such a group is on the lines of seizing a hostile grain store, not hunting a brace of rabbits. That again can drive plots if you have to make tactical decisions to protect a long supply line or moral decisions about letting the local civilians starve so you can feed your troops. A potent magical cauldron capable of feeding a platoon might just be a macguffin to get your players to try for a stealth mission to try to seize it to help with the supply situation.
Edited to fix grammar.
I think the easiest thing to do to reduce bookkeeping and make it simpler is to (instead of treating each piece of food as something else to keep track of) group rations together. Figure out how much your group needs to eat each day (per person) and how much they need together. Then figure out how much enough food for one day for everyone should cost and how much it weighs.
Example: Let's say each human or human-like creature needs ~2500-3500 calories (They are walking/fighting all day, which tends to make one hungry). That's several loaves of bread, or maybe one loaf, a half-pound of red meat (dried/smoked), some vegetables and a flagon of beer or two (that's the stuff to give the troops!). Feel free to tweak the numbers if you disagree. All together, I'd guess maybe 2-4lbs, so let's say 3lbs per person. I'd estimate the price at 5sp, although it depends what the economy is like in your game, and what different things cost. If the PCs want to pay a little more for more compact food, raise the price to 1gp or so.
Thus, if we have a party of 4 (human, half-elf and two dwarves) who can be expected to eat about the same, one day of food for everyone weighs about 12lbs and costs 2gp. If they are going to be travelling for a week, that's (7 x 12 =) 84lbs and (7 x 2 =) 14gp. However, after 2 days they decide to turn back. After 4 days' travel, they're back home. Take off (4 x 12 =) 48 lbs of weight to leave 36 lbs of food (12 days of food for one person, or three days for four people).
The advantage of this is that if the group is exploring a dungeon, they can pay for food in days at a time, letting them plan ahead. Also, they and you know when the food should be gone. If you have someone Creating food, then they simply produce their own food-days, which you can add to their total.
Optionally: To simulate spoilage, make food keep for about a week (depending on what it is - if the group pay more, it should last longer) then roll 1d6 for each food-day left. If a 1 comes up, it's spoiled. Increase/decrease the numbers if you want.
This system saves bookkeeping because once you've worked out the price and weight of food-days, you only have a single, small number to keep track of.
I had to take care of something similar for an adventure I ran once (it wasn't Silhouette, not any flavour of D&D, but the principles still apply, I believe).
The PCs were "under siege" in a sort of barrack/tool shed close to a mining entrance. So they had a selection of stuff they could take with themselves, and it was clear they had to try to hide in the tunnels to escape their enemies. This made the logistics (do I take rope or 4 extra rations?) important, because they had not much time, the item selection was limited, but still they couldn't take all with them, and they had no idea if they would need more food, more water, more rope...
Basically I created (designed in Word and printed with my PC) small "character sheets" for the items that they had at their disposal. In case of small items that could be taken together, I created sheets with tick boxes a bit like this:
If someone wanted to carry say, 20 rations, they would just cross off the extra ticks. (And of course I asked them to cross one off whenever someone ate a ration).
For a lantern, for example I'd do something like:
The system I was using wasn't super-fussy about encumbrance, so I winged it (let's say you have 10xSTR+5 carrying capacity - Silhouette stats are 0-based, -5 for your weapons and clothes... Rations "weight" 1/5 of enc unit, lantern is 2/5, 100 yards of rope is 2 units etc.)
This way the players could discuss and take decisions, the items had a token that represented them in play, and consumable could easily be crossed out (the mines were difficult terrain, so in some places you had roll vs. Athletics or lose some random item, like 1d3 rations etc.)
Always remember that RPGs are only interesting when you get to make decisions
Accounting and bookkeeping aren’t interesting because usually they’re less “do I take this or that?” and more “well now, have I forgotten anything?” Even “do I take this or that?” isn’t very interesting if you have no information to go on: if it’s just a toss-up which you take, getting it right doesn’t feel like success and getting it wrong is bad luck rather than a mistake. That’s not interesting.
Therefore, don’t leave supply issues too open-ended. This causes problems of almost “reverse-metagaming,” where the player doesn’t know (or remember) things that the character would. Make sure you indicate to your players what options they have (in a general way and of course leave them opportunities to be clever). If supplies are short, make it clear what options would be obvious to them, and what consequences they can reasonably expect for doing so.
I left out the Cleric because, well, the Cleric would just be: