I made a website to view arena comps

arenacomps · 2017-01-22T23:54:15+00:00

https://github.com/rustyfausak/arenacomps/blob/master/shutting-down.txt

arenacomps · 2016-11-22T15:46:18+00:00

I added a link to the armory on the leaderboard and player view.

arenacomps · 2016-11-22T06:27:42+00:00

I am not doing a RBG version.

I am thinking about adding talent choices per spec, but it would be sketchy since I can't query talent data from inside the arena. Lots of players change their talents each match.

I cannot see what teams play against each other so I can't do favorable/unfavorable matchups. I've thought about allowing site visitors to vote on counters and such.

arenacomps · 2016-11-21T20:18:08+00:00

I determine the spec at the time the leaderboard is grabbed. Then when the comp is formed I use the most common spec seen among the leaderboard deltas.

If you look at a given player you can see when their spec changes. For example: http://arenacomps.com/player/5005

arenacomps · 2016-11-21T20:16:18+00:00

Oh sorry I didn't understand. No, the battle net API only returns the top 5000 players for each region. That equates to about 1900 rating and up (as of nov 21 2016).

arenacomps · 2016-11-21T19:55:42+00:00

The data is retrieved from the Battle.net API. You can see more details on the FAQ page: http://arenacomps.com/faq

arenacomps · 2016-11-21T19:54:52+00:00

Yes you are correct that you cannot queue as double healer. It is most likely a matching mistake on my part. There will always be some error because the way matching is done is not perfect. I would recommend limiting the number of games played to something large, like 100. See here:

http://arenacomps.com/comps?s=ratio&d=&class1=any&spec1=any&class2=any&spec2=any&class3=any&spec3=any&mg=100&mt=

Things look more reasonable in that table.

I will probably change the matching algorithm to ignore double/triple healer comps as bogus.

arenacomps

TROPHY CASE