/cdn.vox-cdn.com/uploads/chorus_asset/file/24703425/2.png "Amnesia Review: The Bunker - The most stressful Amnesia game to date")
Overwatch 2 player and content creator Marblr ran into a peculiar bug in Overwatch 2 payload maps that causes the payload to ignore and skip checkpoints. The strange glitch was discovered after it accidentally occurred during one of Marblr’s games, causing me to investigate further.
After spending some time trying to get this bug to occur again, it was discovered that if a player is moving the payload and gets off just before it hits the checkpoint (in Marblr’s case, 0.1m away), checkpoint), instead of rolling backwards, the payload will continue to move past the checkpoint. This means that the payload will continue en route to the next point without marking the point it just passed as reached, skipping it entirely. You can watch Marblr’s discovery of the bug in their YouTube video below:
At first, this may seem like a worrisome bug. This is because when removed, it could save the attacking team some crucial seconds during the phase where the payload is currently halted after reaching a checkpoint by immediately continuing to move.
However, there is no need to worry too much. First of all, this error is difficult to achieve, which means that it is very unlikely that you will see it appear often. Most of the comments on the Marblr video are from other players who have shared this experience in a single game during their time playing Overwatch 2, always wondering how it happened.
And of course there isn’t much benefit in triggering this error. As demonstrated later in the Marblr video, because the previous checkpoint was never marked as reached, the final checkpoint will not unlock, meaning it’s virtually impossible to win the game once this bug occurs. . The only way to reverse the error is to let the payload go back to where it passed and stop to allow it to be recaptured. Of course, this won’t work on all maps, as some have doors that close once the payload has passed through them.
Regardless, it’s a very interesting bug to see, and it’s left many players wondering how long it’s been hidden in the game without anyone noticing. Have you had any problems with this particular error? Feel free to let us know in the comments section below, and don’t forget to check out the rest of our content here on dlprivateserver for more news, guides, and lists to keep you up to date on all things Overwatch 2.
