Miguel said: Hey Folks, just wanted to pass this through the community for some final feedback and to make sure it wont break anyone's experience. A few questions: - Is it enough to decrement the hit dice pool on roll or would you still need the 'minus' button? - When the dialog is open, rolling the button should automatically close it or would you rather have to click the 'close' icon? Click to play: This looks like a good start. A few thoughts: It is not clear from the animation if changing the levels in a class increases/decreases the amount of hit dice by the change in levels or sets it to the same number of hit dice as the level. In your example, if a character had 0d6 and went from level 5 wizard to a level 6 wizard, would going up a level change the number of hit dice to 1d6 or 6d6? It should be 1d6 in this case, because going up a level does not recover hit dice, it just gives you a new one. Going down a level should reduce the maximum by 1, but it should only reduce the current number of hit dice if it exceeds the maximum. The user should see their maximum number of hit dice somewhere in the Hit Dice box. Either the hit dice should be organized in a list instead of a grid, with entries saying something like "X of Yd6", or the text on the bottom could say "Hit Dice (3d10, 6d6)". If a list was used, extra entries could push the attacks and equipment sections down. I really like the ability to quickly spend hit dice one at a time or roll a bunch in bulk. It will greatly benefit high-level play while not introducing a burden on lower-level PCs that only need to spend 1 hit die. My preference is to keep the spinner control that the hit dice already have versus the plus button. Sometimes people accidentally add to many back, and it would be nice to be able to decrement without rolling. It is not clear from the animation how the sheet will handle two classes with the same hit die. It should accumulate and store hit dice of the same size together. So a player with a fighter 2, paladin 8 should see 10d10 rather than 2d10 and 8 d10. Given your comment on the difficulties the companion API would have the with change as it lies currently, I would propose storing hit dice in the backend of the sheet differently. Have the sheet maintain a list of current and max hit dice of all sizes, in order from biggest to smallest. When the player gains a level, it increments the current and maximum for the correct hit die size. Internally, your example would have hit dice maximums be stored as 0d12, 3d10, 0d8, 6d6, and the current hit dice count would be stored in a similarly descending order. The sheet then only displays the hit dice that have a maximum that is greater than 0. By keeping these in order, the companion API can then iterate through the list of current hit dice in order, restore hit dice from largest to smallest, and stop when the hit dice are all recovered or it runs out of hit dice. While a player can recover hit dice in any order they want, it generally only makes sense to recover the largest ones first, so I feel that is a fairly safe default. While the new automation is nice, and the layout is much more clear to the user compared to what is available currently, there is a piece of functionality that is lost. Right now, a player can set the maximum number of hit dice if they have a magic item, feat, or something else that grants a bonus hit die. The settings page should have a section where the player can add an additional number of d12s, d10s, d8s, or d6s. I like that the modal has you choose all the hit dice at once instead of having to choose the number of one size to roll, click OK, choose the number of the next size to roll, click OK, etc. The modal should close when the hit dice are rolled. I am sure this just has not been implemented in time for the demo, but the Constitution bonus should be added to the rolls.