You're also choosing to use Kryx's sheet over Roll20's sheet. You're explicitly requesting roll20 to modify Kryx's code, with or without permission. That, as I said, "steps on Kryx's toes," especially if Kryx has his own plans for the code layout of the sheet. Every coder has their "preferred style" of coding, wherein the code value is the same but the style is different; messing things around without warning is grounds for chaos. Making an exception specifically only for Kryx's sheet, just because it's popular, starts going down a slippery path of "why do you give special attention for that system but not this one." Roll20 is intended to be system-agnostic. Besides, they're not "squashing" Kryx's code. They provided new abilities and shiny tools that require implementation to actually use. Each sheet author needs to write the code to allow implementation. If the FATE sheet author really wanted to, they could stick in the 5srd compendium too. Kryx simply hasn't implemented it yet (because it's harder than just saying "go implement it"). I wish all code were just plug-and-play, but that's just not how code works. EDIT: to make another analogy, it's like the newest version of any program/operating system: Windows 10, iOS 9, Android Marshmallow, Adobe Photoshop. If you want the latest shiniest toys (and better security) you have to switch to the new program/system, which may involve some transition pains, and sometimes you find that it's just not possible because of the way the code is structured. Not everything can or should come with backwards-compatibility (and if you don't believe that, well, I guess this is just the end of things here). And I say this as a Windows 7 user who tried Windows 10, found it incompatibile with my computer, and went back to Win7.