THIS HAS TO STOP! BG ERROR SCREEN

I was about to hit vibranium V, finished the fight with 100% HP and got the message of death .
why is this a thing? its been going on for months and it hasn't been fixed. Is it a hacker?

Comments

lucianxvs

lucianxvs

its so infuriating, I played perfectly and i lose because of a stupid bug…exactly after i finish the fight, and now i have to restart it and finish it in 10 seconds and the defender is at full HP, what the hell…ahhhhhhhhhh

lucianxvs

it also counts as a forfeit, which is not fair, i finished the fight with 100% hp…i did not forfeit…

Jerichoharris

It happens to us all, it’s been a thing for ages and we’ve had precious little out of Kabam to even acknowledge it as a problem.

SirGamesBond

Na na na, Definfitly hacker. All info in device is now cooked. Rip man

lucianxvs

just got the same error screen again…. twice in the same day.. nice

DSRGOD123

Ye this is a common thing,one of the many reasons I stopped playing battle grounds.

lucianxvs

stupid server stop crashing on me when Im about to win… why is this happening..

DNA3000

It is some kind of synchronization error, and it is probably not the same error consistently. In other words, it isn't some long standing bug that has never been fixed, rather it is a symptom of any bug that causes either a sync error or an instance crash.

To emphasize, this error in a sense predates Battlegrounds. The game has always had the possibility of a fight working on the client but failing on the server, and the net result is the game errors out and behaves as if the player never fought the fight. This was a thing in AQ nine years ago. It isn't a bug, it is a symptom of a range of bugs. Kabam does fix these bugs, but others show up with the same symptom.

The best way to mitigate this is to periodically force close the game client and reopen it, particularly before doing very important fights. BG fights, war bosses, end game content, whatever. This is typically a problem that crops up after the game has been running for a while, and resetting the game eliminates (temporarily) whatever is ultimately causing the problem. However, there is no way to 100% avoid it. Resetting seems to avoid 99% of them, but not all of them.

Osborne

To kabam: why you guys don't release a bug free bundle offer for $100/month 🤡