Unless someone is willing to pick up where Kryx left off, I believe he's done more than enough for all of us when Roll20 broke the sheet he'd retired. I'm glad he did, as I never did like Roll 20s OGL character sheet, and converting back to it (which, according to the threads on it I still follow, is still in a state of constant development) from the Shaped sheet I've used in my games for years now would be an absolute nightmare. I wish there was a conversion API between these two sheets, but I feel - because of how inconsistent and oversimplified the OGL sheet is - that any conversion would output garbage either way (Shaped to OGL, or OGL to Shaped). It just wouldn't, and perhaps couldn't work. For that reason, I wish that Roll20 would adopt the Shaped model of unique charging of items, more organized framework, and consistent background structure and naming conventions. To do so would mean going through their vast library, step by step, converting everything they find inconsistent until its done. That kind of an overhaul would take years, so it's very unrealistic - and I'm only considering D&D 5e, not Pathfinder and all the other systems they have available. Many people like working with what they have to offer; and technically, its not broken, so I can understand if they don't want to fix it. Its when you go Pro, start dealing with APIs, thats when you see how Shaped shines and OGL offers virtually nothing. Thats the gripe I have; why the people paying the subs end up constantly being forced to use the OGL backbone - devaluing the sub in the process. People could use the Shaped sheet without APIs and see the same performance as OGL (actually, still think Shaped wins here... lol). But with the sheet API, they actually see much more for their Pro subscription. JP said: @Joshua J. this has been addressed several times earlier in the thread. Kryx said: "Update all should work. You can also manually look through each character sheet (which forces them to upgrade)." For me removing a Roll20 module or addon that used the old sheets solved the problem. On the broader monster importer issue: <a href="https://app.roll20.net/forum/post/10428496/is-it-just-me-or-the-pathfinder-companion-api-is-broken/?pageforid=10434523#post-10434523" rel="nofollow">https://app.roll20.net/forum/post/10428496/is-it-just-me-or-the-pathfinder-companion-api-is-broken/?pageforid=10434523#post-10434523</a> The pathfinder importer has similar problems but they seem to somehow be able to resolve them. Could be related.