You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 9, 2024. It is now read-only.
When a tracked player stops to get tracked (went off any clans, stopped playing) and come back the WG API does not allows me to infer when he played the battles on the interim, and so a large number of recent battles are reported.
This fixes itself in 28 days, but can introduce distortions if the player played a lot off the system.
Possible solutions
Purge players that went off for more than a month;
Continuously pull data from these players, on a monthly schedule, forever;*
Some mix of slow pulling data and purging;
If the number of battles is too large (more than 1,000?) put an achor just before the data collection so he starts again with zero recent battles; this may be the fair solution.
The text was updated successfully, but these errors were encountered:
When a tracked player stops to get tracked (went off any clans, stopped playing) and come back the WG API does not allows me to infer when he played the battles on the interim, and so a large number of recent battles are reported.
This fixes itself in 28 days, but can introduce distortions if the player played a lot off the system.
Possible solutions
The text was updated successfully, but these errors were encountered: