I'm wondering why all of the actions are buried in the feats section, while also formatted like the feats, and separated into two lists? Like, considering the actions you gain from your class, feats and race may end up being used every turn. Like saves, health, and attacks (which actions & activities often include), actions belong on the first page, so that tab flipping is kept to a minimum. Additionally, reactions & free actions should be merged into the actions list, for consistency's sake. No need to divvie them up, when they all use almost identical language. They could be differentiated without expanding them by having their action icon in front of the name. The current UI for the actions input is also pretty janky. There's not a field to put requirements, even though that is a common component of actions language. Additionally, the way of an action's cost is identified is a little wacky. Reactions and free actions get radio buttons, which is fine, but weirdly differentiated; regular actions just have a text box, that's then outputted as action type? When that's almost not even a concept in 2e? To ruminate on it for a minute, I can't imagine why it's even an editable field, when really there are only 5 options, ever. Free Action Reaction 1 Action 2 Actions 3 Actions And then you could combine both their purposes in a single box type. In fact... Feature Request Actions Feature Flow Brief Description : The Actions and Reactions & Free Actions sections should be combined into a single area, which can be done by switching out the radio buttons and the textbox with a single drop down menu that labels it as the type/number of actions. This could then be moved to the character tab, where it would be most useful, considering a lot of these actions could be used every turn. I would slot it in between Perception and Language proficiency boxes, opposite to attacks. I realize I kinda ripped into your work up there, and I'd like to say I mean nothing rude. Just trying to give good constructive feed back, and currently the implementation of Actions is possibly the most messy of a major system in this sheet right now. I do like a lot of what the sheet does, and am excited to see how it may evolve!