Apologies, I looked at the timeline of releases, and saw that you followed form wonderfully for your v1.07 release, and it was the one after yours that made the changes. I wanted to personally thank you for your assistance bringing out v1.07.
I need to step back from active development on this project.
The reality is that my current setup is Linux-only, and I no longer have a practical Windows environment available to run or validate the toolchain. The project depends on...
Okay, let me first say that, yes, I know I came back on April 1st, and no, this isn't a prank. I have rewritten my option spec, and it currently leaves some Riivolution edge cases out, in Riivolution each choice in an option can have different...
The project scope is fully limited to NSMBW, this is by design. This allows me to use a signature inside the initial image to verify compatibility between original image (BASE) and Riivolution package (PLG), you can look back at the original spec...
Okay, time for user feedback...
I’m reviewing the current community-led release against my freeze point at v1.06 and noticed a few gaps:
Optional components in a mod aren't able to be expressed in the current PLG spec, and thus are not...
It will likely take a month or longer to do a clean port into Node.js, I know if anyone has seen my workflows before this sounds massive, and that's because, in actuality, it is. I may release an intermediate batch version in the mean time...
I noticed that you did quite a bit of inlining into the main batch file, I would love to discuss with you exactly what does what and if needed expand the spec to accommodate the features you were working around into the spec.
I’ve decided to pick up the mantle again. This time I’m moving toward a cross-platform design targeting Windows (Batch), Linux/Unix (Bash), and the browser via a Node.js runtime engine.
This will be a port of the current community v1.07 with...