Victor B. said: Nope, I sent email to Roll20. Ravenknight hopefully the same. They've got it messed up so one click doesn't work. Forget about handout version. I'll fix that. Thought it was using the main version variable but I guess it isn't. I'm pretty sure part of the problem is how you haven't followed the usual framework for updating API scripts in the repo, buy creating a new folder for each new version of the API, while leaving the old versions of the API intact in their old folders. Also, for some reason in the script.json it looks like this: " authors " : [ " Victor B " ], instead of this: " authors " : " Victor B " , And even if the old versions of the script where available in the repo, your "previousversion" part doesn't mach with the name of the folder in the repo(the name there is still (2.0): " previousversions " : [ " 2.22 " ], You can look at one of Aaron's APIs that are in the repo for examples on how things look like when they work properly. Oh, and if Combat Master have any version-based script to update something in an active game, I suspect it might have issues due to the lack of having access to older versions of the script. Now that I've looked at API stuff in general, the API repo, and your script, I'm pretty sure I know how to submit a update to an existing API the standard way, as well as fix some of the minor things in how your API exists in the repo. Coming from the Character sheet side, the process is slightly different compared to updating character sheet. Do you want me to submit your v.2.34 to the repo with the related fixes, or do you want to do it yourself? I would expect the back and forth(& possible fix) with Roll20 to take longer than until next Tuesday, when the next Roll20 API update would happen. And if they fix things quicker than that, I can just close down my PR.