A nasty exploit in Overwatch 2 currently causing frustration. Bastion players can use their Ultimate almost infinitely.
Overwatch 2 has been available for a few days and even though the servers caused quite a few problems due to an ongoing DDoS attack, the start went relatively smoothly. The gameplay is good as usual and only the battle pass and the monetization cause big discussions.
But there is also a bug that is causing quite a stir in all game modes. Because the character Bastion has an ultimate that is much stronger than it should be. This is due to a bug or an exploit – depending on how you take it.
What is this error? The bug affects the ultimate ability of DPS character Bastion. When executing the ultimate, he goes into his siege mode and switches to a “top view”. There he can freely place three artillery strikes on the map – wherever he wants. At least if everything works correctly.
Currently there is a bug that Bastion doesn’t only fire three shots, but as many as fit into the time limit of his ultimate abilities – i.e. 10, 11 or even 12 artillery hits, which make short work of any character. With so many impacts, it’s almost impossible to dodge, so using the ability with this bug almost automatically results in a devastating team kill.
Community reacts angrily: The fact that such a massive bug can be found in the live version of Overwatch 2 naturally bothers many players in the community. In ranked matches in particular, such a long ultimate can mean that a game is “given away”. However, the exploit also makes for some amusing faces, such as the streamer Somjuu, whose face completely derails when he realizes that Bastion’s attack is hitting several times more than planned:
Recommended Editorial Content
At this point you will find external content from Twitch that complements the article.
I consent to external content being displayed to me. Personal data can be transmitted to third-party platforms. More regarding this in our Data protection.
How does the bug work? Of course, we won’t reveal that at this point and we also advise everyone once morest reproducing the bug. Since it is very difficult to “accidentally” cause this error, Blizzard may well issue temporary penalties for this offense when reported by other players. One should therefore avoid exploiting the error.
Have you noticed other bugs in Overwatch 2? Bugs or issues you’re struggling with right now?