Home Creators Posts Import Register Favorites Logout

Downloads

Poll

Rich Text - help me decide how to format Class Features

  • everything on the first line as header 49
  • only the name as header and bold the "info" 32
  • name and info as header, the reference as normal text 78
  • as option 1, but without the bullet point 19
  • as option 2, but without the bullet point 19
  • as option 3, but without the bullet point 21
  • other, I'll comment a better way 0
  • 2025-10-18
  • —2025-10-23
  • 218 votes
{'title': 'Rich Text - help me decide how to format Class Features', 'choices': [{'text': 'everything on the first line as header', 'votes': 49}, {'text': 'only the name as header and bold the "info"', 'votes': 32}, {'text': 'name and info as header, the reference as normal text', 'votes': 78}, {'text': 'as option 1, but without the bullet point', 'votes': 19}, {'text': 'as option 2, but without the bullet point', 'votes': 19}, {'text': 'as option 3, but without the bullet point', 'votes': 21}, {'text': "other, I'll comment a better way", 'votes': 0}], 'closes_at': datetime.datetime(2025, 10, 23, 22, 0, tzinfo=datetime.timezone.utc), 'created_at': datetime.datetime(2025, 10, 18, 23, 59, 42, tzinfo=datetime.timezone.utc), 'description': None, 'allow_multiple': False, 'total_votes': 218}

Content

How do you think the Class Features should be formatted?See the options in action with the MPMB Rich Text Tester.pdf

As you can read in the public announcement post, rich text formatting is a new feature that will be introduced with the 2024 edition sheet.

One of the many upsides of adding these formatting options is that the Class Features will no longer need to be indented to be readable. This will make it much easier to transcribe class features for use in the sheet as it removes the need for manual line breaks and leading three spaces, thus allowing for more text to be displayed–less need for awkward wording.

I would like to ask you how I should format the Class Features added by the automation. I've come up with 6 options, but feel free to comment alternatives.

MPMB Rich Text Tester.pdf

Please use the attached MPMB Rich Text Tester.pdf to try the possibilities for yourself and perhaps you can come up with a more readable way to format the class features than the 6 provided options.

Be aware that this PDF works just like the character sheet in that it requires Adobe Acrobat Reader DC (available here for free) on Windows or macOS to function. It leverages the same AcroJS as the character sheet, thus won't work on any other software.

Files

Comments

Alex Jabornik

Hey it says that I do not have permission to access the file?

Noldere

Not sure why normal downloads aren't working, but you'll need to be logged in within the browser it sends you in order to get the file.

morepurplemorebetter

What link did you click? Does clicking on the attachment on the post work? Patreon makes it harder with every change to link to an attachment of a post that hasn't gone live, so it might well be that the link in the email doesn't work.

Alex Jabornik

Worked it out. While I'm logged in on the app, trying to open the file opens the link in Chrome, where I wasn't logged in

morepurplemorebetter

Thus the attachment works, but the links in the post don't? Note that the attachment is different from the links in the post. Patreon attaches the file at the bottom of the post. Not sure how that displays in the app though. But the attachment is a PDF that only works in Adobe Acrobat Reader DC on Windows or macOS, just like the sheets themselves.

morepurplemorebetter

Thanks for pointing that out Noldere, I'm guessing that is exactly the issue for people using the app.

David MacDonald

What about abbreviating the class (Ftr, Clr, Pal, etc) and the Subclass (or just state "Subclass") as the features are listed under each Class anyway for multiclass? Might save some extra space. People should know their class/subclass lol. So using your example: Rage (Bbn 1, PHB'24 51) [+3 damage, regain 1/SR, 4× per long rest] Frenzy (PotBz 3, PHB'24 54) #[+3d6 damage] or Frenzy (Subclass 3, PHB'24 54) #[+3d6 damage]

PhanZero

I prefer the 2nd option - it separates the different feats with the bullet points (especially important if we add our own stylizing to text) and highlights the most important bits of information for better reading during play.

Mark Altvater

I voted for #2. The reference info is there, but not bold, like the actual gameplay info.

Elrohill

I prefer between 1st and 2nd with bullet point as good way to visually separate each feature. When in option 1, I would prefer reference text in other colour (maybe grayed out but still bold). In both options - I would see first line with slightly bigger letters - +1 - 1,5px more than it is now?

Lawrence R. Hoy

I like Option 5 (Option 2 without the bullet point for the header row); I think that makes the most sense, since there will be bullet points within the features and this is more like they would look in a rule book.

Gagi Petrovic

Option 3 looks great: the important details are bold. Easy for quickly looking up.

Tobias Turowski

2&3 look equally good to me as a user of the printer friendly version. I might even prefer Option 2, but I already see more people voting for 3, so I clicked that as well. Also: Thank you so much for the continued work. While I appreciate the generosity, I hope you re-activate the billing soon so that you have an income again!! :-O

nitrojane

I like option 1 the best, but option 3 works well too.

morepurplemorebetter

This is a good idea for saving space, but I'm not sure if it wouldn't be introducing too many new abbreviations that will only lead to confusions. Doing this would require defining an abbreviation for each class and subclass, extra workload I would like to avoid at this moment ;) I'll keep it in mind for a possible future change to the sheet.

mark tucker

This is one of the many things I do when reformatting high level multiclass sheets to fit everything important. Sometimes I even just erase the whole Class and page descriptor. They totally know what class they are playing.

Darkon Turas

I lean toward having the header take up less horizontal space to reduce the chance of going to two lines.