Script Bundling

I have a couple of scripts for a game system I'm working on implementing in Roll20.  Specifically, I have the following scripts written; Die Rolling Character Import I know there's API and Character repo's but I was wondering if it would be against convention to bundle the two scripts together?  Ideally there would be one folder with 2 subfolders, one for each script.  My intention is to give users one single folder to visit to get all current and future scripts for the system.

If you're storing this in your own Git repository, you can handle it however you want to --  you just have to make sure people know where to find it and how much of it they need. If you're going to submit it to Roll20, each script will be its own file/project with its own script.JSON. You could set them up with a dependency of each other (so if they got one from the one-click, they would get the other. Or you could actually copy/paste into a single file and upload that as your project.

The scripts are currently in private GitHub repos, ideally I would like to have them in the public Roll20 GitHub repo. Strictly speaking the scripts are not dependent on one another.  I'll just add them to the repo and let alphabetical sorting take care of the rest.

I really don't see a problem with concatenating them if their purpose is to supplement a specific sheet. There are a number of "Companion Scripts" that do this already. The D&D 5th Edition by Roll20 Companion and Shaped Companion have a Swiss Army Knife of functions. The one thing you want to watch out for is that your sheet does not require using any script. That will disallow it from the Roll20 git collection.

keithcurtis said: The one thing you want to watch out for is that your sheet does not require using any script. That will disallow it from the Roll20 git collection. Interesting, my sheet requires the dice roller I built... I guess that limits me to self hosting :(

I believe this is to maximize the audience for a given sheet. Roll20 does not want to put a subscription bar to just playing. Of course, if this is not a published or at least publicly available game, it wouldn't be allowed in the repo anyway. Rules must be readily available. Sheets can be submitted for independent games and homebrew systems. Homebrew games will need to ensure they are not violating copyright for their respective game system. In both cases, the rules need to be readily available online to the public. There's more information in the Help Center, here .

keithcurtis said: I believe this is to maximize the audience for a given sheet. Roll20 does not want to put a subscription bar to just playing. Of course, if this is not a published or at least publicly available game, it wouldn't be allowed in the repo anyway. Rules must be readily available. Sheets can be submitted for independent games and homebrew systems. Homebrew games will need to ensure they are not violating copyright for their respective game system. In both cases, the rules need to be readily available online to the public. There's more information in the Help Center, here . Thanks for the link, I'm still trying to grok all the rules Roll20 scripters should follow.  I get that the Roll20 team doesn't want to raise the bar to play but my sheet simply won't work with the deault roll API as robust as it is.   Not a huge deal, I'm the author of the game system as well so I'll just put links in the book to my personal company public git repo for players to use.  My repo can be organized as I see fit as well so that's a benefit too.  In a perfect world I would like for players to just go to the Roll20 repo and find what they need but it seems that is not in the cards.