Forum Discussion

Nicholaskya's avatar
4 years ago

All stat-trackers are capped at 21,474,836 .

Product: Apex Legends
Platform:PC
Please specify your platform model. PC
AMD or Nvidia Model Number AMD Raden R9 200 Series
Enter RAM memory size in GB 32 GB installed --- 19.3 GB available
What is your gamertag/PSN ID/EA Account name? Nicholaskya
Please provide your squad mates' gamertag/PSN ID/EA Account name if possible. N/A
Are you using any software with an overlay? No
Which Legend were you playing (if applicable)? Octane
Which Legends were your squad mates using (if applicable)? N/A
Where did the issue occur? In the lobby (waiting area before the match)
Which part of the map or menu were you in? If you don't remember the exact name, please describe the area or what you were trying to do in the menu. N/A
What were you doing when the issue occurred? E.g. respawning a squad mate at a beacon, using an ability, a squad mate left the game. Viewing my stim distance tracker in-match, in-lobby
Did your squad mates also experience the issue? Yes
How many matches had you played in a row before the issue occurred? More than 3000 matches
When did this happen? (dd.mm.yy hh:mm) N/A.03.21 NA:NA
How often does the bug occur? Every time (100%)
How severe is your issue? Little to no impact to gameplay
What happens when the bug occurs? ANY STAT TRACKER is capped to 21,474,836
What should be happening instead? ANY STAT TRACKER should not be capped to 21,474,836
Steps: How can we find the bug ourselves? Step 1.) Set your stat tracker to 21,474,835 Step 2.) Increase it by performing actions IN MATCHES so that it would be greater than 21,474,836 Step 3.) You view your own player card IN LOBBY, it exceeds 21,474,836. Step 3.2) Notice that OTHER players in your lobby do not see an integer greater than 21,474,836; it is capped.

My explanation in the above report isn't very good, so this is my best explanation of the bug, why it happens, when it happens, and HOW TO FIX IT  !

DISCLAIMER: I'm not a programmer so some of this may be incorrect, but I think it is still good information to give because it may assist you in detecting and resolving the problem

------- WHY I THINK THE BUG HAPPENS:

The 32-bit integer limit

2,147,483,648

The limit of any tracker

21,474,836

Do you see the similarities in the numbers?

The limit of a tracker is almost exactly 1/100 of the 32-bit integer limit.

It is not a coincidence that players cannot progress beyond 21,474,836 on a stat tracker.

Many players experience this, in fact you can verify this fact at this link: https://apex.tracker.gg/apex/leaderboards/stats/all/Damage?page=1&legend=wraith

From the link, you can see that 20 players of legend Wraith are tied at 21,474,836 damage.

It is VERY important to note that these players do not have the same stats, but that their stats are displayed as the same.

The problem lies in the fact that their tracker when seen by other players, shows the set limit of 21,474,836 , but when viewed by the player themselves, they see the REAL VALUE which is greater than 21,474,836.

Maybe there is some mistyped article of code that applies to all trackers, saying that if a tracker exceeds 2147836 , it equals 21474836 . I have no idea..

1.) The "visible value" I am about to mention is the value seen in the match, and the value seen by other players.

2.) This does not affect the REAL VALUE, but only the visible value.

So basically, one's own client can view their tracker at above the limit.

In match, a new player card is generated with the adjusted value.

In lobby, other players see the player card generated with the adjusted value.

The adjusted value and the real value both exist at the same time; if you switch your tracker to a different slot, you see the real value --- but then the adjusted value overrides it.

I know this won't be high priority to fix considering it's not altering gameplay, but please fix it ASAP!

*DxDiag attached

*Adjusted value that other players see attached

*Real value that one's own client sees attached

No RepliesBe the first to reply

About Apex Legends Bug Reports - Archive

23,008 PostsLatest Activity: 5 years ago