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

Ilmari said: I've accidentally wiped out a character sheet by accidentally adding the character builder. I was trying to add spells to the new 2024 sheets. Is it possible to recover what I had? As far as I can see, an automated character builder is already a worthless vanity addition that nobody really wants. Now it's destroying the work I'd already done. I hate it. Is there a the DM can turn it off completely so there's no risk of tripping over it? Good morning! The builder should only add to your sheet, not overwrite anything. BUT the builder doesn't know what you've added to your sheet, so it will look like it's "empty". You can just exit at any time, saving your changes as a draft for later or discarding them, using the Exit button in the top right. You may need to access the builder from a desktop to see this button right now, though. You can also just build with nothing selected and nothing will change. I'll pass on the feedback about the worthless vanity addition that no one wants, but the builder is very heavily used, so I suspect we may continue to offer this feature for the forseeable future. I apologize for the disappointment this may cause. You can always combine builder and sheet content as well - unlike older versions of these builders, you can go into the builder, skip to literally any slide, make the choices there, and build, and it will stack with whatever you wrote on the sheet. We actually use this feature frequently as developers to test very specific portions of characters!

Hultz (Keeper of Secrets) said: Keithcurtis said: If the sheet lacks something specific in order for it to work (like an attribute to be exposed), then that thing would need to be identified and a request sent to the team for that specific thing. I briefly contacted Scott C. one of the authors of Easy Experience and he indicated to me that the needed attribute on the 2024 character sheet is not exposed and Roll20 needs to fix that. So.. without using a script, what is the recommended way to update the Experience Point value on the 2024 sheet? I'm going to prioritize read/write access for this attribute next week. Glad to hear he's open to working on the script once that's available!

vÍnce said: Hi Nicole, Just curious, please excuse my ignorance, but is there a downside to exposing all the attributes in the sheet to API Mod access? It depends on what you mean by "all the attributes" here. Like, are you referring to "I want to edit my AC", or are you referring to "I want whatever the database holds and I'll figure out what it means myself"? Because those are two different things with different answers. If the former, there's no downside really, it's just work for each individual one, so it has to be prioritized against other work. Unlike older sheets, where the attributes you might want to access are all just in the database as-is and the work is just "go find the exact attribute you asked for", most of what you want to access isn't like that on the 5.5 sheet. For each attribute a user might want, Beacon asks the sheet "how should we respond to this request?" For XP, it's just an oversight because it is actually just a value we have to pull out and update. It is still work and not something we get automatically, but relative to other attributes that one is pretty light. We do have to individually plan each one, though, so oversights do happen and they have varying levels of difficulty to implement. Most of what you see is actually a combination of a bunch of individual pieces of data run through specific logic to figure out how to display them, so that specific logic has to be rerun if you want something like "what's my maximum HP" or "what's the damage of my flail attack". Inline editing has unlocked a lot of editing attributes though, since we now have a system in place for what it looks like when someone just manually edits their value without care for any of that complexity, which we just recently started dipping into with maximum HP editing. If the latter, there are pros and cons that have been heavily discussed internally. Our data is still  in heavy flux, with the way data is structured changed and updated frequently, and as soon as we give access to that structure to the public, anything anyone does will be built on shaky ground and if it breaks due to our changes, it will be frustrating for everyone involved and we'll begin to fall into a trap of messy backwards compatibility. For example, we're now in the process of deleting a certain property from ~75% of our data as part of our work to improve performance. If we had previously allowed APIs to edit this property, then a lot of APIs could have immediately broken, annoying the users of the API, the devs of the API, and us. There's a whole layer of architecture that would be required to make all the data available, which would have to be prioritized against our other features because it would require dev work and upkeep/maintenance. It would be largely useless without heavy documentation, that we would then have to add "keep that documentation up to date with our weekly changes" to the list of work. Personally, someday I would like to go that route because it's exciting to think of what users might be able to create with that level of freedom, but that's just my personal opinion and we're definitely not in a place today where that would make sense. I tried to write documentation for our data a few months ago and it's over a dozen pages already, with the most intricate pieces of data still unstarted, and it's out of date now lol.

Lypse said: Hi guys, Regarding DND 2024 character sheet. I've tried to create modify an ability to become a heal, but the changes does not seem to save. And I've also tried to add a healing potion from compendium and modify that to act as a heal ability, but when I use it, it still posts to chat window as the healing potion, not the description I changed on the ability/icon it into. Is any attempts at homebrew considered unsupported still, or am I missing something important? Sorry if this was already asked, I cant see where to search this topic. /Alex We've got a ticket to fix this, sorry about that! Hultz (Keeper of Secrets) said: Another GM and I were looking at the 2024 Character builder and tried to build a Treasure. Nice stuff but how can I enable it to be moved and/or opened by a player? I haven't found a way to enable any player permissions on a GM created Treasure Chest. What are we missing here? To be able to see a shop, all you need to do is set it as in that player's journal. In previous character sheets, this would hide the sheet itself from the player and only show them Bio & Info. However, beacon gives us the ability to show a read-only or limited version of a sheet if it's in your journal but you don't have edit access, which we really only take advantage of for shops. Actually transferring the items is work we haven't done yet, although it is on our roadmap . Der Arkanier said: Since, I could not find anything in the patch notes and also not in my roll20 game, just checking if this is still in the making? For reference, here is what I originally reported: - The chat bubbles for all "Effects" on the combat tab don't post anything to chat anymore.  - If I create a free action on the combat tab (or any kind of action for that matter) and add a dice value (e.g. d10) to the field "roll" I can see the goldish colored d10 next to the name of the feature. If I press it, the dice rolls in normal mode but not in query mode. In query more the query window opens correctly but when clicking the roll button in the window, nothing happens.  1. This has been ticketed and is in the sprint (which usually means "next few weeks" but can get pushed back based on higher-priority work coming in), but hasn't started work yet. 2. This should be fixed. I'm not in charge of the change log so I'm not sure if it's been updated yet with the note, but it should say "Added support for action rolls to prompt Query Mode" or something similar.