Obtained from <player>'s dad
For index number 0 for Pokémon XD, what if that Eevee (or any one of its evolutions) were to be transferred to a Game Boy Advance game and then transferred to another Pokémon XD game? ht14 02:16, 10 July 2013 (UTC)
In the handheld games
This article implies that a Pokémon can be obtained in Colo, sent to a handheld game, then sent to XD, and it would display an incorrect location in XD. However, it also states that all Pokémon obtained in Orre will have its met location displayed as "met in a trade" in the handheld games. This indicates that the met location is stored, but some other value is forcing the met location to be overridden and displayed as "met in a trade" instead. My guess is that it uses the game of origin value. If it is the game of origin value, does this only occur when it is set to 15 (which does correspond to all bits in that value being set), or do other values also trigger it (e.g., any value in which the first bit or first two bits are set)?
Additionally "met in a trade", the supposed met location for Orre Pokémon in the handheld games, is not the message they usually display for Pokémon in locations that do not appear in those games (like Pokémon met in FRLG locations in RS); they would normally display "obtained in a trade". --SnorlaxMonster 11:52, 3 January 2015 (UTC)
- Slight correction: "Met in a trade" is used in FRLG, "obtained in a trade" is used in RSE. --SnorlaxMonster 13:30, 3 January 2015 (UTC)
- It's actually pretty simple: the "met" location is never overriden, the games simply display different text messages on different cases according to the stored values. All games simply store the met location as numerical values rather than a text message, allowing the text to be displayed differently according to the conditions set for each game:
- 1.The game first checks the Pokémon's game identifier. If it's unknown, it will immediately display "met in a trade" (worded differently between games), but if it's identified and has a programmed "location text", it will display that text (will elaborate below).
- 2. If the game identifier is the same as the current game, but the Player's id / Secret id / OT are different than those of the save file, the game will display "apparently met in X location".
- 3. If the game doesn't have a "location text" for a desired value, it will display "met in a trade" rather than the correct text. If a location value exists in game, but the game identifier is not recognized, it will also display "met in a trade". This always happens if the game the Pokémon was generated in is more "recent":
- Ruby and Sapphire only recognize values 0x01 (Sapphire) and 0x02 (Ruby) for "valid" games where Pokémon can come from.
- FireRed and LeafGreen recognize values 0x01, 0x02, 0x04 (FireRed), 0x05 (LeafGreen).
- Colosseum recognizes all of the above plus 0x0F (Colosseum or XD).
- Emerald recognizes all of the above plus 0x03 (Emerald), but does not recognize 0x0F (Colosseum or XD).
- XD recognizes everything of the above.
- In the case of unrecognized games, "fateful encounter" will translate to "met in a trade", since it's a valid location but from a more "recent" game. Emerald will display the correct met area for anything from previous games (excepting NGC games), something R/S and FR/LG only do whithin their pair.
- 4. Met level also directly affects the displayed text:
- If the met level is higher than 0, the summary displays "met at X location".
- If the met level is 0, but the player data is different than the saved file's, then the summary displays "met at level 5".
- If the met level is 0, and the player data matches the saved file's, then the summary displays "hatched at level 5".
- Since NGC games don't have "egg" data, they always display the "met at level 5" message in this case.
- I don't know if I answered your question lol. hfc2X 17:16, 15 July 2015 (UTC)