1,541
edits
List of glitches (Generation IX): Difference between revisions
→February 27 to March 12, 2023 Poké Portal News Bad Egg
m (→Prior to v1.3.0: Need to check which bugs were resolved in v1.3.0, document any previously unknown bugs, move any that were resolved) |
|||
| Line 106: | Line 106: | ||
If the player attempted to join a 5★ event raid after going online in v1.1.0 during this period, these raids would result in a [[Bad Egg]] instead, due to the lack of species data existing in v1.1.0. These Bad Eggs cannot be hatched, released, or traded, and also set the flag for having caught Walking Wake or Iron Leaves, causing the player to be unable to attempt to catch another. Updating the game to v1.2.0 does not result in the Bad Egg becoming the correct species.<ref>https://twitter.com/Atrius97/status/1630378458034626564</ref> | If the player attempted to join a 5★ event raid after going online in v1.1.0 during this period, these raids would result in a [[Bad Egg]] instead, due to the lack of species data existing in v1.1.0. These Bad Eggs cannot be hatched, released, or traded, and also set the flag for having caught Walking Wake or Iron Leaves, causing the player to be unable to attempt to catch another. Updating the game to v1.2.0 does not result in the Bad Egg becoming the correct species.<ref>https://twitter.com/Atrius97/status/1630378458034626564</ref> | ||
{{YouTubeEmbed|7gtymg7VudU|@Atrius97|Violet|Violet}} | |||
This glitch was partially fixed in Scarlet and Violet v1.3.0, which released April 20, 2023, with v1.3.0 detecting any Bad Eggs present in the savefile and resetting the respective capture flag(s) if a player had obtained a Bad Egg, Additionally, a repeat of the event was scheduled for [[Poké Portal News#May 1 to 14, 2023|May 1 to 14, 2023]] as a direct response <ref>https://twitter.com/Pokemon_cojp/status/1648612433962110976</ref> to the issue, allowing affected players another chance to capture a Walking Wake and/or Iron Leaves. | |||
v1.3.0 also made a change to how Poké Portal News event data was stored, now storing it under version specific blocks in the savefile, preventing event data from a newer game version from being accessed by the player on an outdated game version, hypothetically preventing the original glitch from occurring again in the future. | |||
Despite the v1.3.0 patch notes<ref>https://en-americas-support.nintendo.com/app/answers/detail/a_id/60277/~/how-to-update-pok%C3%A9mon-scarlet-and-pok%C3%A9mon-violet#v130</ref> claiming to resolve the issue, while the patch does properly detect Bad Eggs | Despite the v1.3.0 patch notes<ref>https://en-americas-support.nintendo.com/app/answers/detail/a_id/60277/~/how-to-update-pok%C3%A9mon-scarlet-and-pok%C3%A9mon-violet#v130</ref> claiming to fully resolve the issue, while the patch does properly detect the presence of Bad Eggs, any Bad Eggs obtained during the aforementioned glitched raid event continue to persist in the player's storage after updating to v1.3.0, without any method of removing them, as they still cannot be traded, released, or hatched. | ||
{{YouTubeEmbed|xDTnN-d8QmQ|@Atrius97|Violet|Violet}} | {{YouTubeEmbed|xDTnN-d8QmQ|@Atrius97|Violet|Violet}} | ||