View source for List of glitches in Generation VII

{{GlitchResearch|USUM details; every non-Poké Transporter related glitch to be checked to see if it still occurs in v1.1 and v1.2}}

This is a '''list of glitches in the [[Generation VII]] [[Pokémon games]]'''.

==Battle glitches==
{{main|List of battle glitches in Generation VII}}

==Overworld glitches==
{{main|List of overworld glitches in Generation VII}}

==Pokémon Sun, Moon, Ultra Sun, and Ultra Moon==
===All versions===
====Case conversion bug====
On the [[text entry]] screen, pressing the X Button causes the last entered character to be converted between uppercase and lowercase. However, the characters that were added in Pokémon X and Y that could not be entered in the [[Generation V]] games are not converted, and are left as-is. The affected characters are É ↔︎ é in English- and German-language games and Ç/Ï/À/È/Ì/Ò/Ù ↔︎ ç/ï/à/è/ì/ò/ù in Spanish-language games. This glitch also exists in [[Generation VI]].

====Emoticon display bug====
[[File:Emoticon display bug.png|thumb|200px|A Pokémon with an affected nickname]]
The emoticons that can be [[Text entry|entered]] in [[nickname]]s and [[Original Trainer]]s in Japanese- and Chinese-language games are displayed incorrectly in the game's main font. For example, a Pokémon nicknamed {{ding|&#xE081;}}{{ding|&#xE082;}}{{ding|&#xE083;}}{{ding|&#xE084;}} (neutral face, happy face, sad face, angry face) in a Japanese-language [[Generation VI]] game will have its name displayed as {{ding|&#xE082;}}{{ding|&#xE084;}}{{ding|&#xE083;}}{{ding|&#xE081;}} (happy face, angry face, sad face, neutral face) in the game's main font when transferred to the Generation VII games.

This does not apply to the small font used for nicknames in battle or the font that was used on the [[Pokémon Global Link]], which display the four characters correctly, or to the equivalent emoticons that can be entered in the English-, French-, Italian-, German-, Spanish-, or Korean-language games, which are displayed correctly. While the affected characters cannot be entered in these languages, nicknames and OTs of Pokémon traded from a Japanese- or Chinese-language will still exhibit the bug.

====Giratina Nectar glitch====
If a {{p|Giratina}} in its [[Origin Forme]] has its [[Griseous Orb]] swapped for [[Nectar]], it will take various glitched forms depending on the Nectar's color:
* Red Nectar will return it to its [[Altered Forme]].
* Yellow Nectar will cause it to remain in Origin Forme.
* Pink and Purple Nectar will cause it to take a glitched form with the appearance of its Altered Forme but the cry of a {{p|Rotom}}.

====Thundurus Smart Strike glitch====
Due to a coding error, {{p|Thundurus}} in its {{form|Thundurus|Therian Forme}} cannot learn {{m|Smart Strike}}, even though it can in its Incarnate Forme.

==Pokémon Sun and Moon==
===All versions===
====Alolan Exeggutor trade glitch====
When receiving an {{rf|Alolan}} {{p|Exeggutor}} from a [[trade]], the Pokémon's head part can be seen for a split second on the bottom left of the screen after the [[Poké Ball]] opens.

====GTS morphing glitch====
The player must first deposit a Pokémon onto the GTS that will not be traded during the period of the glitch. Next, the player will need to use the Seek Pokémon option and look up any Pokémon. Once done, the player will need to select a Pokémon that has already been traded for. Afterwards, the player should view the summary of the deposited Pokémon. This will lead to a visual glitch where the model of the deposited Pokémon is replaced with the model of the Pokémon that was viewed last.

{{youtubevid|GbaiQ1kAz-M|shallowkittyartist|Sun|Moon}}

====Legality checking false positives====
Several features in Pokémon Sun and Moon, such as online trading and [[Battle Spot]], check that a Pokémon is legal before allowing it to be traded or used. However, these checks are imperfect, and often believe legitimate Pokémon to be modified.
*For a brief period of time after the [[Pokémon Bank]] update, every Pokémon that can be caught via {{DL|QR Scanner|Island Scan}} could not be used in [[Battle Spot]] or traded on [[GTS]] or via [[Wonder Trade]] if it had its [[Hidden Ability]], due to the game believing the Pokémon to be illegal.
*For a brief period of time after the [[Pokémon Bank]] update, Pokémon caught in a [[Safari Ball]] or [[Dream Ball]] could not be used on Battle Spot.
*For a brief period of time after the [[Pokémon Bank]] update, if a Pokémon whose game of origin is a [[Generation I]] [[Virtual Console]] game but has been evolved into a [[List of cross-generational evolutionary lines|cross-generational evolutionary line]], the Pokémon is thought to be illegal and thus cannot be used on Battle Spot or traded.

