Reply to thread

Message

<blockquote data-quote="AaronOfBarbaria" data-source="post: 6728400" data-attributes="member: 6701872">Some of the &quot;errors&quot; listed there are actually not errors at all given the way the monster building system works (build stats &gt; playtest &gt; adjust CR so that it feels right, rather than tweaking the math all across the monster to match what is listed as normal for a particular CR).Example: the Assassin is listed as having erroneous saving throws, skills, passive perception, and attack modifiers. All +1 more than the values assigned for their &quot;fix&quot; - but that is because the Assassin was statted up as CR 9, but playtesting found it a little less potent than expected and its CR was adjusted to 8, which shouldn't include changing it's proficiency bonus because that would necessitate rechecking its probably CR, and would mean needing to keep testing to make sure those new values weren't still less than expected.So really, the errors on that list aren't always actual errors, and indicate a significant way in which the compiler of the list has missed the point - putting the &quot;rough idea&quot; rules for building monsters as a higher priority than actual playtesting results.</blockquote>

[QUOTE="AaronOfBarbaria, post: 6728400, member: 6701872"] Some of the "errors" listed there are actually not errors at all given the way the monster building system works (build stats > playtest > adjust CR so that it feels right, rather than tweaking the math all across the monster to match what is listed as normal for a particular CR). Example: the Assassin is listed as having erroneous saving throws, skills, passive perception, and attack modifiers. All +1 more than the values assigned for their "fix" - but that is because the Assassin was statted up as CR 9, but playtesting found it a little less potent than expected and its CR was adjusted to 8, which shouldn't include changing it's proficiency bonus because that would necessitate rechecking its probably CR, and would mean needing to keep testing to make sure those new values weren't still less than expected. So really, the errors on that list aren't always actual errors, and indicate a significant way in which the compiler of the list has missed the point - putting the "rough idea" rules for building monsters as a higher priority than actual playtesting results. [/QUOTE]

Verification