Home Creators Posts Import Register Favorites Logout

Content

Massive update to the content in both the 5e (2014) and 5.5e (2024) character sheets. All the 5e (2014) content has been updated to use the newer features of the sheets, such as formatting characters, once per day checkboxes on the spell sheet, and using automated first person conversion for notes of verbose magic items. All races have had their traits updated to use headers and bullet points if space allowed.

As the previous poll decided, the 5.5e (2024) sheet now supports all "legacy content", which is all the content that hasn't been reprinted for the 5.5e rules (i.e. most of it). This legacy content has been changed to adhere to the 5.5e (2024) standards, like capitalisation of game mechanics and running text for class features instead of one-line sentences.

Full disclosure, I did dip my toes into the work of LLMs to help with some of these conversions, see "AI Disclaimer" below.

For a full list of changes to the 5e/legacy content, please see this GitHub release post.

At long last, the documentation for (sub)classes, races and backgrounds has been updated from v12.999 to this latest release, see the v14.2.0 documentation on GitHub and the v14.2.0 documentation on GitHub. This was something I have had on my to-do list for a long time, as you can probably tell from the fact that v12.999 is from December 2017. With some LLM assistance, I have finally found the time and motivation to update the parts of the documentation that were still stuck in the past, see "AI Disclaimer" below.

