Pokémon Omega Ruby and Alpha Sapphire are coming this November!
Check BNN and Bulbanews for up-to-date Pokémon news and discuss it on the forums or in our IRC channel.
The Bulbapedia mobile skin is currently in open alpha. If you run into any issues using the skin, please report them on the forums.

Talk:Save data structure in Generation I

From Bulbapedia, the community-driven Pokémon encyclopedia.
Jump to: navigation, search

Need To Create Page

I have information regarding this page, but I don't appear to have the rights to create it. Halp? --GuyPerfect (talk) 17:20, 8 April 2013 (UTC)

To create pages you need to be autoconfirmed, which is achieved by performing a certain number of edits. The number of edits required is unknown. Lady Ariel 21:28, 8 April 2013 (UTC)
I'm sure I'll reach that number while working on this page. Could someone start it for me? (-: --GuyPerfect (talk) 19:59, 9 April 2013 (UTC)
Until you are able to create pages, it would be best if you worked on the page in the Sandbox. Lady Ariel 21:40, 9 April 2013 (UTC)


The character encoding is not a unique feature of the save data structure. It is used by basically any string in the ROM. While no current data structure page for Gen I uses it, I'm sure there are data structures which could be given articles which would use the character encoding. The character encoding simply does not belong in a section here on the save data structure page. Tiddlywinks (talk) 03:51, 1 April 2014 (UTC)

I think the issue with this split is that it is not significant enough to have its own page. That's just my opinion though. --Spriteit (talk) 13:59, 25 April 2014 (UTC)
I think the fact that it doesn't belong on this page is a much more significant issue. As someone who has previously searched this site for this information (and couldn't find it), this isn't the page I would've expected it to be on. While I agree that it'd be pointless to have a page for each generation, we should have one page that includes them all, and talks about the similarities and differences between eacher generation's character encoding.