Reply to thread

Message

<blockquote data-quote="spinozajack" data-source="post: 6594319" data-attributes="member: 6794198">I believe you have to look at the statistical effect on incoming damage vs a range of to-hit values vs your base AC, to figure out the DR value for a given attack's base damage.So, make it proportional to the expected damage reduction of AC 10 to your armor's AC, on a range of attacks. Then you simply print out a lookup table with the precise value that AC 11 - 25 values would reduce average damage by (averaged across a great many attacks), and use that table of Incoming Damage vs Taken Damage, with each row in the table be in 1 HP of incoming damage increments.You just need one printout for each armor type, or armor type + shield. So 9 tables total, hand the one out to the player who's using DR and have them do a lookup in the table to see what damage they take given what armor they are currently wearing.Perfectly balanced to the base game maths when you consider a large number of attacks. And fast too. Table lookups are easy and straightfoward. If the player gets tired of it, they just revert to the base AC system again. Easy opt-in optional rule, works per-player too to keep them balanced versus the group. Except a slight penalty to status effects on hits which would of course happen much more often. Heavy Armor Master's flat 3 DR could still be useful and incorporated into the table itself, to give a greater chance at completely negating a hit, including status effects. You could treat 0 damage as a miss from a rules standpoint when deciding whether a save is necessary for status effects. Or do it on a case by case basis. Maybe wolves don't get easy bite grapples on plate armor wearers unless their teeth sink into an exposed area and draw blood. Poison saves shouldn't happen when 0 damage is taken either.</blockquote>

[QUOTE="spinozajack, post: 6594319, member: 6794198"] I believe you have to look at the statistical effect on incoming damage vs a range of to-hit values vs your base AC, to figure out the DR value for a given attack's base damage. So, make it proportional to the expected damage reduction of AC 10 to your armor's AC, on a range of attacks. Then you simply print out a lookup table with the precise value that AC 11 - 25 values would reduce average damage by (averaged across a great many attacks), and use that table of Incoming Damage vs Taken Damage, with each row in the table be in 1 HP of incoming damage increments. You just need one printout for each armor type, or armor type + shield. So 9 tables total, hand the one out to the player who's using DR and have them do a lookup in the table to see what damage they take given what armor they are currently wearing. Perfectly balanced to the base game maths when you consider a large number of attacks. And fast too. Table lookups are easy and straightfoward. If the player gets tired of it, they just revert to the base AC system again. Easy opt-in optional rule, works per-player too to keep them balanced versus the group. Except a slight penalty to status effects on hits which would of course happen much more often. Heavy Armor Master's flat 3 DR could still be useful and incorporated into the table itself, to give a greater chance at completely negating a hit, including status effects. You could treat 0 damage as a miss from a rules standpoint when deciding whether a save is necessary for status effects. Or do it on a case by case basis. Maybe wolves don't get easy bite grapples on plate armor wearers unless their teeth sink into an exposed area and draw blood. Poison saves shouldn't happen when 0 damage is taken either. [/QUOTE]

Verification