All progress being reset when match ends
All progress being reset when match ends. Can't rank up any class or general level. After match i can see that for ex lvl of trooper reaches 15 but when i go back to menu it is still 14 How it can ...
Forum Discussion
Oh good I was wondering if I was the only one. I have reached lvl 31, Support lvl 3, and complete a challenge like 4 times today.
EA_AticDICE Team
@Info_Drone-0451 @Toptishka94 @DR_QQ008 is it reset or stop progressing and is it everything or just one part? Please deatildown whats missing or been rest.
/Atic
Achievements, gun/vehicle kills, medals and codex entries, XP and player level.
In-game you can see the counters go up if you check the selected assignment, it resets when you exit the server though.
Achievements, gun/vehicle kills, medals and codex entries, XP and player level.
In-game you can see the counters go up if you check the selected assignment, it resets when you exit the server though.
Not getting any operations points today
Just played two matches and nothing
Yesterday was fine
Weapon assignments, community assignments, assignments in general. Level XP as well. It was fixed yesterday for a bit. Then again today it returned, only today it the "end of round" screen is also broken, it doesn't load or show anything, progress doesn't track as well.
I just thought it was a problem with battlefieldtracker.com ‘cause when I checked my stats after playing tonight I could see my playing time had not changed.
It showed the exact same days/hours/minutes as before I played tonight which of course is not correct.
However when I go into Game Reports I can see the match is actually there; I can click my name and see the usual info for the round - my K/D, hit % of weapons etc.
So the match itself is apparently registered correctly at DICE’s file system, however each player is not updated. (At least my profile wasn’t - I’m assuming it’s the same for everyone else too)
Hope this makes sense, otherwise feel free to ask.
Edit:
The last time my stats were updated was 12 hours ago according to battlefieldtracker,com.
So the bug’s started in the past 12 hours it seems.
