ROM Hack Backing up / restoring all saves ...

Escape1975 · Jan 15, 2021

I'm using JKSV and I see the option of dumping all saves, which creates a JKSV folder on the SD card,
but it seems in order to restore back on a new SD card for example I have to both start every game
in order to re-create the save, then restore one by one ... is there a batch restore maybe ?

Lacius · Jan 15, 2021

No, since saves can't be restored unless they've been played at least once.

Escape1975 · Jan 15, 2021

Lacius said:
No, since saves can't be restored unless they've been played at least once.

Ok, I see, it would be nice then to have a mass restore feature for saves that have been played once,
and the restore would grab the newest save available ... oh well

Lacius · Jan 15, 2021

Escape1975 said:
Ok, I see, it would be nice then to have a mass restore feature for saves that have been played once,
and the restore would grab the newest save available ... oh well

That would create obvious problems, since people would batch restore and think they restored everything, but things could and would get skipped.

Escape1975 · Jan 15, 2021

Lacius said:
That would create obvious problems, since people would batch restore and think they restored everything, but things could and would get skipped.

True, it would be nice when migrating between SD cards when using emuNAND though.

Lacius · Jan 15, 2021

Escape1975 said:
True, it would be nice when migrating between SD cards when using emuNAND though.

You can just copy the emuMMC from one SD to the other, and all save files will copy over.

Or, better yet, don't use an emuMMC.

Escape1975 · Jan 15, 2021

Lacius said:
You can just copy the emuMMC from one SD to the other, and all save files will copy over.

Or, better yet, don't use an emuMMC.

Yeah I was just thinking emuMMC is safer as everything is virtual,
and as far as performance goes it shouldn't make much difference ...

Lacius · Jan 15, 2021

Escape1975 said:
Yeah I was just thinking emuMMC is safer as everything is virtual,
and as far as performance goes it shouldn't make much difference ...

Unless you plan on using online play with a clean sysMMC (or you have an ipatched system on 4.1.0), there is no reason to use an emuMMC.

Escape1975 · Jan 15, 2021

I think I figured it out, the only difference between emuNAND and sysNAND would be one config line,
and of course comment lines starting with # have to be removed for it to actually read the config ...

[config]
autoboot=0
autoboot_list=0
autohosoff=1
autonogc=1
backlight=100
bootwait=3
updater2p=1

[Atmosphere]
# emummcforce=1 (emuNAND)
# emummc_force_disable=1 (sysNAND)
emummc_force_disable=1
fss0=atmosphere/fusee-secondary.bin
icon=bootloader/res/icon_payload.bmp
kip1patch=nosigchk

[Stock]
emummc_force_disable=1
fss0=atmosphere/fusee-secondary.bin
icon=bootloader/res/icon_switch.bmp
stock=1

ROM Hack Backing up / restoring all saves ...

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Similar threads

Popular threads in this forum