====Momentary Evolution sprite glitch====
[[File:Gen7 evolutionglitch.PNG|thumb|A [[Scizor (Pokémon)|Scizor]] appearing for a single frame as the screen fades in before Evolution.]]
During an Evolution, before the "What? (POKéMON) is evolving!" text appears, the model of the evolved Pokémon may appear for a split second at the top-left corner of the screen. For Pokémon with tall models, it is also possible for the model to appear off the screen.

{{youtubevid|s5DeQM08BIo|ChickasaurusGL|Sun|Moon}}

====Pokémon Refresh form cry glitch====
If a [[Generation VII]] Pokémon with an alternate [[form]] is chosen to play with in [[Pokémon Refresh]], its first [[cry]] will be that of its species' default form, regardless of its own form. However, the rest of the time it will use the correct cry. This is only relevant for Pokémon species which have forms that exist outside of battle that have different cries to their default form.

{{p|Oricorio}} Pom-Pom Style, Pa'u Style, and Sensu Style will all use the cry of Baile Style in this instance. Midnight Form Lycanroc uses the cry of Midday Form in this instance.

{{youtubevid|0TdhnNEdXD4|ChickasaurusGL|Sun|Moon}}

====TM text glitch====
If a Pokémon learns a [[TM]], the TM's bag text will be dark black (as if it never learned the TM) instead of gray (as it should be for Pokémon that already know the move).

