# Invasion event: Internal Battle Counter is off

**URL:** <https://community.gemsofwar.com/t/invasion-event-internal-battle-counter-is-off/73252>\
**Category:** Bug Reports\
**Created:** [December 11, 2021, 10:57am UTC](https://community.gemsofwar.com/t/invasion-event-internal-battle-counter-is-off/73252 "2021-12-11T10:57:38Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![gary\_dils](https://sea1.discourse-cdn.com/flex019/user_avatar/community.gemsofwar.com/gary_dils/32/64086_2.png) [@gary\_dils](https://community.gemsofwar.com/u/gary_dils)\
**Post date:** [December 11, 2021, 10:57am UTC](https://community.gemsofwar.com/t/invasion-event-internal-battle-counter-is-off/73252/1 "2021-12-11T10:57:38Z")

</div>

**Platform, device version and operating system:**  
PC / Mobile

**Screenshot or image:**  
 ![json](https://us1.discourse-cdn.com/flex019/uploads/gemsofwar/original/3X/1/5/152d4505a4b6dda327a880b9e759849bb927ef79.png)

**What you were expecting to happen, and what actually happened:**  
when fetching the `live_event_get_info` for Invasion event (current event id is `5179`) the leaderboard entries (`GuildLeaderboard`, `GlobalLeaderboard`, and `PlayerLeaderboardEntry`) report the `BattlesWon` with the same number as `EnemyLevel`, but those should be different. In the above example the number of battles should’ve been _41_ (3x Stage 1 - 7 + 20x Stage 8).

**How often does this happen? When did it begin happening?**  
Happens every time, probably around since the Invasion events started.

**Steps to make it happen again**  
during Invasion weekend: log into the game, go to Guild → Invasion and observe the data fetched from the API

Cheers, Gary.

---

<div class="post-metadata">

**Author:** ![ats1080](https://avatars.discourse-cdn.com/v4/letter/a/74df32/32.png) [@ats1080](https://community.gemsofwar.com/u/ats1080)\
**Post date:** [December 11, 2021, 12:28pm UTC](https://community.gemsofwar.com/t/invasion-event-internal-battle-counter-is-off/73252/2 "2021-12-11T12:28:51Z")

</div>

This must be due to mongo optimizations too🤣
