Config saving behavior

[derrekr]

Config saving behavior

[FlameKat53]

kinda related to this issue, i guess.
i think we should save the config to nand on ctrnand:/rw/fastboot3DS/ and not to ctrnand:/fastboot3DS/ of the NAND

[NintendoManiac64]

This inconsistent save-location behavior was really throwing me for a loop when I was trying to get my 3DS to automatically boot into luma3ds CFW when the SD card was removed (the default behavior for boot9strap).

So despite it now being 2 years after the most recent release, I would very much support the idea of being able to save the settings to the NAND even when the SD card is present.

[profi200]

It's designed this way to prevent bricks. The eMMC is not something you can take out and stick in your PC. If something goes wrong on there you have to get a ntrboot flashcard or hardmod to unbrick that. There is also no way we can save the config location because we are relocating the config where this would be saved in.

It was/is a difficult decision.

[NintendoManiac64]

OK, brick prevention is a very legitimate reason for the current behavior.

I think my confusion would have not occurred if it was somehow made more apparent to the user that there are effectively two modes with regards to saving.

In particular, I thought settings were always saved to the SD card regardless, and therefore if there's no SD card then settings can't be saved at all and it just always loaded the default (this is akin to how games on consoles with memory cards work, like the GameCube).

[d0k3]

Actually, the config saving behavior is changed in a recent nightly, allowing you to have your config on NAND only, while still keeping the possibility to override it with a SD config. Maybe try a recent nightly?