to expand on that statement: write the script to let people pull a list of spells from a handout, so long as its formatted properly, (I would suggest making sure it follows standard statblock formatting, a lot of people are familiar with that) and make it available from there. the handouts will have to be made by each person to include in their game, but gives the added benefit of letting them pick and choose which spells belong in their game. (I would add as each player learnt a new spell to add - in fact, I would make them do the work, so make sure that the GM can set permissions on who can use this script when it goes public. you would need to decide if a spell was permanently recorded in a handout (with folders now, thats definately possible and easy to manage) or if it keeps them all in state. I would recommend having it actually use the handout as its medium, and keeping your state clear, as spells are not commonly accessed, and if the API goes down, then they are still available as a handout at least. It would mean that your script has the capability to hook the information from each handout and use it for your scripts as you need it, and that players can access it for reference, if need be. You can also write a smaller one-time script to create and print out what you've already done to handouts, so that you don't have to reformat your work to convert it. all in all, I would say (not that I'm a lawyer or a programmer) that this is probably the best and easiest solution to not lose what you've already done, and to make your work available to the public as well. (an option to copy a spell from the handout to acoba's character sheet spell section would also be awesome, if thats even possible with repeating sections.
