D&D 5E (2024) Character Sheet & Builder by Roll20

Saul J. said: Notice that my earlier message wasn't addressed: If you choose a background from an older book, like Strixhaven: A curriculum of Chaos, the builder doesn't handle the backgrounds correctly. For example, the Strixhaven backgrounds come with a feat (Strixhaven Initiate). But, the builder wants you to choose an Origin feat. According to the PHB, you only choose an Origin feat if the background doesn't already come with one. (See the box on p. 38 of the 2024 PHB). Any plans to fix this? This is something that is important to fix in order to be able to use the new sheet/builder with older non-2024 books. That is on our radar to update for the later backgrounds that offer feats, like these and Spelljammer. We were actually just talking about this today!

Tuo said: Is restoring fully free input on all roll input fields for custom roll expression and full access to sheet templates to be used in macros on that vaunted radar? Or were such core functionalities left on the wayside from the start? It actually is. The sheet does its rolls in a slightly different way than legacy sheets, so we need to make a few updates to make this possible (ex. right now, if you send out a roll that includes rerolls, it will do the rerolls but won't tell us which ones to "drop"), but it's a high priority right now. Frankly, a higher priority than backgrounds that offer feats, but those can be done in parallel anyway so one doesn't have to block the other in that way.

Saul J. said: Is there a timetable/eta for fixing these two problems? Both are really needed before the sheet can even begin to be considered "usable". As it stands now, the sheet and the builder are just an "alpha" concept that is not fully functional. Nicole B. said: It actually is. The sheet does its rolls in a slightly different way than legacy sheets, so we need to make a few updates to make this possible (ex. right now, if you send out a roll that includes rerolls, it will do the rerolls but won't tell us which ones to "drop"), but it's a high priority right now. Frankly, a higher priority than backgrounds that offer feats, but those can be done in parallel anyway so one doesn't have to block the other in that way. I don't have a timetable right now, sorry. This is a high priority but because it's not a one-off "just fix it" kind of issue and touches more than one piece of code, it's going to take some dev effort and multiple rounds of QA and all that that entails. I can say we're starting on the "fixing what Beacon tells us about advanced rolls" either today/tomorrow or early next week, but I can't guarantee the timeframe of finishing all the work.