Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds another property for NPCs that I believe will greatly improve usability in scenarios where GMs wish to design plug-n-play adversaries that can easily scale up and down.
I believe I followed the established conventions for defining the role property onto the npc data model; as for the implementation and role table (what is used to query which attributes and bonuses are to be applied) I went for a simple approach which is entirely self contained and can be later refactored if need be.
A remaining sub-task to be done after is to restore an NPC's resources after level/role changes, but that is a minor QOL.