Due to the game’s refusal to load them into matches, Overwatch 2 players receive “unfair” bans, leaving them with leaver penalties that cannot be reversed. The video game Overwatch 2 could be better. There were absurdly long loading times when it first came out, and during the early launch matches, there were sporadic disconnections. But now that Overwatch 2 has been out for almost six months, most of these bugs have been fixed. Players continue to report loading-related problems, which subject them to leaver penalties that result in bans and a loss of MMR.
Some players call this issue the “applying update” bug because when they try to load into a match, they are caught in a loading screen that reads “applying the update.” They would eventually stop loading into the video game, which the system would record as dodging and punish them for.
Due to an update error, players from Overwatch 2 have been banned
The problem was first reported on December 13, 2022, in a Reddit post on the Overwatch forum. Several other people in the comments confirmed it also happened to them, despite the fact that it did not receive much attention. Since then, the bug has been mentioned sporadically on Reddit and Blizzard forums, but it still needs to be rectified. Although there are tutorials available for fixing it, an increasing number of players are now reporting the issue.
It was mentioned by a gamer in the bug reports section of a Blizzard forum post. “Twice in two days, when I try to play comp, my game gets stuck on ‘Applying Update,’ resulting in a suspension and (I assume) an unfair leaver penalty,” they stated. Numerous other players have confirmed that it has also happened to them. On the Overwatch subreddit, another player also complained about their issue and claimed that Blizzard would not remove any leaver penalties from it.
They allege in this post that the Blizzard-recommended solutions for the “applying update” bug were only a temporary remedy and that it has happened to them numerous times since implementing the fixes. Although this bug has been mentioned in numerous bug report forums, no fixes have been made as of yet.
Comments are closed.