Bug: DBD_BloodwebPoints Steam stat wraps around to 0 at values above 4,294,967,296 (2^32)
Bug #333
DBD_BloodwebPoints Steam stat wraps around to 0 at values above 4,294,967,296 (2^32)
| Status: | New |
| Priority: |
Medium |
| Added by: |
|
| Assigned to: |
Unassigned
|
| Due date: | |
| Reported for: | |
| Actual Result: |
Steam total BP earned stat incorrectly reports mod(accurate value, 2^32)
|
| Expected Result: |
Steam total BP earned stat (DBD_BloodwebPoints) reports accurate values.
|
| Severity: |
Minor
|
| Reproducibility: |
Always
|
| Platform: |
Steam
|
| Additional Notes & Comments: |
Not set
|
Steps to Reproduce
- Earn 4,294,967,297 BP (or more)
- Query the Steam API for the DBD_BloodwebPoints stat.
- Observe that DBD_BloodwebPoints incorrectly reports 1 total BP earned (instead of 4,294,967,297).
Explanation
DBD_BloodwebPoints Steam stat wraps around to 0 at values above 4,294,967,296 (2^32).
Root cause appears to be that this value is being reported from DBD to Steam as a 32-bit int stat. Per https://partner.steamgames.com/doc/api/steam_api#ESteamUserStatType, there is no higher precision integer stat available on this platform.
Since new Steam stats are routinely introduced with new chapters, and some stats are reported as 32-bit floats (e.g. DBD_GeneratorPct_float), one possible solution would be to introduce a new stat, DBD_BloodwebPoints_float, that reports total bloodpoints earned as a 32-bit float.
While a 32-bit float would incur gradually increasing precision loss at values above 16M, the error would only be +/- 2048 BP at 20B--equivalent to 1 common item from the bloodweb.
Rather than a potentially disruptive data type change from int32 to float32, I'd recommend introducing a second stat alongside the int stat. Benefits:
- Zero risk of breaking existing consumers of int32 DBD_BloodwebPoints
- Consumers could reconstruct the exact value if desired using the combination of DBD_BloodwebPoints and DBD_BloodwebPoints_float with modulo arithmetic.
The proposed solution should be a low-scope change since new stats are routinely introduced and there is precedent for introducing float values.
There are no other values in the reported Steam stats that allow correctly inferring total bloodpoints earned.
stats.deadbydaylight.com/statistics reports correct values, but these metrics are unavailable publicly as the Steam stats are. There are no known APIs for retrieving them.
This makes the official stats unsuitable for:
- Sharing and verify by other users
- Stats leaderboards (nightlight.gg, dbd.tricky.lol, dbdstats.com, deadbystats.eu, etc.)
I'm sure you could develop an official leaderboard that serves these popular use cases, that would be a much higher scope change, whereas this should be a very low scope fix.
I have only recently crossed this limit, I have friends who are estimated to be in the 18 billion BP range who are also disappointed that their stats aren't reported accurately.
Admittedly, this is not the highest impact bug, but it does affect your most dedicated players. Seeing this fixed would be very appreciated and worthy of a Labor of Love nomination.
Watchers
