Weapon Progression Unlocks (NOT XP-Unlocks) Not working (Kills not counting)
Product: Battlefield 2042
Platform:PC
Please specify your platform model. PC
AMD or Nvidia Model Number RTX2080TI
Enter RAM memory size in GB 64GB
Are you using any software with an overlay? No
Which part of the game is the issue happening in? Multiplayer
Which part of the mode? ConquestSmall
Please select your region North America
On which server did this happen? Solo/Co-Op
When did this happen? (dd.mm.yy hh:mm) 12.11.21 19:00 CST
Summarize your bug Weapon unlocks based on achieving a number of kills with a weapon are not working in Solo/Co-op All Out Warfare
How often does the bug occur? Every time (100%)
Steps: How can we find the bug ourselves? 1) Play Solo/Co-Op All Out Warfare 2) Go to your loadout screen and edit the attachments for your weapon, find something that requires 30+ kills to unlock and take note of how many kills it currently has 3) Kill any number of enemies 4) Go back to the loadout screen, and the number of kills has not changed at all
What happens when the bug occurs? Kills are not accumulating to allow progression towards weapon / vehicle mastery, and therefore not allowing attachment / equipment unlocks
What should be happening instead? Kills should be accumulating allowing mastery and unlocks
This issue is not about XP-based unlocks, it is purely about cumulative KILL COUNT based unlocks.
This was posted about last friday, but the 600+ comment thread was deleted without any comment from EA other than a copy/paste of a tweet about XP being disabled on Custom Portal Experiences. Based on the *only* response that an EA CM has provided, both here and on twitter, I am lead to believe that it's possible the temporary fix for the Portal XP Farming of turning off XP in Custom Portal Experiences and reducing XP gains of Solo/Co-Op All Out Warfare is somehow also affecting the kill tracking for mastery unlocks on weapons / vehicles. If it is related, however, it's very much a "known issue" to the EA team at this point, and it's not even being tracked anywhere official, so the community is unaware of it.
@EA_Atic: if you could please shed some light on this and just let us know if it's being looked into, that would really help a significant portion of the customer base. The thread got excessively toxic, but a cursory review of the evolution of the comments would have shown that that was due to spending a week with hundreds of "I have the same issue" and +XP votes that ultimately lead to no responses from the team at EA.
Something has been changed on the server side and this issue is now resolved.
Want to thank the back end devs for their work on this, and ... while the patience of the CM team for not completely losing their mind due to the toxicity of some of the posts about this is to be lauded, the complete lack of communication on this issue for over a week is shameful. I recognize it's a hard job, but your job is managing the community, and you dropped the ball. Please do better, the game's success depends on it.
