Hey, I'm using a Pi 2B, which works nicely most of the time.
And it's quite straightforward to use it these days, as you can use a preconfigured system like Recalbox or Retropie and you're good to go.
To reiterate the problem I encountered, my Pi is offline and I only let it fetch the time from my phone's internet to set the correct time within the emulator before playing a game with a clock function.
I simply forgot it once, saved, and now the game always claims it was saved on 2076/01/01, no matter how much I save running the correct date again.
I guess it's simply to protect the raid and event system, but as a downside, it disables it completely should your save file and current time conflict once.
I'll possibly have a look at the save file later. Without elaborating much further (could be a grey area), the protection mechanism has to be stored somewhere.
On a side note, I loaded the game and corresponding "faulty" save directly on my phone running RetroArch, the correct time and all, loading and saving still triggers the protection, which was expected.
So for now, my options are the attempt mentioned above, restarting, or resume on 2076/01/02. X-(
