I got a few questions regarding the PGI Leaderboard (that one you go to by logging in to mwomercs.com/profile/leaderboard).
There are the results of 16 Seasons. How long is one Season? And when does a new one start and an old one finish?
Does it include FP-Matches too or just quickplay (group and solo)?
I have a few friends here in the game, who strongly doubt the shown data in the leaderboard (f.E. the number of played matches). I just want to know about, if they are doubting for a reason or not.
Thank you!
PS: I am german, so pls excuse grammer/mistakes.
1
Pgi Leaderboard
Started by Archie4Strings, Oct 26 2017 11:19 PM
5 replies to this topic
#1
Posted 26 October 2017 - 11:19 PM
#2
Posted 27 October 2017 - 01:18 AM
Each season corresponds to one month. For instance, Season 16 will conclude and Season 17 will begin on 1. November.
The leaderboard is titled "Quick Play Leaderboard", and as such Faction Play matches are not included. This is just for solo and group queue.
Here is a post I made recently using numbers from this leaderboard: https://www.reddit.c...ough_sept_2017/
And here is a spreadsheet that I am working on currently (literally right now) that I will be posting soon to the public: https://docs.google....t#gid=792219336
The leaderboard is titled "Quick Play Leaderboard", and as such Faction Play matches are not included. This is just for solo and group queue.
Here is a post I made recently using numbers from this leaderboard: https://www.reddit.c...ough_sept_2017/
And here is a spreadsheet that I am working on currently (literally right now) that I will be posting soon to the public: https://docs.google....t#gid=792219336
#3
Posted 27 October 2017 - 01:58 AM
Alright, thank you!
#4
Posted 27 October 2017 - 08:10 AM
Tarogato, on 27 October 2017 - 01:18 AM, said:
Each season corresponds to one month. For instance, Season 16 will conclude and Season 17 will begin on 1. November.
The leaderboard is titled "Quick Play Leaderboard", and as such Faction Play matches are not included. This is just for solo and group queue.
Here is a post I made recently using numbers from this leaderboard: https://www.reddit.c...ough_sept_2017/
And here is a spreadsheet that I am working on currently (literally right now) that I will be posting soon to the public: https://docs.google....t#gid=792219336
The leaderboard is titled "Quick Play Leaderboard", and as such Faction Play matches are not included. This is just for solo and group queue.
Here is a post I made recently using numbers from this leaderboard: https://www.reddit.c...ough_sept_2017/
And here is a spreadsheet that I am working on currently (literally right now) that I will be posting soon to the public: https://docs.google....t#gid=792219336
Wow, interesting !
#5
Posted 13 April 2018 - 12:39 AM
So, how do you access this leaderboard data via an API? Is there actually an API for receiving player data (kills, deaths, K/D ratio, etc)? Where is the documentation or an example on that?
Edited by Gartenlaube, 13 April 2018 - 04:01 AM.
#6
Posted 16 April 2018 - 10:43 AM
Gartenlaube, on 13 April 2018 - 12:39 AM, said:
So, how do you access this leaderboard data via an API? Is there actually an API for receiving player data (kills, deaths, K/D ratio, etc)? Where is the documentation or an example on that?
It's kind of tricky at the moment. The Jarl's List is a good example of a system that scrapes the leaderboards, https://leaderboard....org/search.php. I don't know if the source code is published, but theoretically, every month it may use a framework such as selenium to login to mwomercs.com and pull down the records of the prior season. After this process completes (maybe it takes a couple hours so as to not trigger a DOS flag and get locked out for some arbitrary time period) the people running the Jarl bot will have built up their own personal database of playernames and metrics.
You could do the same. Ideally maybe the Jarl's dev already has exposed prior season's match data over an API and I just don't know about it? If you do build a scraper, please be courteous about exposing an API endpoint so tons of additional people don't need to repeat the work and further tax mwomers.com's bandwidth with superfluous spiders crawling every which way.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users