List of glitches (Generation VIII): Difference between revisions

List of glitches (Generation VIII) (view source)

Revision as of 07:21, 6 July 2023

355 bytes added , 6 July 2023

m

→‎Spinda spot pattern glitch

Atrius97

1,545

edits

@@ Line 277: / Line 277: @@
 {{YouTubeEmbed|bYFppn6L3gs|channel/UCPJed1wrXUIdLlUA_W7qznw|name=Hoomanadaw|ice}}
-===Spinda spot pattern glitch===
+===Spinda spot pattern glitches===
 [[File:USUM BDSP Spinda Comparison.png|thumb|An example of a {{Shiny}} Spinda, showing inconsistent spot patterns when viewed in {{g|Ultra Sun and Ultra Moon}} (left) and {{g|Brilliant Diamond and Shining Pearl}} (right), despite having identical [[encryption constant]]s. ([https://twitter.com/Atrius97/status/1483660395906678785 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])]]
@@ Line 283: / Line 283: @@
 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.<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>
+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>
 {{-}}