Another day, another problem in Battlefield 3 to tell you about. Unlike the minor IRNV Scope, Tactical Light and MAV issues that players were complaining about after release, this one is a little more serious and affects the use of the FAMAS weapon.
It has become apparent that many players are complaining of stat losses after game and XP not accumulating properly. Considering that this wasn’t happening after the recent most recent patch update, we can only assume that this new bug may have crept into the game after the recent double XP playlists update.
The problem has become so serious that DICE has had to investigate the matter and they’ve said that the bug could be down to the use of the FAMAS rifle in game. According to the developer, any player who uses the FAMAS in game could result in the WHOLE server not gaining XP or stats after the game and as a result – they have recommended that everyone stop using the weapon until the problem is fixed.
As you can imagine, this is a huge problem in game and one that just can’t be fixed instantly without proper testing. It’s no easy task either to just ask players to not use the weapon, because as you know we now play in an FPS community which is full of trolls who will see this as a perfect opportunity to infuriate one or two gamers just for the fun of it.
Since the patch update, you could argue that the FAMAS wasn’t really used extensively anyway. Pre-patch it was the most used weapon on the likes of Operation Metro, but after the last patch DICE nerfed the weapon so much that nobody wants to go near it any more.
What a mess DICE now finds themselves in though with players having no control over whether their stats and XP will be lost at the end of a game or not. Unassuming players are bound to still use the FAMAS who haven’t been keeping up with forum news, so DICE needs to sort this out ASAP.
Have you experienced a stats or XP loss in game? A lot of people are saying that they haven’t used the FAMAS at all, but don’t forget it could be someone else on the server that is using the weapon for the problem to still happen. We’ll let you know once we hear more details from DICE on this embarrassing bug.