Ed S. said: I believe what Gediablo is talking about is a per character sheet pop-up not a per game pop-up. The new sheet updates gets pushed and when you open a character sheet it lets you know you are about to upgrade to the new layout, cancelling would just leave the sheet the way it was before it was opened, unconverted. For the benefit of all who may not understand how this works, here's a bit more detail on what's happening and why what you suggest isn't possible. What you see as a character sheet is effectively two separate systems working together. Underneath, there is a big set of named "attributes" that contain information about your character in a particular format - things like "Charisma" and "Proficiency Bonus", but also internal settings that make the sheet work which aren't obviously part of a character's attributes. If you go to the attributes and abilities tab of a character you will see some (but not all) of these attributes. Some of them have values that are fairly obvious, others contain complicated information in specific formats that help the sheet do its stuff but make no sense to an end user. On top of this sits a presentation layer consisting of a limited form of HTML that can display these attributes in the format that you see on the screen. The way that the presentation layer is written depends on the way that the data it displays is stored, and vice-versa. Sometimes it's possible to change one without changing the other, but sometimes, changing the way things are presented requires the way that the data is stored to be change as well. When Kryx releases a new version of the sheet, he often has to change the way the data is stored in order to support new layouts/features. He tries to avoid this wherever possible, but the Roll20 character sheet system is relatively constrained, so he often doesn't have the choices that would be available to a web developer on a more open-ended platform, so he has to make do with what he can. When he updates the way the data is stored, he has to write scripts that upgrade the attributes of old characters to the new format, so that they will work with the new presentation system. These scripts get executed when you open a character sheet for the first time on a new version of the sheet. Now, what happens if you cancel that upgrade script? Well, the data is still stored in the old format. But the presentation layer is the new system, which relies on the attributes being in the new format. So now everything is broken. Well, you might ask, why can't he have an option to not upgrade the presentation side as well? That's what I was talking about in my previous post - doing that would entail effectively having a copy of the sheet HTML for every version that is supported, with some sort of switching mechanism between them. It's not clear to me that's even possible given the constraints on character sheet HTML, but even if it was, it would be incredibly unwieldy, slow, and error-prone in ways that would make people long for the level of problems that we have now! It might look like a case of "just make the upgrade optional", but what actually hides underneath that statement is a world of complexity involving versioning systems, data migrations and lots of complex testing; it's no coincidence that there are multi-million dollar companies whose entire purpose is producing systems to handle this sort of stuff. Expecting Kryx to be able to do it on his own on a platform that provides no support for it is obviously not realistic - but an understandable misunderstanding if you don't know much about how software development works under the covers.