Custom Sheets and Non-official Material: What is appropriate?

Hi there! I've got a question about the rules for creating and sharing custom character sheets.&nbsp; I want to take the current 5e Character Sheet and augment it to fit a 5e supplement. This supplement adds a number of features that I would like to put in an appropriate location, and remvoes a few features (certain skills have been folded into others, for ease of play). They rework core classes, add elements and archetypes to old classes, etcetera.&nbsp; My question is this, and relates to this specific Rule from the "Building Character Sheets" code of conduct ( <a href="https://wiki.roll20.net/Building_Character_Sheets#Roll20_Character_Sheets_Repository" rel="nofollow">https://wiki.roll20.net/Building_Character_Sheets#Roll20_Character_Sheets_Repository</a> ):&nbsp; &nbsp; &nbsp;&nbsp; Do not infringe on intellectual property . Community sheets should not include character creation or advancement due to potential copyright restrictions. 'By Roll20' sheets may include this content thanks to our partnerships with game creators. Sheets that are developed from the code of a 'By Roll20' sheet will need to ensure any character creation or advancement options code is removed. It's okay to have attributes that auto-calculate based on other attributes (including the current level). We'll let you know if your submitted sheet violates this rule. Am I interpreting this correctly? It means that I cannot change class names from the class drop downs on the sheet so that they automatically calculate saves, spell casting, and the like, and I cannot add a new method for spell-slot calculation that allows one of their new classes to progress properly?&nbsp; Related question: are these "you cannot do this at all" restrictions, or "you cannot do this and share the character sheet" restrictions?&nbsp;

You can include things you need to be able to play the name, but not things that would help people design their character&nbsp; without a rulebook. This is tricky to adjudicate, and I think is largely ignored on community sheets, but I'm pretty sure they'll be careful to check if you take a "By roll20" sheet and add character design features (using the charactermancer, for instance). The things you've specifically asked about - changing class names, spell-slot calculation changes-&nbsp; are things that should be okay, since there are already sheets built in homebrew versions if D&amp;D that do this kind of thing. One other difficulty you might run into: the 'By Roll20' sheets are roll20's proprietary sheets, and are starting to take advantage of roll20's infrastructure that we dont have access to. If you make a sheet based on the public code of one of their sheets, it might not work fully, because you are missing certain hooks to their backend that they can take advantage of. Thats why none of their sheets in the public repository have been updated for many months: those are the "last public versions" - their newer work is developed in-house, away from our eyes. Their last public version probably works okay, but I vaguely remember something about styling differences between people who are using that code, and using the up-to-date sheets. On your related question: you can do whatever you want in your own games. It only becomes an issue when you seek to share your character sheet or addons.

cool, thanks for the feedback.&nbsp; I'm not looking to write any charactermancer stuff. I'd remove all that code if I felt like going through it, tbh hahahaha. Mostly I just want the class dropdowns to have class options from the books, so that people can click, like, the Barbarian-esque class and get the right saves automatically, you know? If that's cool within the rules, then that makes me happy. awesome.&nbsp; im using the "Legacy" sheet. the new features I wanted was the stuff where, like, Traits on the NPC sheet aren't just text boxes, and the new spell display set up, where you can view a spell card on the spells page. I'm gonna have to reverse engineer the NPC traits thing, that's not in the legacy sheet (last update was two months ago). Bleh