Resourcepack Generator

[OpenBagTwo]

Upon merge, this PR will resolve #1 by adding a simple-to-use resourcepack generator to this repo.

Done So Far

• Created a script that will loop over all files in a folder and convert any music files (that is, files recognized by ffmpeg as having decodable audio) to ogg. The script also generatse language files from parsed metadata and creates unique textures for "record items" for each track.
• Described the basic usage in the README (that is: plop the executable in a folder full of music, then run it)
• Built out a command-line interface that allows specifying alternative input and output files
• Built out a wildly over-complicated configuration system that will allow power-users an absurd level of control and customization. YAGNI? For sure. Did I learn a lot? I guess. :laughing:

To Do

• [x] The script still needs to either generate a new foxnap.yaml config or otherwise indicate the number of tracks to set in the config.
• [x] Add python unit testing to the GitHub actions
• Manually create and test builds on the following platforms:
  • [x] Desktop Linux x86
  • [x] Steam Deck (peculiarities about the read-only filesystem blah blah)
  • Raspberry Pi arm64 (this is a nice-to-have)
  • [x] MacOS Intel
  • [x] MacOS arm64
  • [x] Windows 10 or 11
• [x] For all of the above platforms possible, automatically create builds GitHub Actions
• For all of the above platforms possible, automatically test CI-created builds via GitHub Actions, explicitly:
  • Python unit tests (covered by the second bullet)
  • [x] ./FoxNapRPG --version prints a valid version (and not "0+unknown")
  • [x] ./FoxNapPRG with no other flags scans the current working directory and generates a resource pack in the current working directory (these should be downloadable artifacts to allow for manual inspection and testing with the mod)

[OpenBagTwo]

Got builds going for Windows, macOS and Linux, but at some point it looks like I broke versioneer.

[OpenBagTwo]

Fixed version-freezing. Yay!

[OpenBagTwo]

I'm going to de-scope Linux arm64 builds for now (pending https://github.com/actions/runner-images/issues/5631) and instead change the action item to providing instructions for manual building on arm64 devices.

Regarding automatic testing on all platforms: the explicit risk to call out isn't that the unit tests fail (though that's a concern) but that the launcher won't work.

Double-click-to-execute is not something I can automatically test with GitHub's CI runners, but I can test calling the executables from the command line and running against either a test folder or against the oggs already in the mod source (that won't test that the decoders are working, but that's also the least likely thing to break) and explicitly verify:

• calling ./FoxNapRPG --version reports the correct version (and not "0+unknown")
• calling ./FoxNapRPG with no flags grabs the file from the cwd and generates a zip in the cwd

[OpenBagTwo]

Oh, also noting that the macOS build appears to be either a universal binary or at least runs well through Rosetta 2--had no issues running on either an M1 Macbook Air or a 2012 (Intel) Macbook Pro

[OpenBagTwo]

Well that's been a journey, but I've actually got everything working how I want it for now.

Before merging, I just want to call out some:

Tech Debt

• Build artifacts have gotten enormous with the inclusion of not just the converted music in the resource packs, but the raw tracks as well. Also bear in mind that there are three sets--one for each OS. At some point GitHub might actually care.
• README contains no instructions for custom spec configurations.