===Version 1.0 to 1.1 only===
====Scatterbug Egg Moves glitch====
{{GlitchResearch|Which Vivillon Patterns correspond the Scatterbug being unable to learn Egg Moves}}
Prior to version 1.2, depending on the pattern of {{p|Vivillon}} they correspond to, {{p|Scatterbug}} are unable to learn [[Egg Move]]s.<ref>[https://www.reddit.com/r/Vivillon/comments/5qn0xc/egg_moves_glitching Egg Moves Glitching? : Pokémon]</ref><!--

Affected patterns include River Pattern.-->

===Version 1.0 only===
====Evolution move learning glitch====
{{GlitchResearch|Is it only for Pokémon who learn Evolution moves, or for all?}}
Immediately after [[Evolution]], some Pokémon will not attempt to learn moves they would otherwise learn at that level. This glitch only affects moves that the Pokémon also learn at level 1, but not those always learned upon Evolution. For example, {{p|Kadabra}} will not attempt to learn {{m|Confusion}} after evolving at level 16 (but will attempt to learn {{m|Kinesis}}), and {{p|Butterfree}} will not attempt to learn Confusion if evolved at level 11 (but will attempt to learn it after having evolved at level 10).

{{youtubevid|Z7vMIxgVsQY|ChickasaurusGL|Sun|Moon}}

==Pokémon Ultra Sun and Ultra Moon==
===All versions===
====Shiny Partner Cap Pikachu====
At any point after reaching [[Akala Island]], the player can scan a QR code to access [[Pikachu in a cap#Partner Cap|Partner Cap]] {{p|Pikachu}} from a deliveryman at [[Pikachu Valley]]. This Pikachu is intended to never appear as {{Shiny}}. However, instead of checking its [[personality value]] against the [[Trainer ID]] and Secret ID number of Pikachu's [[Original Trainer]] to prevent its personality value from making it Shiny, the game uses the player's data instead.

This Pikachu has a [[Appendix:Fan terminology#TSV|TSV]] of 1009, and as long as the player has a TSV that is not 1009, this Pikachu has a chance of being Shiny.<ref>[https://twitter.com/Atrius97/status/1583498917731532800 Example of RNG abused Shiny Partner Cap Pikachu by Atrius97, via Twitter]</ref> If the player's TSV matches the Pikachu and is also 1009, this Pikachu can never be obtained as Shiny for that player. Shiny Partner Cap Pikachu are identical in appearance to normal Pikachu (aside from playing the typical Shiny sparkle animation upon entering battle), as no Shiny model for Cap Pikachu are programmed into the game.

===Version 1.0 only===
These glitches were fixed in version 1.1.

====Litten crash glitch====
If the player picks {{p|Litten}} as their first partner Pokémon, the game may freeze after the cutscene where player chose the aforementioned first partner ends for an unknown reason.

==Pokémon Let's Go, Pikachu! and Let's Go, Eevee!==
===Partner power-favored Berry overflow glitch===
If the first [[Berry]] [[Partner Play#Feeding|fed]] to the [[partner Pokémon (Let's Go, Pikachu! and Let's Go, Eevee!)|partner Pokémon]] on a given day is a favored [[Golden Razz Berry]] and the current value of the [[Partner Play#Partner powers|partner power]] counter is 10 or higher, the counter will exceed its maximum value of 255 and overflow to a lower value. This is because the game first attempts to add the full amount to the counter before capping it at 100.

==Poké Transporter==
===Poké Transporter name encoding glitch===
If a Pokémon's in-game species name was changed between [[Generation I]] or  [[Generation II]] and [[Generation VII]], [[Poké Transporter]] will mistakenly assume that these Pokémon are nicknamed upon being transported.

====French====
{{GlitchResearch|Confirm every Pokémon this occurs for ([http://pastebin.com/fZX8q3gu full potential list for French])}}
Some Generation I Pokémon include {{wp|diacritic}}s (such as "é") or the {{wp|Typographic ligature|ligature}} œ in their French names, but the Generation I games do not use these special characters in Pokémon's names. If sent through [[Poké Transporter]], the name of the Pokémon will be considered a nickname; it will not adjust to using lower case letters and will not change upon Evolution.

;Pokémon affected
{| class="wikitable"
! rowspan="2" |Pokémon
! colspan="2" |French name
|-
!Gen I
!Gen VII
|-
|{{p|Charmander}}
|SALAMECHE
|Salamèche
|-
|{{p|Clefairy}}
|MELOFEE
|Mélofée
|-
|{{p|Clefable}}
|MELODELFE
|Mélodelfe
|-
|{{p|Exeggcute}}
|NOEUNOEUF
|Nœunœuf
|-
|{{p|Ditto}}
|METAMORPH
|Métamorph
|-
|{{p|Eevee}}
|EVOLI
|Évoli
|}

====Mr. Mime====
In Generation I and Generation II, in English, Italian, and Spanish, {{p|Mr. Mime}} does not have a space in its name. Additionally, in Generation I the point in Mr. Mime's name in these games is the decimal point ({{OBP|Character encoding|Generation I|codepoint}} <code>0xF2</code>) rather than the period (codepoint <code>0xE8</code>) which can be entered in nicknames; Poké Transporter interprets the decimal point as a hyphen, but correctly interprets the period. As a result, Poké Transporter assigns the nickname MR-MIME to unnicknamed Mr. Mime transported from these languages coming from Generation I. For unnicknamed Mr. Mime transported from Generation II, the nickname MR.MIME will be assigned instead.

===Poké Transporter name shift glitch===
If a player attempts to transfer [[MissingNo.]], [['M (00)]] or another [[glitch Pokémon]] to [[Pokémon Bank]] from the 3DS Virtual Console versions of Red, Blue and Yellow, the software will not transfer it, but each Pokémon after it will have its [[nickname]], [[original Trainer]], and [[Trainer ID number]] changed to the nickname, original Trainer, and Trainer ID number of the Pokémon before it.

While Poké Transporter normally changes fully capitalized species names to regular capitalization (e.g. ALAKAZAM to Alakazam), because the shifted names are treated as nicknames, if the name is not the Pokémon's species name the name's capitalization will not be changed. Because glitch Pokémon often have characters in their names that cannot be entered when entering a nickname, such characters will be replaced by a space. This glitch has been confirmed to still occur as of version 1.5 of Poké Transporter.

{{Youtubevid|GLHE2DZ5wCk|channel/UCZz2ixp-5T6VeAPtAMQ5v5Q|name=ChickasaurusGL|Sun|Moon}}

==References==
{{reflist}}

==Related articles==
{{Glitches}}<br>
{{Project GlitchDex notice}}

[[Category:Glitches by game]]

[[de:Bugs in der siebten Generation]]
[[es:Lista de glitches de la séptima generación]]
[[fr:Liste des bugs de la septième génération]]
[[it:Elenco glitch in settima generazione]]
[[zh:游戏漏洞（第七世代）]]