OK, as discussed (see split thread!) I've created a GitHub repo for this project which has tagged versions. If you click here you can see it:
And all the releases that have been done.
It's based on @JMack89427's repo; all I did was standardize the file name and use releases, rather than multiple files in the same directory, to capture the versions. Now anyone who wants a specific version can find them, and we can track changes to the file easily.
If you're a developer on this please DM or send me your GitHub user name! I'll make you a contributor. @keithriley it sounds like you have something ready to merge.
Do we want to go with PR review? Or just merging? Or a free-for-all on master where anyone can merge at any time?
My vote would be PRs, but no requirements for review. It's what I'm going to do. But I'm also just some guy. My next change will be to add automatic version checking like @Cobra built, and I will definitely ask for review.
I don't want to interrupt any development! If you have something to get into this repo, holler any time and I'll make sure you have access.
