Thanks for the response! I'll add some clarifications here as well: Nicole B. said: 1. Consistency between roll templates However, it's not clear to me how much of the roll template syntax will be available for custom macros. They should be available for custom macros just like anything else - can you clarify where exactly you're hoping this to work so I can double check? Unfortunately, many people use the word macros to encompass a lot of things, so while the intention is all of the syntax is available for custom macros, I'd definitely like to make sure exactly what you're asking for is covered here. If it helps you to look yourself, the simple roll template is the one that exists (attack is next but is getting a bit held up by indicating crits/fumbles at the moment). With the 2014 sheet, there is fairly clear documentation for each roll template that allows a player to manually recreate/use the template. Just take the sections and fill in as desired, such as for the 'traits' template: &{template:traits} {{name=Traits Name}} {{source=Source:Source type}} {{description=Trait description}} You can even hover over the element while inspecting the HTML to see the component parts (this is inspecting the 2014 character sheet) : But the 2024 roll templates are designed in a completely different way that seems to obscure the individual parts of the template (this is inspecting the 2024 character sheet) : This is from inspecting the output that appears in chat: As far as I can tell, the 2024 sheet uses roll templates, but it would be impossible for me to create a macro that uses the roll template manually. What syntax would be entered into chat to recreate a roll that comes from the sheet? 2. Attributes Partial - Some attributes on the sheet are now manually editable, but it appears that there are still a lot of duplication of values that could easily be a single value ('ac' versus 'npc_ac') I'm guessing that a lot of the attributes are not going to change (there's no reason to change the 'experience' attribute that I can think of), but there is definitely a lot of bloat and unused 'legacy' attributes on the current character sheet. For instance, there are a ton of 'npc_*****' attributes on the sheet, that may as well be the same as the non-NPC values and just have a single attribute that is used whether the sheet is set to PC or NPC. There are other issues, such as the 'class' versus 'multiclass1' attributes and they show on the sheet versus how they combine into 'class_display'. Unfortunately, this has to be how it is for macro reasons. We've gotten an ocean of requests of basically "we want every attribute that already existed", and this is the first piece of feedback I've ever seen that's actually taken into account that we could make the attributes cleaner, return more relevant data, and not return duplicate data if we didn't do that. But, if we stop returning `npc_name`, then that means that every macro that uses that will only work on the 2014 sheet. Because multi-sheet games are such a powerful tool for us, we don't want to split from the 2014 sheet on attributes and have macros only work on half of them. We could remove them from the token bar display though, that's one flexibility option we have on Beacon sheets that we don't have on older sheets. Someday I dream of a future where we can add attributes that expose all the detail of our actual data structure and let people go wild with editing each piece individually and seeing how they all fit together, but we have to make all 2014 macros work first. Or at least, all the ones that make even a little sense in this new context. I'm super confused by this response. I can't think of a situation where I want to use the same exact macro on a 2014 sheet as the 2024 sheet. Or maybe I'm not understanding what others have asked for when saying "we want every attribute that already existed". If the 2024 sheet was at parity (with additional features) with the 2014 sheet, then I would forgo using the 2014 sheet altogether and just have characters and macros using the 2024 sheet. Which leads me to another point: I also do not want roll template names to be reused for both 2014 and 2024 sheets. That will break macros, just like how the 'default' template has been co-opted so that the legacy purple default template is no longer available and instead displays in the new format. I know this has been expressed by others in the forums as well. But my initial feedback point was that the 2024 sheet should absolutely have " attributes cleaner, return more relevant data, and not return duplicate data". I'd be curious to see examples of feedback or suggestions you have received that is implicitly or explicitly asking for the attributes to remain in the same format that they currently do, such as having both 'ac' and 'npc_ac' on a single character sheet, or what the use case is for that to be set up that way. Personally, if I had a PC character that I needed to convert into an NPC (and have different stats for some reason), it seems that it would be much easier to simply duplicate the character and create an NPC version, instead of using a single character that toggles back and forth between PC and NPC with different stats. Allow 'numerical' fields to accept non-numerical inputs or attribute calls This is still under development - we need to do some Beacon work to make it return something other than just the result. Right now, everything in roll syntax works with Beacon (except grouping, I believe), but the problem is the sheet isn't getting enough data to actually show the details of your roll. For example, if we passed in 3d10r<5, we would get "here are all your rolls: 10, 2, 3, 5, 7" and "here's your result: 22" and, since the parsing of the syntax is done on the VTT side and not on the sheet side, we wouldn't know how to work with those rolls. We're working on a better solution right now so the sheet can display these things accurately. It's a big project that has to be touched by a lot of people that all have more projects than time, but we're making progress on that front. No. This is even worse than the 2014 sheet, because there's no way to set the 'npc_name' separately from the 'character_name'. Working on this. It was just an NPC oversight that we haven't circled back to fix yet. Yay! It still doesn't look like there's any way to add a 1d4 roll to Saving Throws from Bless. Have you tried adding a Saving Throw Effect? If you drag & drop Bless onto your sheet, you can see exactly how it's set up. The effect section is specifically designed with Bless in mind. Hmm, I think I had an old 'Bless' effect on the sheet or something because it does look different now that I deleted it and added a new one. I'll edit this above, thanks! Yay! No. I'm not seeing any clear indicators in the spell list for Ritual, Concentration, etc. While this won't match the entirety of this feature request, we are working on a new version of the spells view that will at least cover your desire for an ultra-compact view, always prepared, and some chip separation/distinguishing. Yay! No, but maybe? I played around with modifying a standard Dagger attack for a bit, and I honestly can't tell what is happening with the Critical Damage roll. This might just be bugged and need to be logged and fixed. We recently put in a feature to update an attack's critical damage, specifically to support common homebrew crit rules and other crit-related things, but it seems to have been the victim of a bad code merge and isn't fully functional yet. Another thing I'm looking into today. I looked into a workaround of adding an effect that adds what you need for a brutal critical and turning it on before clicking damage, but because critical damage doubles all dice, that means that adding one results in adding two when you click the crit damage button. So, not ideal. Yay! There are a few I skipped here - mostly the feature requests which I've logged but they have to go in the priority list around what we already have planned and our ongoing bug fixes. I do appreciate the requests for new features to move the sheet forward mixed in with bug reports to shore up what we already have, though. Especially feature requests for things that didn't exist on the 2014 sheet. It's nice to see enthusiasm about what we can do that extends beyond what we already had :) Thank you! Yay! Thank you for the response!