Hero could do with more granularity. The armour values are abstracted by the system. Although the system is capable of supporting detail if required. You could design armour as, for example 6 DEF vs slashing weapons but 4 DEF vs blunt impact weapons.
Mind you the damage is also abstracted to hit-point equivalents so it isn't that helpful in telling you when you have a bruise and when you have a broken arm.
However, formulas could be used instead of tables. The only reason I see for tables it to maintain some kind of artificial intellectual property rights, by using a fictional legacy table generation algorithm.
I'd have far less problem with the tables is there were substantive research as to the results and didn't appear to be numbers drawn out of a hat.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
no subject
Date: 2008-04-10 02:38 am (UTC)Mind you the damage is also abstracted to hit-point equivalents so it isn't that helpful in telling you when you have a bruise and when you have a broken arm.
However, formulas could be used instead of tables. The only reason I see for tables it to maintain some kind of artificial intellectual property rights, by using a fictional legacy table generation algorithm.
I'd have far less problem with the tables is there were substantive research as to the results and didn't appear to be numbers drawn out of a hat.