Transfer: Difference between revisions

1,016 bytes removed ,  22 June 2022
→‎To Generation VIII (as well as Pokémon: Let's Go, Pikachu! and Let's Go, Eevee!): massive deduplication; delegating technical details to the HOME article (e.g. the BDSP blocks for Nincada and "2 Dialgas" is *not* because of cloning glitches)
(→‎To Generation VIII (as well as Pokémon: Let's Go, Pikachu! and Let's Go, Eevee!): false (some Mythicals in SwSh not in Galar dex and not even obtainable via event with the right origin mark))
(→‎To Generation VIII (as well as Pokémon: Let's Go, Pikachu! and Let's Go, Eevee!): massive deduplication; delegating technical details to the HOME article (e.g. the BDSP blocks for Nincada and "2 Dialgas" is *not* because of cloning glitches))
Line 107: Line 107:
{{-}}
{{-}}


In Pokémon: Let's Go, Pikachu! and Let's Go, Eevee! and Generation VIII, not all Pokémon exist in the coding of each game, and HOME will only permit a Pokémon to be withdrawn if they exist in the coding of the destination game. Compatible Pokémon for a particular game may be expanded with updates over time.
In Pokémon: Let's Go, Pikachu! and Let's Go, Eevee! and Generation VIII, not all Pokémon and forms exist in the coding of each game, and HOME will only permit a Pokémon to be withdrawn if both the Pokémon and the specific form exists in the coding of the destination game. Compatible Pokémon for a particular game may be expanded with updates over time.


The following 69 Pokémon that lack a compatible game in Generation VIII cannot be withdrawn into Generation VIII at all:
The following 69 Pokémon that lack a compatible game in Generation VIII cannot be withdrawn into Generation VIII at all:
Line 184: Line 184:
{{reflist|group=note}}
{{reflist|group=note}}


In addition to the above, some games may impose further restrictions on transferring:
Additional transfer restrictions:
* [[Pokémon: Let's Go, Pikachu! and Let's Go, Eevee!]] (LGPE):
* [[Gigantamax]] Factor {{p|Meowth}}, {{p|Pikachu}} and {{p|Eevee}} cannot be transferred to [[Pokémon Brilliant Diamond and Shining Pearl]] or {{g|Legends: Arceus}}.
** LGPE may only withdraw Pokémon with National Pokédex #001 - 151, as well as {{p|Meltan}} and {{p|Melmetal}}.
* {{p|Spinda}} cannot be transferred in either direction between HOME and Brilliant Diamond/Shining Pearl.
* [[Pokémon Sword and Shield]]:
* {{p|Nincada}} originally from Brilliant Diamond/Shining Pearl cannot be withdrawn in any game other than (another copy of) Brilliant Diamond/Shining Pearl, and Nincada originally from outside of Brilliant Diamond/Shining Pearl cannot be withdrawn in Brilliant Diamond/Shining Pearl.
** Sword and Shield may not withdraw any Hisuian regional variants.
* If one Brilliant Diamond/Shining Pearl save file has two of a Pokémon species that is normally only [[caught|catchable]] once per save file (such as {{p|Dialga}} or {{p|Palkia}}), and neither has been deposited into HOME before, only one may be deposited, even if the two have different [[OT]]s.
* [[Pokémon Brilliant Diamond and Shining Pearl]] (BDSP):
 
