77,633
edits
Nickname: Difference between revisions
m
→Detecting unnicknamed Pokémon
m (→Main series) |
|||
| Line 64: | Line 64: | ||
When a Pokémon is migrated from a Generation III game to a Generation IV game via [[Pal Park]], if the migrated Pokémon's current name exactly matches its species name in the Generation IV game's language, it is flagged as being unnicknamed; otherwise, its current name is permanently treated as a nickname. This can result in a Pokémon's species name being permanently treated as a nickname, if it is migrated to a game in a language in which its species name differs from its current name. Since there are no Korean Generation III games (and it is not possible to enter Hangul in any Generation III game), using Pal Park in a Korean Generation IV game will always cause the transferred Pokémon to be treated as having nicknames. Pal Park otherwise requires that both games be the same language, so this is otherwise only a problem for Pokémon traded between languages in Generation III. Pokémon that are [[language of origin|Japanese in origin]] always have Latin letters in their names converted to fullwidth characters, which are considered distinct from regular Latin letters, so cannot be treated as unnicknamed when migrated to a Western language Generation IV game. | When a Pokémon is migrated from a Generation III game to a Generation IV game via [[Pal Park]], if the migrated Pokémon's current name exactly matches its species name in the Generation IV game's language, it is flagged as being unnicknamed; otherwise, its current name is permanently treated as a nickname. This can result in a Pokémon's species name being permanently treated as a nickname, if it is migrated to a game in a language in which its species name differs from its current name. Since there are no Korean Generation III games (and it is not possible to enter Hangul in any Generation III game), using Pal Park in a Korean Generation IV game will always cause the transferred Pokémon to be treated as having nicknames. Pal Park otherwise requires that both games be the same language, so this is otherwise only a problem for Pokémon traded between languages in Generation III. Pokémon that are [[language of origin|Japanese in origin]] always have Latin letters in their names converted to fullwidth characters, which are considered distinct from regular Latin letters, so cannot be treated as unnicknamed when migrated to a Western language Generation IV game. | ||
When a Pokémon is migrated from a Generation I or II Virtual Console game to | When a Pokémon is migrated from a Generation I or II Virtual Console game to {{g|Bank}} via [[Poké Transporter]], if the migrated Pokémon's current name exactly matches its species name in the language of the game it was transferred from, it is flagged as being unnicknamed; otherwise, its current name is permanently treated as a nickname. Due to [[List of glitches (Generation VII)#Poké Transporter name encoding glitch|bugs in how Poké Transporter detects unnicknamed Pokémon]], some unnicknamed Pokémon can have their names turned into nicknames upon transfer. Unnicknamed {{p|Mr. Mime}} (in English, French, Italian, and Spanish) becomes nicknamed "MR.MIME" instead; prior to Version 1.3, it became nicknamed "MR-MIME". Prior to Version 1.3, English unnicknamed {{p|Farfetch'd}} became nicknamed "FARFETCH D" upon transfer. Due to Poké Transporter not accounting for the fact that French Generation I and II games do not use {{wp|diacritic}}s or {{wp|Typographic ligature|ligature}}s in Pokémon species names, unnicknamed French Pokémon whose names include those characters are also treated as being nicknamed. | ||
===Transferring nicknamed Pokémon=== | ===Transferring nicknamed Pokémon=== | ||