Incorrect Banners awarded for Territory Wars

[mikejedi13]

Product: Star Wars: Galaxy of Heroes
Platform:Android Phone
What type of device are you experiencing the issue with? Samsung Galaxy S8
OS Version 7.0
Ally Code: (Find it here: http://bit.ly/AllyCode ) 834-131-749
What type of issue do you have? Other
How often does the bug occur? Every time (100%)
Summarize your bug In the latest Territory War, our total banners were not calculated correctly. By my manual calculations, we scored 13,610 banners, but the game shows a total of 12,900. I've attached screenshots to verify the claim. I thought that maybe the correct total would show after results were finalized, but the incorrect score remains.
Steps: How can we find the bug ourselves? Check our guild's TW score as of 2/20/2018. We scored 13,610 but only show a total of 12,900.
Connection Type Mobile
Please select your region North America
Country United States

‌

It seems like the final battle of a territory was not counted in the banners.  So, 10 for the victory, and 700 for conquering the territory.  That was the difference in our score.

[mikejedi13 · Accepted solution]

Looks like this issue was resolved in the latest updates. Thanks!

[EA_HighCommand]

Hi @mikejedi13 and thank you for your report. I checked the result of the TW (the one that ended 2/20/2018, 7:00 PM GMT) and the score of 12,900 appears to be correct.

[mikejedi13]

Here's the math:

20 x 250 = 5000 (250 defensive squads, 20 banners each)

250 x 8 = 2000 (8 zones cleared, 25 squads in each)

700 x 6 = 4200 (conquer bonus for 6 zones)

1150 x 2 = 2300 (conquer bonus for 2 zones)

11 x 10 = 110 (11 squads cleared in another zone, 10 banners each)

Total banners = 13,610

The display, and your records, show 12,900.  Therefore, there is still a problem.

[mikejedi13]

And just look at the scores compared to the territories taken. We beat them by 1 *full* territory (plus a number of squads), which is worth 700 banners, but only won by 220 banners!?

[mikejedi13 · Accepted solution]

Looks like this issue was resolved in the latest updates. Thanks!