Over the last week, I’ve received numerous beet error codes only during gambit matches. I’ve had zero issues playing strikes, crucible, raids or anything else. I refuse to believe that my connection is the problem when this only occurs with gambit. Now I’ve finally received a temporary ban due to a game issue. I’m at Legend rank right now trying to reset for the dredgen title but as of this last week it has been virtually impossible with this bug. Again, this only started happening over the last week.
Have you looked up the error on help.bungie.net and taken the steps it outlines to fix the issue?
If you are suspended, this lasts only 30-60 minutes. You’ll be met with a ‘time out’ message on PVP and gambit in this case.
However, if you are restricted, it’s not as a direct result of the beet error and in fact comes as a result of connection logs showing your account to have a consistently unstable or weak connection to the game.
[quote]Over the last week, I’ve received numerous beet error codes only during gambit matches. I’ve had zero issues playing strikes, crucible, raids or anything else. I refuse to believe that my connection is the problem when this only occurs with gambit. Now I’ve finally received a temporary ban due to a game issue. I’m at Legend rank right now trying to reset for the dredgen title but as of this last week it has been virtually impossible with this bug. Again, this only started happening over the last week.[/quote]
I've been having the same issue it is bungie I've played so much crucible not a single problem every other game runs flawlessly with steady connection it's only GAMBIT and these *unts cant figure it out so they ban players