Re: Weapon Progression Unlocks (NOT XP-Unlocks) Not working (Kills not counting)

@finiteworm66 Again, they could have handled it better by just clarifying that it was for progression too and that it was being exploited as well. At the same time the original message was very clear that it was a temporary solution and that it would return when fixed. I assumed like many others that this related to both xp and progression straight away, as they were both removed. I imagine the team thought it was quite clear in that regard too so of course they won’t respond with more because it just seems like a bunch of people didn’t see/read their original message.

If there was a completely civilised discussion with no attacks on the devs of anything toxic, then maybe they would have clarified it, but there’s so much hatred in these forums right now that I’m surprised they haven’t just closed off communication.

Since this isn’t a bug and this is not the discussion forum, this is my last message.

@rekoj1806 The real issue at hand is that intent matters very little compared to affect. The message that was delivered can be assumed to be related to XP *and* progression, but EA never communicated that. As such, it's our responsibility as the player-base to assume, until communicated otherwise by EA and not a general feeling we have, that this is indeed a bug.

@rekoj1806 To be perfectly clear: if this is not a bug, and it is a known issue related to the disabling of XP in certain game modes - that's TOTALLY fine. They said that that would come back once they worked it out. They need to communicate that to us, however, not just move threads related to the issue to the discussion forum. It's been an issue for a week, and is not in any way tracked on the Known Issues list. A new influx of players started playing yesterday, and they're already encountering this and conducting their own troubleshooting thinking something is wrong with their game. This is something that a simple acknowledgement can correct.

On the other end of the spectrum, if our assumptions that this is related to XP being disabled are incorrect, then this is a bug with a different root cause. In that case, again, it's perfectly okay if they don't know what that cause is yet, and are furiously investigating it, but that needs to be communicated.

Regardless of the status of this issue and its solution, it should be tracked on the Known Issues, as it is a massive issue that has been known about for over a week now.