While Nintendo 3DS is probably the folder they'll end up putting it in (many people confuse that with the root), there are other folders that the script can detect. They really don't need to know where they misplaced it, just that they did, and they should enter the keycombo to fix it.
choo choo, all aboard the train to OCS
* finalizing: switch to file-management scriptrunner
Switch to scriptrunner for file management (to lessen user error from incorrectly copying files).
Thus, users will need to copy just two files: finalize_helper.firm to SD:/luma/payloads/ (which will have to be created by the user) and finalize.romfs (which ends up on root of SD).
This change allows for better checking of file integrity and lessens the chance of user error from incorrectly copying files.
The scriptrunner's task is to load finalize.romfs from the SD card, unpack it, and to copy its contents to root of SD.
The intended location of finalize.romfs is root of SD, but the scriptrunner will attempt to move the file if it is found in SD:/Nintendo 3DS, SD:/DCIM, SD:/luma, or SD:/luma/payloads.
Remove errors relating to missing files (since that should no longer be possible).
Add visuals on the top screen for error resolution, with QR codes to the guide / NH where appropriate.
* finalizing: inline chainloader
in case people have more than one payload
While Seedminer is now deprecated, it has been a page on the guide for
more than 5 years, so it's guaranteed to be linked basically everywhere.
So instead, let's stub this.
As MSET9 has mostly matured, we will no longer need several other
exploits.
The following are removed:
- alternate-exploits (and all linked by it)
- All seedminer-related paths
- firmware update pages
- MSET9 now has extensive error-checking, which is almost fully accounted for in the troubleshooting (save for errors that shouldn't happen)
- Enhanced troubleshooting for ID1, pulled from the visual troubleshooter. Commonized and used for Seedminer multiple ID1 scenarios
- Update MSET9 page to account for mset9 v1.1
- Finalizing script v1.5.1 to remove errors.txt
people had been interpreting this as "execute mset9.py" / ignoring the bullet points, which on windows would make it so the script closes when an error occurs instead of displaying the error
- Reword uninstalling mset9 to removing mset9 for consistency and so that people hopefully don't skip it
- Add an additional message right before the finalizing setup link to make even fewer people skip it, hopefully
- Move Assert id0 troubleshooting to the top of mset9 (it's the first error people are likely to encounter)
- Add MSET9 detected to troubleshooting
- Update to script v1.5.0, which adds proper(ish) MSET9 detection
