The Problem There are now several options/features of character sheets and API scripts that require being live on the Roll20 repository to function/test correctly. In addition to this, the current method for updating character sheets or scripts is to copy paste code from the sheet/API editor into a github file and then upload that to github to be merged with the appropriate repository. This method is fraught with possible chances for mistakes/errors to be introduced; incorrectly naming a file, copy and paste errors, or overwriting an incorrect file ( see the recent problem with the Pathfinder sheet for an example ). A Solution If we could point the character sheet drop down selection and the API One-click system at custom repositories character sheet authors could test the default settings option that will be rolling out soon without needing to wait for a merge cycle, script authors could test user options, and instead of needing to code our scripts/sheets in the editor and then C&P the new code to github, we can edit the code on our own forks of the github repository eliminating the possibility that something will be copy and pasted incorrectly and drastically limiting the possibility for a file to be misnamed or incorrectly overwritten without being noticed prior to release. Userbase Impact While the API script part of this suggestion will only affect pro-user games and thus might not have a wide enough impact to justify the change, the character sheet part of this suggestion will help to ensure that the character sheets, which have become such a big feature of games on Roll20 regardless of your subscription level, remain fully functional with as few bugs as possible introduced during the update process. Thank you, Scott
