Talk:Save data structure (Generation II): Difference between revisions

Line 91: Line 91:
:As far as what you wrote above, I don't see any (significant) difference with 1.0. (Fun fact: it looks like the game initializes the non-player names by copying 11 bytes from a place in the ROM. That explains the repetition of names, and also the random data after "MOM".)
:As far as what you wrote above, I don't see any (significant) difference with 1.0. (Fun fact: it looks like the game initializes the non-player names by copying 11 bytes from a place in the ROM. That explains the repetition of names, and also the random data after "MOM".)
:You're right, it should be checked. It's also worth considering, though, that those unused names [http://bulbapedia.bulbagarden.net/w/index.php?title=Save_data_structure_in_Generation_II&diff=2160157&oldid=2160153 were added] by one person. What I mean is, it's always good to check; but in this case, it's also possible that the unused names (and perhaps [http://bulbapedia.bulbagarden.net/w/index.php?title=Save_data_structure_in_Generation_II&diff=2160153&oldid=2097396 Options]) are the outliers. [[User:Tiddlywinks|Tiddlywinks]] ([[User talk:Tiddlywinks|talk]]) 01:08, 18 April 2015 (UTC)
:You're right, it should be checked. It's also worth considering, though, that those unused names [http://bulbapedia.bulbagarden.net/w/index.php?title=Save_data_structure_in_Generation_II&diff=2160157&oldid=2160153 were added] by one person. What I mean is, it's always good to check; but in this case, it's also possible that the unused names (and perhaps [http://bulbapedia.bulbagarden.net/w/index.php?title=Save_data_structure_in_Generation_II&diff=2160153&oldid=2097396 Options]) are the outliers. [[User:Tiddlywinks|Tiddlywinks]] ([[User talk:Tiddlywinks|talk]]) 01:08, 18 April 2015 (UTC)
== Daylight savings offset ==
I'm using the German version of Pokémon Gold to test things with and play around and I found the daylight savings offset to be 0x2050 instead of 0x2037.
Changing the dst at mom's does not affect 0x2037 but instead 0x2050 switches between 0x10000000 and 0x00000000, so I guess it might be correct.
3

edits