Given how often people may add and remove levels of varying classes as they try new build ideas, concepts or, like me, just test stuff out - that can get very messy to code. Very few people are going to need this and those that do can easily just record the hit point rolls in the Notes field.
Rollback Post to RevisionRollBack
Click ✨ HERE ✨ For My Youtube Videos featuring Guides, Tips & Tricks for using D&D Beyond. Need help with Homebrew? Check out ✨ thisFAQ/Guide thread ✨ by IamSposta.
If they WERE to code this, I'd recommend only storing a single value per level, which is immediately dumped from storage if the levels are removed. Then add a line warning about this in the dialog box for removing levels.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
It would be great if you could see a history of Hit Points you had on prior levels.
Given how often people may add and remove levels of varying classes as they try new build ideas, concepts or, like me, just test stuff out - that can get very messy to code. Very few people are going to need this and those that do can easily just record the hit point rolls in the Notes field.
Click ✨ HERE ✨ For My Youtube Videos featuring Guides, Tips & Tricks for using D&D Beyond.
Need help with Homebrew? Check out ✨ this FAQ/Guide thread ✨ by IamSposta.
If they WERE to code this, I'd recommend only storing a single value per level, which is immediately dumped from storage if the levels are removed. Then add a line warning about this in the dialog box for removing levels.