A new Destiny 2 glitch is currently ruining the game by causing the error code “Rutabaga.” The Destiny 2 community played it cool. But over the weekend, that changed when the “Rutabaga” ruined the game far too often.
What happened? Over the weekend, Bungie acted to prevent players from exploiting an extreme glitch in Destiny 2 that leads to the error code “Rutabaga.”
The problem with the Min/Max glitch had been known to the developers for 4 months, and they had already been working on a solution. However, Bungie did not see an urgent need for action until this weekend.
The hide-and-seek ends – Now the ban hammer drops
Bungie was confident and suspected that the error code had not yet circulated among players. However, certain circles within the Destiny 2 community were already aware of how this glitch worked. They remained silent to avoid drawing unnecessary attention to Bungie.
But over the weekend, that changed when YouTuber JB3 broke his silence. He was also the one who first reported the glitch to Bungie. However, when nothing happened, he decided to go public.
His video demonstrates what the glitch can do and why it has this name.
- The glitch works with various Supers and characters.
- With correct activation, players can generate 10 or more orbs of power instead of 3.
- This gives players infinite Super.
- Additionally, the glitch could also extend any timer in the game as a built-in “net limiter.”
- This glitch can only be applied on PC.
How did the Min/Max glitch work? In the video, JB3 now provides the exact instructions for executing the glitch. First, you need to completely fill the Super bar for it to work at all.
To execute the glitch afterward, you only needed to activate windowed mode and then briefly open the menu via Alt-Tab. Then, click on window minimize/maximize with the mouse for 5 seconds, and you will get the desired effect upon activating your Super.
Why is this a problem? Anyone who exploited the glitch had a significant advantage in any activity. The Ultimate could be charged much faster this way.
While this might be okay in PvE, it can lead to major problems in PvP. It could give teams a huge advantage. Since the glitch became public this weekend, Trials, the Destiny 2 endgame PvP, and Gambit were directly affected.
After JB3’s video was released, many players immediately tried to apply the Min/Max glitch themselves. Bungie responded promptly to prevent the exploitation of the glitch. Players who exploit the glitch from now on will receive an error code known as “Rutabaga.”
By the way, there have been many crazy glitches and bugs in Destiny 2 that have ruined the game in one way or another. In the following article, we have listed the 10 best:
That’s why you should not try this: The mere issuance of the error code was apparently not all that Bungie integrated to resolve the issue. After the developer’s announcement, reports in the forums and in the Destiny subreddit increased that players who received the Rutabaga error code were either banned or completely excluded from the game.
You should therefore definitely avoid using the glitch now if you do not want to lose access to Destiny 2. However, even if you “just” Alt-Tab out of the game, this can cause issues.
When will the error be finally fixed? It is still unknown how Bungie plans to ultimately deal with the glitch. Affected players can report in a forum thread if they are affected or would like to provide further information.
Did you already know about the glitch or have you just now found out? What was the best bug you ever experienced in Destiny 2? What do you think about certain circles within the Destiny 2 community deliberately withholding such glitches to avoid drawing Bungie’s attention?
