Hoyer, I think you didn't clearly read or understand my my comment; there was no way for us to ignore your code addition. When we launched the game, opened our sheets, and began engaging in combat, the macros didn't work. We, of course, had no idea why this was happening, and had to stop our game for about 20 minutes to find out what the issue was - and try to find a workaround. We hadn't done anything more than open our sheets - and the attack macro function was broken; We had no way to option out , one way or the other. We have an international team of players, and time is EXTREMELY important and limited, due to time zone considerations; we don't have the time to sort out this kind of sudden loss of functionality due to your actions. I had been doing prep for this game earlier in this week, testing various token abilities in combat, etc, and did not run into this in any of my previous test runs.. I've been speaking with Roll20 support about this recurring issue with your changes and their effects, and they confirm that your changes don't merit the awarding of a new character sheet version; I think it became clear to me why. Visually , there is no difference between Diane P.'s original working (if a bit clunky) version, and your "upgrades" - even though you have substantially changed what the sheet does - the appearance is the same. You have the coding ability to make the changes for the macros and add abilities and changes, but not, apparently the ability to make a new character sheet layout design. If you did that, I think the Roll20 Team would have no issues in granting you a new character sheet version & we won't have to deal with sudden losses in function because of your "improvements" while we are playing on Roll20.