Right now, I'm leaning towards just failing if the user tries to load a. msu1 contains a ROM or patch, whether or not the user provides an external base ROM, and whether the user loads the. msu1 files as ROMs produces 6 different scenarios, depending on whether or not the. Currently, the only game I know of that is distributed as a ROM is Super Road Blaster, but BS-Zelda also distributes their base ROMs, so they could conceivably release a.
It was brought to my attention that the pack spec allows the pack to either contain a ROM file or a patch file, which complicates things a bit.
msu1 file, and copy it to the same directory. Acquire a copy of Zelda A Link to the Past (unheadered) and rename it "Conkers High Rule Tail (v1.2.3).sfc" to match the. I've already implemented it in the msu-zip branch here: f8da152 and am looking for feedback before merging it into master.įor a test, you can try the Conker's High Rule Tail pack here: msu.zip support already added by OV2, I could add support for it as well here. I had the idea that since this format was nearly identical to the.
As it turns out, the distribution format that they settled on is nearly identical to the existing msu-zip support already added to Snes9x (it's basically just a zip file with a custom file extension), except using the higan naming scheme for the files within the archive, and with the addition of a patch file inside the archive so the MSU-1 patch can be distributed along with the audio and data files. I was recently discussing a project over on byuu's message board to develop a standard distribution format for MSU-1 game packs to simplify life for the end users, especially given the differences between the various implementations (manifests or not, track-#.pcm vs romname-#.pcm, etc), along with a utility to extract the files and rename them properly for each implementation.