also:
- update script integrity link
- add some credits
- version bump
- reword some warnings a little bit to be mildly less polite
- disambiguate missing-graphic CIA install fail (14g)
More robust check for MSET9
- If user-id1 is detected, attempt to rename it. Then silently also check for hax'd ID1 to avoid a second prompt.
- If hax'd ID1 is detected (but no user-id1), attempt to remove it
- Eject and reinsert SD to ensure that sysnand sd mounts
Original PR by @Naim2000
Modified extensively by @J0n-b0, then polished by myself
Co-Authored-By: thepikachugamer <44107089+naim2000@users.noreply.github.com>
Co-Authored-By: J0n-b0 <119065467+j0n-b0@users.noreply.github.com>
readme: use new file paths
readme: separate between automatic builds and manual file placement
readme: minor grammar/word fixes
docs: update behaviour from #1
docs: fix a wrong word
The script expects a `finalize` directory in the root of romfs, which
is where all the files are.
3dstool is simple-minded; when specified a folder as the romfs target,
that folder becomes the root of romfs. This causes the built romfs to
have no `finalize` directory.
Move `finalize` to `romfs/finalize` and use the `romfs` directory for
3dstool.
Add a temporary variable that can be replaced externally, via `sed` or
other mechanism.
Let our GitHub Actions workflow add the sha256sum of the built romfs.
finalize_helper
- check for a few more cases of user error (finalize (x).romfs)
- add error #25 if gm9 fails to boot (=gm9 does not exist = insufficient sd space)
finalize.gm9
- add logic to skip CIA installation