A member of the community brought to my attention an issue seen in the player statistics data, specifically the leaderboard position. The Microsoft Playfab API, which is polled to grab all player statistics data, is returning inaccurate leaderboard positions for all statistics that are not in the top 1000 players for their respective category.
This error comes directly from the Microsoft Playfab API, and is not caused by any internal backend or business logic that is run on my side.
The fix for this issue now runs a daily job that will crawl each statistic leaderboard and grab the top 50,000 players. Any statistics that are crawled by this job are marked with a verified icon. For statistics outside the top 50,000, the Microsoft PlayFab API is used to estimate your position on the leaderboard. While it's not completely accurate, it usually places you within 100,000 spots of your actual position.
Tracking has been rolled out across all statistics (player, weapon and class), capturing the top 500 players for each leaderboard. All leaderboards are checked daily.
Several UI improvements have been made to enhance the mobile experience, though itโs still a work in progress. A future update would look to rewrite the entire frontend using Next.js & shadcn.
๐ง Several other bug fixes, backend and microservice rewrites to improve site performance.
If you have any recommendations, features you'd like to see on the site, or if you encounter any bugs, feel free to reach out! Let me know via the Contact page.
Live data is now fully integrated into chivalry2stats.com!
Player statistics are fetched in real-time from the Microsoft PlayFab API. Please note that you may experience slightly longer wait times as data is not retrieved from this site's database. Player display names and alias histories are updated daily, reflecting changes only after they have completed a match.
Stay tuned for more updates!