Table of contents:
Things don't always go as planned. Even professional companies and developers with some experience, such as Niantic. After the last update of mechanics that arrived a few days ago in Pokémon GO, now it's time to go back and remove one of them due to a malfunction. And it is that the new Pokémon exchange options within the trainer battles have not turned out as expected. Something that has led Niantic, Pokémon GO developers to backtrack on the issue
The issue comes hand in hand with not stopping the fighting when switching Pokémon in these confrontations between real players. Thus, Niantic believed that it would be good to show the animation of a Pokémon that reaches the arena and leaves the pokéball as it happens in the series or the rest of the video games, all without the enemy stopping its attack. However, it appears that players are taking advantage of this poorly crafted mechanic, and the depth of trainer battles has reached a new height precisely by allowing Pokémon to attack or take damage while the opponent is introducing their new fighter.
Now, through the official Pokémon GO blog, they announce that the true motivation of the team is to create strategic and intuitive combat, but that this change in mechanics does not achieve that objective.Given the situation that has occurred since this change was implemented on July 9, they have decided that it is best to take a step back and return to the previous combat pause systemAt least until they manage to polish all the problems that this new change of mechanics entails.
Phantom Damage
Apparently the battles between trainers are not as polished as they should be. Proof of this is the phantom damage that can be de alt to Pokémon at the moment of switching from one to another. This practice has been used by players to try to gain a strategic advantage. Niantic's problem is that pausing the game when choosing to switch Pokémon in the middle of combat hasn't solved the problem either.
Not to mention the malfunctioning of the shift button, which doesn't always act as it should. Faced with so many problems in the combat mechanics, the most logical thing is to go back and try to solve the errors before releasing these functions againOf course, now without a specific date.