** BDSP may not withdraw any Alolan, Galarian, or Hisuian regional variants.
These restrictions occur for a variety of technical and [[glitch]]-prevention reasons (see the [[Pokémon HOME#Limitations|Limitations]] section of the [[Pokémon HOME]] article for details).
** {{p|Spinda}} cannot be transferred between Pokémon HOME and BDSP because of a [[List of glitches (Generation VIII)#Spinda spot pattern glitch|bug]] in the latter game, which causes the encryption constant to be read as a {{wp|Endianness|big-endian}} value (i.e. bytes are read in reverse order), and the possibility to indirectly change Spinda's spot pattern.<ref>[https://twitter.com/Atrius97/status/1500557458623778819?s=20&t=mTXrhj_q08wVglb4s7RrVw @Atrius97]</ref><ref name="serebii-twitter 1">[https://twitter.com/SerebiiNet/status/1526896501653381122?t=yR4quQbGSrUSh1d2BDJfVQ&s=19 @SerebiiNet]</ref>
** {{p|Nincada}} cannot be transferred to BDSP due to [[cloning glitches|clone-related glitches]],<ref name="serebii-twitter 1"/> but Nincada originating in BDSP can be transferred outside of the game.
** [[Gigantamax]] Factor {{p|Meowth}}, {{p|Pikachu}} and {{p|Eevee}} cannot be transferred to BDSP. This is to prevent them from [[evolution|evolving]] while still having the Gigantamax Factor.<ref name="serebii-twitter 1"/><ref name="serebii-twitter 2">[https://twitter.com/SerebiiNet/status/1526900020011745282?s=20&t=EjiW0CDu0avbVjizmVLcmA @SerebiiNet]</ref>
** Pokémon from BDSP that are normally only available once per save file (such as {{p|Dialga}} or {{p|Palkia}}) may only be transferred once per BDSP save file and HOME account.
* {{g|Legends: Arceus}}:
** Legends: Arceus may not withdraw non-Hisuian regional variants, with the exceptions of Johtonian Sneasel, Alolan Vulpix, and Alolan Ninetales.
** [[Gigantamax]] Factor {{p|Pikachu}} and {{p|Eevee}} cannot be transferred to {{g|Legends: Arceus}}. This is to prevent them from [[evolution|evolving]] while still having the Gigantamax Factor.<ref name="serebii-twitter 1"/><ref name="serebii-twitter 2"/>


====Moveset alteration====
====Moveset alteration====
Unlike previous generations, games in Generation VIII have significant coding differences, and thus cannot [[trade]] with each other outside of paired versions. In this sense, the generation is split into three "game environments": Sword and Shield, Brilliant Diamond and Shining Pearl, and Legends: Arceus.
Similar to the situation between Sun/Moon/Ultra Sun/Ultra Moon and Let's Go, Pikachu!/Let's Go, Eevee!, the three paired releases of Generation VIII have significant coding differences, and thus cannot [[trade]] with each other (direct trade is only possible with another copy of the same game or its paired counterpart). In this sense, the generation is split into three "game environments": Sword/Shield, Brilliant Diamond/Shining Pearl, and Legends: Arceus.


Different game environments also have different [[move]] lists. To allow Pokémon to be transferred despite these differences, HOME tracks the game-specific data of each Pokémon, and assigns appropriate movesets whenever the Pokémon's game environment changes.  
Different game environments also have different [[move]] lists. To allow Pokémon to be transferred between them despite these differences, HOME tracks the game-specific data of each Pokémon, and assigns appropriate movesets whenever the Pokémon's game environment changes.  
* If the Pokémon enters a game environment that it has never been in before, it will be assigned a moveset of the 4 most-recent level-up moves for a Pokémon of its species and level in the target game.  
* If a Pokémon enters a game environment that it has never been in before, it will be assigned a moveset of its 4 most recent level-up moves in the destination game.
** Example: a level 20 Pikachu caught in Sword is transferred to Brilliant Diamond. Upon arrival in Brilliant Diamond, the Pikachu will have a moveset of [[Spark]], [[Feint]], [[Electro Ball]], and [[Double Team]].
** Example: a level 20 Pikachu caught in Sword is transferred to Brilliant Diamond. Upon arrival in Brilliant Diamond, the Pikachu will have a moveset of [[Spark]], [[Feint]], [[Electro Ball]], and [[Double Team]].
* If the Pokémon returns to a game environment that it has previously been in before, its moveset data for that environment will be restored.
* If the Pokémon returns to a game environment that it has previously been in before, it will regain its previous moveset data for that environment.
** Example: if the Pikachu from the previous example is transferred back into Sword or Shield, its moveset from the last time it was in Sword or Shield will be restored. If it is transferred into Brilliant Diamond again, its moveset from the last time it was in Brilliant Diamond or Shining Pearl will be restored.
** Example: if the Pikachu from the previous example is transferred back into Sword or Shield, its moveset from the last time it was in Sword or Shield will be restored. If it is transferred into Brilliant Diamond again, its moveset from the last time it was in Brilliant Diamond or Shining Pearl will be restored.


2,613

edits