Milestones not progressing.
Product: Star Wars Battlefront II Platform:Microsoft XBOX One What is your issue related to? General Summarize your bug I have 4 milestones that the game won't let me progress on: Hold the enemy b...
Forum Discussion
Product: Star Wars Battlefront II
Platform:PC
What is your issue related to? General
Summarize your bug Assault kills not properly counted?
What is your gamertag/PSN ID/EA Account name? Starculpepper
How often does the bug occur? Every time (100%)
Can you tell us the date (MM/DD/YYYY) that you saw the bug?
What time did you see the bug? (HH:MM AM/PM)
In what game mode did the bug occur? Blast
What is your time zone? GMT (UTC)
Steps: How can we find the bug ourselves? Playing any non-campaign mode mode (as far as I can tell) I get a summary screen of my kills, assists etc, but that doesn't match recorded progress against the class milestones? For example, trying to unlock the first weapon for assault requires 50 kills. I can achieve 10 in a battle in Blast, but the milestone count only records 2 kills?
What happens when the bug occurs? As above - incorrect record and slow or stalled progress on milestones.
What do you expect to see?
Please select your region Europe
AMD or Nvidia Model Number
Playing any non-campaign mode mode (as far as I can tell) I get a summary screen of my kills, assists etc, but that doesn't match recorded progress against the class milestones? For example, trying to unlock the first weapon for assault requires 50 kills. I can achieve 10 in a battle in Blast, but the milestone count only records 2 kills?
Eliminations (what the scoreboard shows) are your kills & assists combined. Assists do not count as kills for progression.
I am seeing the same issue on all classes. Playing as a Heavy class in Strike and actual kills (Not counting assists) 11 but only 3 counted towards the progress. Talked to EA on chat and they said that it is part of another issue but no confirmation on when it will be fixed.
- Great, thanks all
- I have the same problem, one month old bug and still no fix.
