homeEntertainment

'Overwatch' problems & fix news 2016: Blizzard to fix 'Mercy' bug following latest game update

A screenshot from Blizzard Entertainment\'s new game, \"Overwatch\" | Overwatch

Blizzard Entertainment's newly-released game offering this year, "Overwatch," has been well-received by gamers, and to further make the experience more exciting and thrilling, the game studio has been making updates on the features. However, the most recent update did not turn out quite well for some players due to a resulting bug.

The latest game update brought some interesting tweaks in the gameplay, especially with the newly introduced competitive gameplay. Unfortunately, errors can still be expected following every quick update. Specifically, a bug that is affecting the character of Mercy has been reported by the gamers. It appears that Mercy could not be used as effectively as the previous days when the latest update was not yet implemented.

Gear Nuke reported that the particular bug has been a big issue for the gamers as they turned to different online forums such as Reddit and "Overwatch" threads to express their concerns. The update was released by Blizzard last June 28, and since then, those players using Mercy have been noticing a major bug on the character. Moreover, when the players are trying to fix their target using Mercy, they have to re-arrange the target focus every time the players change streams. It might have been a normal occurrence, but it was noted that before the recent patch update, the targets do not need to be reacquired after the players change streams.

It turns out the many players are experiencing this problem, and Blizzard was quick to address the issue. The game developer company confirmed via "Overwatch" forums that their recent patch update has caused a glitch on Mercy. "Overwatch" principal game designer Geoff Goodman revealed in a statement that the target bug was unintentional. He apologized to the players who experienced the inconvenience and promised that Blizzard will find a fix to this bug very soon.