WeAreNotTwoGoblinsInACloa
Member
Some templates, such as "Young", must be selected at character creation. They are supposed to come before class levels, and HLO throws a red warning if that's not the case. HLO is acting under the assumption that a character with class levels added has already been played and the template (I'll just keep saying Young as an example) is being incorrectly acquired later.
That ignores how NPC character creation usually flows. It's common for DMs to go back and forth to different parts of a character, tinkering, adding, and removing features. In practice, it's much more likely that a DM is adding Young after class levels because this is a new character under construction and the DM chose to apply Young after having already added class levels.
HLO's red warning would be fine if it was possible to manually reposition Young to the bottom of the template/class list. However, it's not possible to do that. The only way to make HLO happy here is to remove and then re-add the class levels, which could be a very large burden if class features have already been selected.
Allowing repositioning of templates and class levels would be a useful enhancement.
That ignores how NPC character creation usually flows. It's common for DMs to go back and forth to different parts of a character, tinkering, adding, and removing features. In practice, it's much more likely that a DM is adding Young after class levels because this is a new character under construction and the DM chose to apply Young after having already added class levels.
HLO's red warning would be fine if it was possible to manually reposition Young to the bottom of the template/class list. However, it's not possible to do that. The only way to make HLO happy here is to remove and then re-add the class levels, which could be a very large burden if class features have already been selected.
Allowing repositioning of templates and class levels would be a useful enhancement.