Talk:Masuda method: Difference between revisions

Talk:Masuda method (view source)

Revision as of 13:16, 17 April 2016

1,337 bytes added , 17 April 2016

→‎Update needed for Gen VI mechanics: new section

Chenzw

1,422

edits

@@ Line 132: / Line 132: @@
 [[User:HaunterBaby626|HaunterBaby626]] ([[User talk:HaunterBaby626|talk]]) 16:07, 18 August 2015 (UTC) HaunterBaby626
 :The method of getting the foreign Pokémon does not matter, so yes it would work with IR trading. [[User:Litwick96|<span style="color:purple">Litwick</span>]][[User Talk:Litwick96|<span style="color:grey">96</span>]] 20:10, 18 August 2015 (UTC)
+== Update needed for Gen VI mechanics ==
+This has been brought up a few times before on this discussion page, but I hope to revive the topic again: the article needs to be updated–the Masuda method in Gen VI now looks at game language, although to be technical, the Masuda method has always been looking at game language. The use of "region", "country" or "location" is a misnomer, because in Gen V and before, the language of the game is locked to the game region, leading to the idea that it is the region which matters.
+What 0x17 records in Gen V is the game language ([https://projectpokemon.org/wiki/Pokemon_NDS_Structure#Block_A source]). This was expanded in Gen VI, with the relevant markers being:
+{|
+!Marker (byte)
+!Data recorded
+|-
+|0xE3 (the old 0x17)
+|Language
+|-
+|0xE0
+|Country
+|-
+|0xE1
+|Region
+|-
+|0xE2
+|3DS region
+|}
+x17 in Gen VI now records data relevant to [[Super Training]]. ([https://projectpokemon.org/wiki/Pokemon_X/Y_3DS_Structure#Block_D_.280xB0-0xE7.29 source], with PKHeX also referencing these same bytes)
+xE3 determines the language tag appearing above the dex number in the Pokemon's summary screen. 0xE0, 0xE1, 0xE2 depend on the 3DS settings, and as far as I know, are not visible nor possible to determine in-game. [[User:Chenzw|Chenzw]] ([[User talk:Chenzw|talk]]) 13:16, 17 April 2016 (UTC)