My response to DarkForcesJedi::
I'm a trade/commerce analyst that works mainly with SQLs and Excel.
In your original post you were taking averages (in this case ratios) and using them like whole numbers. It doesn't work out like that.
What your doing is like this small example (using %s here, as they are another form of average).
In Ireland, 90% of gamers play Destiny
In the UK, 90% of gamers play Destiny
In China, 5% of gamers play Destiny
According to your method the total of players of these 3 countries that play Destiny would equal 61.6% which anyone can see is wrong.
English
-
No, what I am saying is that a country in which 61% of players play Destiny is about average for a country, when countries are ranked by Destiny adoption rate. My point being that each average has a specific meaning in a specific context. Defining a metric of player performance and comparing individuals' metrics to the average of all players' metrics is valid *in that context.* The fact that the metric is an average of something else is irrelevant. The total number of kills divided by the total number of deaths is an average, but it is not a determination of an average player. It is a determination of an average death weighted by kills. "The average *death* is associated with one kill." When you take a per-player metric, regardless of what that metric is, and average it over all players you get a metric for an average player. It might be average number of hours played *per player*, average number of crucible matches *per player*, average number of emotes used per raid *per player*, average DTR score *per player*, or average K/D per player. Any of those represents an average *player* when considering a specific metric. If the average player uses 3 emotes per raid and I use 300 emotes in a KF run, my emote usage was above average. The fact that "emotes used per raid" is itself an average is irrelevant to that fact. (Whether any metric is or is not a measure of player skill is a separate issue.)