Click here to get the Character Sheets via Patreon [ https://www.patreon.com/posts/14927098 ]

Click here to get the Character Sheets via MPMB's website [ https://www.flapkan.com/patrons ]

Want to try the sheets without becoming a paid subscirber? Get them on MPMB's website as "Pay What You Want" [ https://www.flapkan.com/ ]

The 5.5e (2024) content is limited to the main three core rulebooks, the Player's Handbook (2024), the Dungeon Master's Guide (2024), the Monster Manual (2025), and all legacy content from 5e (2014) sources that has not been reprinted for 5.5e (2024). Patreon subscribers can expect a poll in the coming days to decide what should be added next.

With so many things changed, there are bound to be bugs. If you encounter something that doesn't work or doesn't seem logical, please let me know! Ideally on the MPMB Discord in the Bug Reporting channel.

This release is the first time I have dipped my toes into the use of a LLM. I have never used one to write code for the sheet, but now I have put one to good use in transforming the 5e content to the 2024 legacy content. Even though I had hoped it wouldn’t come to this, I have seen the writing on the wall and decided that for transforming the 5e legacy content to the 2024 standard, a LLM could be a useful tool.

Everything has been reviewed by a human (me). This was a more daunting task than I had first envisioned. While a LLM rewrote things in mere minutes, it often took many hours for me to read and correct everything.

A LLM has only been used to help:

Add formatting characters (make racial traits into headers, make spell and magic item names italic, and make creatures bold).

Remove line breaks in class features.

Find and report typos.

Report content that doesn’t fit their allotted space (mostly because of the formatting changes).

Format documentation to the newer style.

Find attributes missing from the documentation and suggest initial texts for their documentation.

Changes in 5.5e (2024) sheet

Content

Added all content from official 5e (2014) publications that has not (yet) been reprinted in the 2024 rules.

Fixed the Lifedrinker Eldritch Invocation (again), this time for not being selectable and causing an error (thanks PhanZero for reporting).

Fixed the Tenser’s Floating Disk spell (thanks Openhandbadger for reporting).

Fixed capitalization of “Action” to adhere to PHB’24 standards.

Addressed some more overflowing content, mostly only noticeable when metric units are enabled.

Fixed Find Familiar companion not getting any notes on the Colourful sheet.

Added a `submenu` attribute to every Eldritch Invocation so the selection process is cleaner.

Fixed missing `size` attribute to Halfling.

Added `height` and `weight` attributes to Drow and Wood Elf.

Fixed Wizard’s Spell Mastery and Signature Spells.

Bug Fixes

Fixed selecting class starting equipment not adding starting GP when the GP field is empty (thanks Thomas for reporting).

Fixed subrace selection pop-up showing even if only one subrace is selectable.

Fixed no traits/bons/ideals/flaws from a `BackgroundList` or `BackgroundSubList` entry being shown in the menu if any of those four were missing from the object. Now any that exist are shown, even if not all four are present.

Fixed a bug that caused selecting the parent species and then selecting the same variant as before to have no species features to be applied.

Improvements

Updated how spell information displays to how it appears in the PHB’24, “Level 3 Evocation” instead of “3rd-level evocation spell”.

Updated `AddWarlockInvocation` to now also add a `submenu` entry if the passed object doesn’t have it.

Syntax Fixes / Changes

Fixed backward compatibility of `BackgroundList.ideal` being an array.

Changed `AddRacialVariant` to `AddSubRace` to better reflect what it does. The old name is now a reference to this new function, so both still work.

Made `isWeapon` now be true if the type of an attack includes the word “weapon”. This makes coding magic items that functions are weapons but aren’t Simple or Martial easier to have bonuses from other things apply to it when set through `calcChanges.atkAdd` and `.atkCalc` (e.g. Barbarian’s Rage).

Added v24.2.0 documentation for `BackgroundList`, `BackgroundSubList`, `BackgroundFeatureList`, `ClassList`, `ClassSubList`, `RaceList`, and `RaceSubList`. This was done with the help of an LLM but manually checked and corrected.

Changes in 5e (2014) sheet

Content

Replaced `toUni` with formatting characters.

Applied formatting characters to names of spells and magic items.

Updated formatting of race traits to new standard of using bullet points and headers.

Updated formatting of `descriptionFull` and `toNotesPage` to new standard for readability.

Added [THIS] to `CreatureList` entries and removed average dice values from them.

Replace `prereqeval` with `minlevel` where possible for `extrachoices` class feature.

Fixed Armor +1/+2/+3, Ammunition +1/+2/+3, Weapon +1/+2/+3, and the Manuals/Tomes that permanently increase ability scores (thanks Zyneras for reporting).

Removed Limited Feature entries for spells that already get a “once per” checkbox on the spell sheet page.

Updated Wizard’s Signature Spells to be automated just like the 2024 sheet.

Bug Fixes

Fixed overflowing unearthed arcana "page" column on the spell sheets.

Fixed inconsistencies with selecting racial variants, where using the “Racial Options” button made the race box update with the variant’s name while the pop-up didn’t do that.

Syntax Fixes / Changes

Fixed forward compatibility of `BackgroundList.ideal` not being an array.

Added new attribute `forceVariantSelection` for `RaceList` objects. Setting this to true forces the player to select a racial variant and they will no longer be able to select the “basic” version of the race. This is used by the Dragonborn, for example, as it requires a colour. This attribute is only for v14, in v24 selecting a racial variant is always mandatory.

Added v14.2.0 documentation for `BackgroundList`, `BackgroundSubList`, `BackgroundFeatureList`, `ClassList`, `ClassSubList`, `RaceList`, and `RaceSubList`. This was done with the help of an LLM but manually checked and corrected.

Changes in both 5e (2014) and 5.5e (2024) sheets

Content

Fixed some minor typos.

Made race/species `name` and `sortname` title case to make the dialogs/menus more consistent and easier to read.

Fixed `heightMetric` of the Gnome.

Bug Fixes

Fixed converting units for negative values.

Fixed a unit/decimal change also affecting Unicode fraction not used in relation to a unit.

Fixed formatting of `toNotesPage` that are send to the 3rd page Notes section.

Fixed not being prompted to select the variant of a species if variants are added later (i.e. not built-in).

Fixed creature senses not being parsed correctly on the Wild Shape page.

Fixed Ability Score dialog rows not aligning when DPI scaling is above 100% (thanks Jeremy for reporting).

Fixed error on Adventure Logsheet page (thanks Jeremy for reporting).

Fixed creatures not getting "[THIS]" replaced by the correct name on the Wild Shape page.

Fixed `AddRacialVariant`/`AddSubRace` and `AddBackgroundVariant` not creating proper iterations when the variant already exists.

Fixed `MagicItemsList.chooseGear` handling of armours.

Fixed handling of `RaceSubList` entries setting attributes or features to `null` to not take on the parent `RaceList` attribute/feature.

Fixed listing of racial variants / species lineages (`RaceSubList`) in the race/species inclusion/exclusion dialog.

Improvements

Updated first person conversion to be more robust.

Updated handling of spell ranges to no longer overflow (especially if metric).

Show custom magic item types in the magic item line menu option to select an item.

Syntax Fixes / Changes

Added possibility for `RaceList.trait` to be an array, which is joined with a line break. This way racial traits are easier to read in the code.

Added `formattingChar` to features, traits, and notes of `CreatureList` entries. This attribute sets how the `name` is formatted, possibly removing it completely.

Made the `sortname` or `name` of a species variant used in the pop-up dialog and menu, if defined. `sortname` has priority over `name`.

Added possibility for using `scoresStackable` with `scoresMaximum` so that the 5e (legacy) Manuals/Tomes that do a one-time increase of the maximum can be set without requiring a custom function (thanks Zyneras for reporting).

Made it possible for `spellChanges` to affect `dependencies`.

Fixed incorrect documentation for `MagicItemsList.chooseGear.descriptionChange`.

Files

Comments

Ryan Lay

I was thrilled to see this post... right up until the LLM thing. I can only speak for myself, but I'd rather have to wait months for an update than know an LLM was used to create the product, even for something as simple as formatting. Those things, and the people they enrich, make me sick to my stomach. I'm sorely tempted to take my (admittedly paltry) $1 a month and just find some other solution to character sheets, but I've been using yours for literal years now, so any transition will be difficult. I still might do it, but I need to do some soul searching first. Just, please man, on behalf of artists everywhere, don't touch that clanker garbage again. If there's any "writing on the wall," then it was put there entirely by the people trying to burn our planet to cinders so they can rule over the ashes. Don't believe their lies.

Mark Kranz

MPMB you can ignore that black and white opinion. Those of us in the SW industry are well aware there's a big difference between the soul destroying use of gen ai for replacing art and creativity, and the selective use of it in coding. Even Torvalds has signed off on it! As long as you own and understand the code, it matters little how its produced. And no, I'm not an AI bro or support use of AI assets, art, prose etc, I just think the topic deserves a more nuanced discussion than the usual polarizing 'LLM BAD!' that comes pouring forth any time its mentioned. Keep up the good work, and thanks for all the work you do to support the D&D community.

morepurplemorebetter

Thank you for your honest comment and I understand where you are coming from. The use of a LLM is controversial and it is the reason why I devoted the disclaimer to it. I think that there is a big difference between using a LLM as a tool to help write/debug code and using AI to side-step creative people by ripping off their hard work, often in ill-gotten ways. To give an example, without LLM-support a bug could easily take hours to solve, especially when it is something as trivial as a single character missing/being wrong, while a LLM will find something like that in seconds. I wouldn’t dare use AI-generated images or content (I write my posts myself as you can probably tell from all the mistakes). I’m absolutely dreading the constantly increasing prevalence of AI-slop in my daily experiences. Why does it seem like everyone has collectively stopped putting effort in making posters? With “writing on the wall” I was referring to the fact that I don’t think that currently any actively developed software is completely free of AI usage in one form or another, certainly not any from bigger tech companies that are developing for consumers. I have many friends in the software-development industry and most rave about the possibilities/efficiency that LLMs provide. The (sad) reality is that it is virtually impossible to avoid software created with AI-assistance if you want to use any form of modern platform or social media. However, I agree that we shouldn’t blindly follow the promises of the people developing AI. I am gleefully waiting for the moment that their (financial) house of cards comes tumbling down, albeit not the inevitable effect that will have on the rest of the economy. I promise to keep my use of AI-assistance at a minimum and will not be using AI for creating images, texts, music, or vibe-coding anything. However, some tasks would probably never be done if it wasn’t for an LLM. Getting proper documentation for classes is one example, there is a reason why I hadn’t touched it in 9 years. Another example is adding formatting characters to the 5e content, it would’ve probably taking me weeks to read and cross-reference all that content, thus not worth the effort.

morepurplemorebetter

Thank you for joining in the discussion and providing a more nuanced voice from the point of view of software-development. I wholeheartedly agree with you, there is a big difference between using a LLM as a tool to help write/debug code and using it to side-step creative people by ripping off their hard work, often in ill-gotten ways. I wouldn’t dare use AI-generated images or content (I write my posts myself as you can probably tell from all the mistakes). I’m absolutely dreading the constantly increasing prevalence of AI-slop in my daily experiences. Why does it seem like everyone has collectively stopped putting effort in making posters? I have been late to even give them a try, but in my experience LLM-support can be a good thing for efficiency, although I see how easily it can make you lazy. I enjoy writing code and am stubbornly hoping for a future where all coding tasks haven’t been replaced by AI-prompts. I am also making very sure I’m not crossing over into vibe-coding territory, where I don’t understand or can troubleshoot the code that I’m using.

Mark Kranz

I don't actually disagree with you; honestly, I just want to return to a simpler time without AI, and without the evil choices made to get here. But I don't think we can close this particular Pandora's Box, so I'll accept reality - use it where it makes sense, skip it where it doesn't, and ignore those who go all in. If I ever want to (or can afford to!) AI detox then - just like going vegan - I'm not going to berate others for my lifestyle choices. Anyway, I'll stop filling up MPMB's Patreon with religious arguments. Good luck with your soul-searching, and I hope you can continue to find joy in the wonderful hobby that is TTRPGs