Upgrade your account to a Community Supporter account and remove most of the site ads.
ShortQuests -- individual adventure modules! An all-new collection of digest-sized D&D adventures designed to plug in to your game.

Reply to thread

Message: <blockquote data-quote="Kinematics" data-source="post: 9888005" data-attributes="member: 6932123">First question is, what level is this supposed to be at?Since there are a couple entries that approach 500 effective HP, I would by default assume we're at level 20. However the rogue is at about 70 HP, and even with 0 Con bonus and just average HP values per level, the rogue should be over 100. So that suggest this is not level 20. Except this is for effective HP, so maybe you're penalizing the character for something? I have no idea.Then there's DPR. You have a max of 35 for a Zealot barbarian. I know for certain than 35 DPR is fairly low in the overall scheme of things, if taken to level 20. Barbarians and fighters can easily pass 80 DPR. 35 DPR might show up around levels 5-10, depending on build. The rogue with 12 DPR might be around level 3? Actually, several builds mention feats, so at least level 4.The second question is about the "Efficient Frontier". You've anchored that metric to arbitrary points that have limited correlation, and haven't established why those endpoints are meaningful, or whether that should be a linear formula at all.For example, there can be a minimum number of effective HP below which it's meaningless to have a character of a given level. And the more HP you have, the less that additional HP adds to the character's utility. That suggests there should be a minimum asymptote, and probably a power curve.The third issue is about the correlation between the Efficient Frontier and your character build results.Since the EF line goes through two of the result points, it suggests you simply set the limit of the curve at those two points.  For a meaningful "value" system, it would be more appropriate for the EF line and the data points to be independent. That is, establish the parameters for what you feel the EF line should be, and then compare the data to that, rather than basing the EF line on the data you calculated. In the latter case, all you're saying is that the EF line is the upper limit of what I've made, not that it has any meaning in and of itself.</blockquote>

Verification