surfarcher
First Post
Interesting. Thanks for letting me know!There is a detailed table bases on combat stats.
Interesting. Thanks for letting me know!There is a detailed table bases on combat stats.
Let's not forget that a +2 shield or a +3 suit of plate armor will definitely require attunement, so using both means that 26ac fighter gets to decide whether he wants to use a decent magic weapon, a ring of resistance, a belt of giant strength, or one of numerous other important items for his last slot.
Yes, you are correct, the Death Knight is too weak so needs to be made more powerful to provide a challenge to the party, thanks to the party having bounded accuracy breaking magic gear.
here is a short table for lingering wounds and rules for massive damage and morale.
The rules are optional. A character needs a formula and possibly special materials and locations (left to the DM). Common items cost 100 GP and require 3rd level; uncommon 500 GP and 3rd level; rare 5,000 GP and 6th level; very rare 50,0000 GP and 11th level; legendary 500,000 GP and 17th level.
A day of crafting (8 hours of work) is worth 25 GP of progress. If the item will cast a spell, the spell must be expended every day during the crafting, but of the spell can be cast once (such as a scroll) the spell needs to be expended only one time. Multiple characters that meet the level prerequisite can cooperate, each contributing 25 GP per day and, if needed, spell slots.
I want to know as a player. My concerns are that a) bounded accuracy at higher levels won't work out quite as 'bounded' in play as it seems on paper (use PHB starting table for wealth & have a heavy armor wearer ready to fight that creature with a +11 mentioned upthread? um... eep!), & b) dealing with monster abilities/resistances while 'undergeared'.
I've already seen a near-TPK in 3.5 from a DM that didn't follow wealth-by-level guidelines (oh, we're level 5, have 1 magic weapon for the entire party - TOTAL, not each - & now you're throwing an incorporeal creature at us? ok, my character runs). Would be nice to have something to at least say 'there's a reason _this_ rule exists' the next time it happens.