Riuken
|
I've been trying to find a way to define what I think of as a "reasonable" attribute array using the point-buy system. I think I've got it figured out, and it looks nice in an excel table, but I'm worried it's too complicated to actually use without the spreadsheet.
highest attribute maximum of 17
highest attribute minimum of 15
lowest attribute maximum of 10
lowest attribute minimum of 8
maximum of 1 attribute less than 10
maximum of 2 attributes less than 11
maximum of 1 attribute greater than 16
no more than 2 of the same value
at least 3 positive modifiers
if highest attribute is a 17, use 21 point buy
if highest attribute is a 16, use 23 point buy
if highest attribute is a 15, use 25 point buy
This is all pre-racial. I would normally just give 3 arrays (shown below), but I feel the point-buy with restrictions could give more variety than the arrays. Is it just too hard to navigate?
17, 14, 12, 12, 11, 8
16, 15, 14, 12, 10, 9
15, 15, 14, 14, 11, 10
| Fuzzy-Wuzzy |
Too complicated, and too restrictive. Why must I have an attribute of at least 15?
if highest attribute is a 17, use 21 point buy
if highest attribute is a 16, use 23 point buy
if highest attribute is a 15, use 25 point buy
Much, much easier to increase the cost of 16s and 17s and always use 25 pb. It might not be 100% equivalent to what you have now, but it'll be close enough and it won't cause as many headaches.