July 2019
Product: Battlefield V
Platform:PC
Please specify your platform model. PC
AMD or Nvidia Model Number NVIDIA GeForce GTX 1080
Enter RAM memory size in GB 16
Which part of the game is the issue happening in? Multiplayer
Which part of the mode? Conquest
Please select your region Europe
On which server did this happen? any
When did this happen? (dd.mm.yy hh:mm) 25.05.2019 20:00
Summarize your bug 1) MAB 38 Mastery V has WRONG information to complete : ** 7 kill over 30m in one round - i think it must be written as IN ONE LIFE.... ** 25 kills over 30m - i think it myst be written as IN ONE ROUND..... 2) MAB 38 is a SMG , it is impossible to kill 7 in one lofe over 30m ! , and in one round 25 kills are also insane... Screenshot attached
How often does the bug occur? Every time (100%)
Steps: How can we find the bug ourselves? 1) you can write correct information as i discoverd (in one life, in one round) but it is impossible to achieve, so you can make it work as it is written right now on the description, so if you simply fix the achievment script it would be fine.
What happens when the bug occurs? you simply can not unlock this achievment because : 1) you must do impossible 2) it is written not as it is working
What should be happening instead? you can unlock the achievement normally, do what is in written on description
MAB 38 Mastery V has WRONG information to complete :
** 7 kill over 30m in one round - i think it must be written as IN ONE LIFE....
** 25 kills over 30m - i think it myst be written as IN ONE ROUND.....
2) MAB 38 is a SMG , it is impossible to kill 7 in one lofe over 30m ! , and in one round 25 kills are also insane...
Screenshot attached
Solved! Go to Solution.
July 2019
A fix for this mastery is meant to be in the next patch.
July 2019
This has already been reported over a month ago:
Special Assignment Bug for MAB 38
The forum has a big search bar at the top you can use, to see if bugs or other things you want to talk about are already mentioned in this forum.
July 2019
August 2019
As for 19.08.2019 this bug is still not fix