ROM Hack Checkpoint extracting old saves

  • Thread starter Thread starter FantasyM
  • Start date Start date
  • Views Views 1,516
  • Replies Replies 11

FantasyM

Active Member
Newcomer
Joined
Jun 17, 2020
Messages
29
Reaction score
3
Trophies
1
Age
29
XP
290
Country
Italy
Hello, so i started having this impossible problem where checkpoint doesn't extract the right file...or at least that's what i see
I tried to re install atmosphere a couple of times, update the .nro file, delete old saves folder....but nothing seems to work
When i launch a game (pokemon in this example) i change my team to be sure to recognize the save, save the game a couple of times (just to be sure), close the game, boot the emummc, extract the saves with checkpoint, go on pkhex, open the save and find that the opened save is an old one, where my team is not changed....but if i put my sd back in the switch and start pokemon, everything is fine, the game starts from where i saved with all the changes i did
Can you help me, i'm kinda losing my mind here
 
i'm using applet mode so it does everything alone
can it be that the save location changed? currently i find the saves in switch/Checkpoint/saves but no matter how many backup i make from checkpoint, how many time i delete the saves folder or anything else, i still find old saves (even with zelda, if i check the jpg in the 6 folders, none of them shows where i saved in game
 
"When i launch a game (pokemon in this example) i change my team to be sure to recognize the save, save the game a couple of times (just to be sure), close the game, boot the emummc"

wait, do you play pokemon on your sysnand and then go turn off your switch and boot into emunand to extract? you know that sysnand and emunand are two separate environment right?
basically if you created your emunand while already having a pokemon save, and then played your pokemon game in sysnand only, its normal that your emunand save will be at an "older state", the one it was when you created emunand

ps : the save is saved in nand, not into the cartridge, its not like 3DS
 
it worked before and i always played on stock and extract from emu
i believe this problem started after i update everything after nintendo update to 10.0.3 (i'm not sure because i didn't export anything since then up to yesterday)

Also, i forgot to say that after i formatted the sd and redid the whole process, i updated pokemon, saved, tried and it worked, but after i returned to stock, it made me download the update again and after that i got the problem back
 
Last edited by FantasyM,
if you created a new emunand before trying to extract its normal, when you setup emunand its cloning the sysnand, but once that is done any modifications done in stock sysnand will not reflect on emunand

its like if you have a hard drive A, you copy it on a hard drive B. If you add and modify files on hard drive A and then go check on hard drive B, you will have the files that you had on A when you did the copy, but not the ones you put or modified after

and in the same way, if you extract a save from emunand, modify it with a tool and then inject it in emunand it will not apply to the file of sysnand, its separate
 
yes i understand what you're saying, but as i said, i never had this problem before
i know that the last time i extracted and modified a pokemon save was in january, but believe me: i played on sys, extracted on emu, modded, restored on emu and went back playing on sys with the modded save
same thing with botw where last time i extracted the save was feb/march
 
Last edited by FantasyM,
well, are you sure you were actually on an emunand then? and not in your sysnand but in cfw? because what you say happened is just impossible, sysnand and emunand are two separate system its like having two switches, saves doesnt magically jump from one to the other

just a precision to be sure : sys and emunand doesnt mean not hacked and hacked, emunand mean icloned nand/mmc content running from sd card, you can be hacked and be on sysnand. are you sure you werent running cfw on sysnand when it worked? and set up an emunand since then?

(i would say that one "possibility" to have a save go from emunand to sysnand would be if you had your emunand connecting to nintendo servers and uploading your save in the cloud, but i dont see how you wouldnt be banned doing that with logs mismatch between your emunand and sysnand, and in any case it wouldnt even be possible since pokemon isnt compatible with cloud save)
 
Last edited by Engezerstorung,
i'll go check, but i'm quite sure i'm doing the same steps as before....maybe i fucked up something when i reinstalled atmosphere
 
or you fucked up the first time, and didnt properly installed emunand, or followed a tutorial that didnt set up emunand and was in sysnand, and when you redid it you were now in actual emunand

but yeah, its totally normal that your emunand save isnt the same as your sysnand one if you played on sysnand since the emunand was created, its the other way around that would be total black magic
 
Last edited by Engezerstorung,
re-did everything, now works...don't know why or what happened and i won't ask
i forgot to update, sorry about that, if mods have to close the question, feel free to do so, thx
 

Site & Scene News

Popular threads in this forum