Be notified of new releases
Create your free GitHub account today to subscribe to this repository for new releases and build software alongside 50 million developers.Sign up
Thanks a ton to @BernardoGiordano for this! Downloading from github should now work again
2 bugs fixed, and 2 minor improvements:
delete_archivesnow actually work!
the self-updater works from the cia correctly now
the self-updater updates the 3dsx if ran from the HBL instead of the installed cia!
the cia now contains the actual version number (needed for fixing the self-updaer)
Note that if you are using version v4.0 with the "broken" self-updater: it will update to this just fine, and it's not actually "broken". It's just the console's way of telling you're already on latest
I now find it ready for release!
You may think it's worse than the previous version, but I only removed "useless" stuff, controls are the same, but the config has more options (self-explanatory).
Writing to nand! The feature 2 and a half persons wanted! Well, it's there at last.
More popular though, is the automatic creation of missing directories when updating something. No more errors when everything went right.
To make it easier for new users, it will also display a message and allow you to download the latest config.json straight from the repo if it doesnt find it. Only need to pop the cia on the SD and install, no worries about a pesky config file ruining the fun.
Nothing major, adds pattern matching to file extraction ("inarchive"), and fixes a little bug that doesnt seem to have been noticed
Fixes github api parsing, and brings in 7z extraction support and wildcards in the config! (only for the inrelease element)
This allows you to add an entry, even if the file you want has its name changing every release! (for example, Luma3DS, and d0k3's tools!)
"inrelease": "Luma3DSv*z",, from the example config.json:
* character after the
v ? it tells the string matching function to keep going until it finds the next character, or the end of the tested string. So here, it matches the
You might be thinking: "You could have used the
. before the extension or the
7z!", well no, and this is the reason why:
It would see the
. in the release/version number, and the rest wouldn't match, so it would miss the correct element! And the release number could include a 7, which would result in the same problem!
Another example: the attached release file below. What
inrelease would match it?
Answer (click to view)
Of course, "MultiUpdater-v3.0.zip" would, but that's cheating. What I wanted was "MultiUpdater-v*zip"!
If you got it right, you understood how the matching function works.
quick fix and release for the github api parsing, allowing for finding the download url of an item in the latest release of a repo.
Long awaited (or not) release, fixes a crash and adds a feature: cia installation!
Just add something to your config that ends up being saved as a .cia
WARNING: might not work from HBL
Brings in backing up/restoring files in case the update breaks something, instructions, and support for local urls in relocation headers.