Roll20 uses cookies to improve your experience on our site. Cookies enable you to enjoy certain features, social sharing functionality, and tailor message and display ads to your interests on our site and others. They also help us understand how our site is being used. By continuing to use our site, you consent to our use of cookies. Update your cookie preferences .
×
Create a free account

Charactermancer Level+ is not allowing HP selection (Roll or Average) 5e 2014

January 16 (2 weeks ago)

Per the title, 3 different level 8 2014 character sheets have the problem when leveling up to 9.

1. It doesn't always draw the UI properly for the class level dropdown.  Sometimes it just says "Class  [ 1 ]" and it is missing the "Level 8+ [ 1 ] = Level 9"

2. Below that, for HP, it will not allow a click on either Roll or Average.  They both remain unselected.

January 16 (2 weeks ago)
AllHansOnDeck
Roll20 Team

Hello Zaodon -

There are a few possible causes. The most common case we've found has when the Compendium Sharing settings in the campaign have changed (help center article has more here, as well as solutions).

Please let me know if none of these help you out.

January 16 (2 weeks ago)

I have not changed the Compendium Sharing settings for my campaign.

However, since you mentioned it, I went to look anyway, and discovered that you (Roll20) forced the "Free Basic Rules (2024 )" into my 2014 game, and also forced it to Share them.  I did not choose this or edit this.   Seems you did this when you implemented the 2024 rules, and my 2014 characters broke.

I disabled this, and now the Charactermancer works for those characters.

You should send out a communication to all Subscribers about this issue,

January 20 (1 week ago)
AllHansOnDeck
Roll20 Team

Thank you for letting me know that detail. The Free Basic Rules released replace the OGL rules, so that those rules could be visible and editable in Compendium Sharing. That confirmed your experience is due to an issue on the 2014 Sheet.

We have a fix to that problem in QA right now, but as you mentioned disabling can resolve the problem for individual games.