I ctr-no-time offset safe to use at any time?

themanuel

Well-Known Member
OP
Member
Joined
Oct 6, 2009
Messages
1,084
Trophies
0
Location
Michigan, USA
XP
607
Country
United States
I modded my New3DS a couple of years ago following the 3dshacks guide, including using no-time-offset. Everything has been working great, but I noticed today my 3DS was reporting 2031 as the date. After making sure I had not accidentally used my powers and traveled to the future, I proceeded to use the no-time-offset app to correct the date. Everything seems fine, except that Checkpoint would throw an error when trying to back up saves: "cannot create destination directory".

I ended up fixing it by deleting the checkpoint directory under the "3ds" directory in the SD card, but I was wondering:
  1. Whether this might have been caused by the date correction
  2. Whether the date correction might cause other issues when used arbitrarily like I did
Caveat: I did update the Checkpoint app today, but the updated version had worked before correcting the date. I mention it in case there is a convergence of issues clouding the situation here.
 

godreborn

Welcome to the Machine
Member
Joined
Oct 10, 2009
Messages
38,471
Trophies
3
XP
29,180
Country
United States
I think so. You're supposed to use that, then correct rtc in godmode iirc. I don't think it will harm the system even if you use it later.
 
  • Like
Reactions: themanuel

godreborn

Welcome to the Machine
Member
Joined
Oct 10, 2009
Messages
38,471
Trophies
3
XP
29,180
Country
United States
I'm not sure if you have to use the app you used or not. rtc takes care of things like time-dependent stuff so that you can't cheat by changing the 3ds time or something. I used both. godmode uses rtc time whenever you dump something. I don't know if that's the reason your clock was messed up. the 3ds clock and the rtc are not connected unless the battery dies afaik.
 
  • Like
Reactions: themanuel

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    a_username_that_isnt_cool @ a_username_that_isnt_cool: @Xdqwerty, about to