Pokmon Sword and Shield Ability Patch bug can break your Pokmon

October 30, 2020 The Pokémon Company have responded to our query and have assured us that the dev team are aware of the issue and that a fix is forthcoming. No time frame of when the patch will come has been given.

If you’re grinding Pokémon Sword and Shield’s Dynamax Adventures for enough Dynite Ore to give your Pokémon their hidden ability, you might want to hold off on that for the time being.

According to a Reddit post by Possible-Coconut, they used the item on their Entei and Zapdos, only to receive a message when attempting to bring them into a raid that says “There is a problem with the Pokémon you have selected”. These Pokémon had the Battle Ready mark that is given to all eligible Pokémon for use at any point in the game, including raids and competitive battles.

A number of replies indicate that the reason for this is related to the fact that hidden abilities weren’t introduced until Gen 5. According to the user wasked, they experimented with bringing a Nidoking caught in Pokémon Leaf Green all the way to Pokémon HOME and was able to replicate the issue. The same thing happened with those from Gen 4, but not from Gen 5 and upwards. Some have also reported the same issue for Pokémon transferred from the Virtual Console versions of the Gen 1 and Gen 2 Pokémon games.

Some users suggested the issue may be resolved by taking the Pokémon to the Battle Tower to reset its moves, but Possible-Coconut confirmed that they did do this prior to posting about the bug.

Related: Here are all the new Pokémon Crown Tundra moves

This is especially worrying since Pokémon Ranked Series 7 is set to begin in the next couple of days, so people are likely giving their Pokémon hidden abilities in preparation for the new season. If their favourite Pokémon are rendered unusable, this could cause major disruption (and some very upset trainers) in the competitive scene.

We have reached out to The Pokémon Company for a response to when we can expect to see a patch to address this nasty bug.

ncG1vNJzZmivp6x7tbTEpaaanJ%2BqwW%2BvzqZmqaebmrqwuoysrqiqlGKur7CMrJ%2BinZyZfKKuyKWgrbFdpa61r8dmma6f