77,624
edits
List of glitches (Generation VIII): Difference between revisions
List of glitches (Generation VIII) (view source)
Revision as of 07:11, 19 September 2023
, 19 September 2023replaced: Pokemon → Pokémon
Bfdifan2006 (talk | contribs) m (→Calculator) |
m (replaced: Pokemon → Pokémon) |
||
| Line 70: | Line 70: | ||
| {{MSP/HOME|0529|Drilbur}}{{p|Drilbur}} || {{m|Mud-Slap}} || {{m|Metal Claw}} || {{no}}<br>{{m|Hydro Pump}} || {{m|Hone Claws}} | | {{MSP/HOME|0529|Drilbur}}{{p|Drilbur}} || {{m|Mud-Slap}} || {{m|Metal Claw}} || {{no}}<br>{{m|Hydro Pump}} || {{m|Hone Claws}} | ||
|- | |- | ||
| {{MSP/HOME|0479W|Rotom}}{{p|Rotom}}<br><small>([[List of Pokémon with form differences#Rotom|Wash Form]])</small> || {{m|Double Team}} || style="background:#999" | | | {{MSP/HOME|0479W|Rotom}}{{p|Rotom}}<br><small>([[List of Pokémon with form differences#Rotom|Wash Form]])</small> || {{m|Double Team}} || style="background:#999" |'''?'''<br>{{m|Discharge}} || {{m|Thunder Shock}} || {{m|Confuse Ray}} | ||
|} | |} | ||
| Line 200: | Line 200: | ||
====Toxic sure-hit glitch==== | ====Toxic sure-hit glitch==== | ||
{{main|Toxic sure-hit glitch}} | {{main|Toxic sure-hit glitch}} | ||
If a {{type|Poison}} Pokémon uses {{m|Toxic}}, any subsequent moves that Pokémon uses in the same turn (possible by using Toxic via {{m|Instruct}} or {{a|Magic Bounce}}) will always hit including when the target is in a [[ | If a {{type|Poison}} Pokémon uses {{m|Toxic}}, any subsequent moves that Pokémon uses in the same turn (possible by using Toxic via {{m|Instruct}} or {{a|Magic Bounce}}) will always hit including when the target is in a [[Status condition#Semi-invulnerable|semi-invulnerable]] state. This glitch also exists in [[Generation VI]] and [[Generation VII|VII]]. This was fixed with the release of version 1.3.1. | ||
{{YouTubeEmbed|fW0-nLf6mz4|WeedleTwineedle|sword|shield}} | {{YouTubeEmbed|fW0-nLf6mz4|WeedleTwineedle|sword|shield}} | ||
| Line 281: | Line 281: | ||
[[File:HOME Mobile v2.1.1 vs v3.0.0 Spinda Comparison.png|thumb|An example of a {{Shiny}} Spinda, showing inconsistent spot patterns when viewed in {{pkmn|HOME}} v2.1.1 (left) and HOME v3.0.0 (right), despite having identical [[encryption constant]]s. ([https://twitter.com/Atrius97/status/1665787431009001472 Source])]] | [[File:HOME Mobile v2.1.1 vs v3.0.0 Spinda Comparison.png|thumb|An example of a {{Shiny}} Spinda, showing inconsistent spot patterns when viewed in {{pkmn|HOME}} v2.1.1 (left) and HOME v3.0.0 (right), despite having identical [[encryption constant]]s. ([https://twitter.com/Atrius97/status/1665787431009001472 Source])]] | ||
[[File:HOME0327 s.png|thumb|The static rendered image of {{Shiny}} Spinda from Pokémon HOME, used in all menus of Pokémon HOME's Switch and mobile apps.]] | [[File:HOME0327 s.png|thumb|The static rendered image of {{Shiny}} Spinda from Pokémon HOME, used in all menus of Pokémon HOME's Switch and mobile apps.]] | ||
When determining {{p|Spinda}}'s spot pattern, Spinda's [[encryption constant]] should be read as a {{wp|Endianness|little-endian}} value. However, Brilliant Diamond and Shining Pearl instead mistakenly read it as a big-endian value, effectively reading the bytes in the opposite of the intended order, causing the spot pattern to be rendered incorrectly. For example, a value of <code><span style="background:#FF9999">12</span><span style="background:#9999FF">34</span><span style="background:#99FF99">56</span><span style="background:#FFFF99">78</span></code> (hexadecimal) would be interpreted as <code><span style="background:#FF9999">78</span><span style="background:#9999FF">56</span><span style="background:#99FF99">34</span><span style="background:#FFFF99">12</span></code> instead.<ref>[https://twitter.com/Atrius97/status/1500557458623778819 @Atrius97]</ref> | When determining {{p|Spinda}}'s spot pattern, Spinda's [[encryption constant]] should be read as a {{wp|Endianness|little-endian}} value. However, Brilliant Diamond and Shining Pearl instead mistakenly read it as a big-endian value, effectively reading the bytes in the opposite of the intended order, causing the spot pattern to be rendered incorrectly. For example, a value of <code><span style="background:#FF9999">12</span><span style="background:#9999FF">34</span><span style="background:#99FF99">56</span><span style="background:#FFFF99">78</span></code> (hexadecimal) would be interpreted as <code><span style="background:#FF9999">78</span><span style="background:#9999FF">56</span><span style="background:#99FF99">34</span><span style="background:#FFFF99">12</span></code> instead.<ref>[https://twitter.com/Atrius97/status/1500557458623778819 @Atrius97]</ref> Due to this bug, Spinda is not allowed to be transferred between these games and [[Pokémon HOME]].<ref>[https://twitter.com/SerebiiNet/status/1526896501653381122 @SerebiiNet]</ref> | ||
In [[Pokémon HOME]] v3.0.0, an additional glitch appeared in the mobile app version of HOME. In HOME v2.1.1 and prior versions, when opening the [[summary]] of a Spinda in the mobile app, Spinda would display the correct spot pattern, identical to its appearance in [[Generation VI]] and below. In HOME v3.0.0, all Spinda were displayed as having the same pattern as the static rendered image used in all HOME menus, appearing to use the encryption constant <code><span style="background:#FF9999">7A</span><span style="background:#9999FF">39</span><span style="background:#99FF99">78</span><span style="background:#FFFF99">66</span></code><ref>https://twitter.com/Atrius97/status/1676088622943207424</ref> | In [[Pokémon HOME]] v3.0.0, an additional glitch appeared in the mobile app version of HOME. In HOME v2.1.1 and prior versions, when opening the [[summary]] of a Spinda in the mobile app, Spinda would display the correct spot pattern, identical to its appearance in [[Generation VI]] and below. In HOME v3.0.0, all Spinda were displayed as having the same pattern as the static rendered image used in all HOME menus, appearing to use the encryption constant <code><span style="background:#FF9999">7A</span><span style="background:#9999FF">39</span><span style="background:#99FF99">78</span><span style="background:#FFFF99">66</span></code>,<ref>https://twitter.com/Atrius97/status/1676088622943207424</ref> regardless of the Spinda's actual encryption constant value.<ref>https://twitter.com/Atrius97/status/1665787431009001472</ref> | ||
The encryption constant of Spinda in HOME remained unchanged, (which meant that if transferred out of HOME into a compatible game, they would have likely retained their original spot pattern), however HOME's mobile app no longer displayed the spot pattern associated with the encryption constant of a given individual Spinda, all appearing identical to the "stock" rendered image of Spinda. This was resolved in v3.0.1.<ref>https://twitter.com/Atrius97/status/1676088622943207424</ref> | The encryption constant of Spinda in HOME remained unchanged, (which meant that if transferred out of HOME into a compatible game, they would have likely retained their original spot pattern), however HOME's mobile app no longer displayed the spot pattern associated with the encryption constant of a given individual Spinda, all appearing identical to the "stock" rendered image of Spinda. This was resolved in v3.0.1.<ref>https://twitter.com/Atrius97/status/1676088622943207424</ref> | ||
| Line 299: | Line 299: | ||
Lingering in certain menus and screens for an extended period of time can cause the sounds of the game to stutter, and eventually cut out entirely, or cause significant framerate issues, eventually leading to a game crash. | Lingering in certain menus and screens for an extended period of time can cause the sounds of the game to stutter, and eventually cut out entirely, or cause significant framerate issues, eventually leading to a game crash. | ||
Notably, the Ball Capsule decoration and preview screens, as well as the post-Contest screen can cause the music and | Notably, the Ball Capsule decoration and preview screens, as well as the post-Contest screen can cause the music and Pokémon cries to stutter and eventually stop working, and scrolling through the Pokédex for an extended period can cause framerate loss and eventually crash the game. | ||
==Sword, Shield, Brilliant Diamond and Shining Pearl== | ==Sword, Shield, Brilliant Diamond and Shining Pearl== | ||