This page is a list of the API's endpoints for /destiny (there's also a forum and user platform). As you can see, there are a number of endpoints for stats including ones that require an activityId. This is what I was looking for. Since you are able to get the aggregate stats for a player you can get a list of activities they have done. Hopefully, a method can be created to filter one player's list of activities against another player's to then start calculating information.

Right, destinytracker is using Bungie's API to get info. We know what it's capable of there, I'm wondering if there is more. I have the day off Monday for President's day. I think I will get an API key and see what I can do, no promises to anyone.

I was actually playing with the API a little bit earlier today. For those who don't know, but are interested in dabbling in the API, Bungie maintains an official API group. They've published the first official interface (https://www.bungie.net/en/Clan/Post/39966/85087279/0/0) and it's definitely worth a look.

Documentation is pretty sparse, but the endpoint descriptions are invaluable:
https://www.bungie.net/platform/user/help/
https://www.bungie.net/platform/destiny/help/

Now that they've solidified an API, I'm thinking we'll integrate some API-linked behavior into the forum.

*Edit: Just be careful with the Grimoire Card one… that thing just locked-up a couple of my code editors while trying to "prettify" the JSON so that I could read it. The response is 844KB of raw text. :D

I just included assists in the second part of the equation.

Also, I just saw an error I forgot to correct last night.. I needlessly tried to shift the first part of the win/loss stat to fall within a range that doesn't make sense for the rest of the equation. The Win/Loss category should read as follows:

=(1/2)[wins/totalgames] + (1/2)(1/π)arctan[wins-losses]

rendering the final forumula:

Score=

1/3*((1/π)arctan[(player1kills-player1deaths)+(player2kills-player2deaths)]+0.5)
+
1/3*((1/π)arctan[player1kills+player1assists-player1deaths]+0.5)
+
1/3*( (1/2)[wins/totalgames] + (1/2)(1/π)arctan[wins-losses])

All of this info is easily collectable at destinytracker... except for games with friends. Not sure how to get that.

Well, full lists of players in every game are available on destinytracker...but it sure as hell wouldn't be easy to collect the data.

I just included assists in the second part of the equation.

Also, I just saw an error I forgot to correct last night.. I needlessly tried to shift the first part of the win/loss stat to fall within a range that doesn't make sense for the rest of the equation. The Win/Loss category should read as follows:

=(1/2)[wins/totalgames] + (1/2)(1/π)arctan[wins-losses]

rendering the final forumula:

Score=

1/3*((1/π)arctan[(player1kills-player1deaths)+(player2kills-player2deaths)]+0.5)
+
1/3*((1/π)arctan[player1kills+player1assists-player1deaths]+0.5)
+
1/3*( (1/2)[wins/totalgames] + (1/2)(1/π)arctan[wins-losses])

All of this info is easily collectable at destinytracker... except for games with friends. Not sure how to get that.

Ooof. Good question. I hadn't even considered control zones. Hopefully that is accounted for in the win/loss category, but I don't know of a way to measure control zone efficiency. You could probably sort the ranking by gametype?

Control points might be a difficult number to factor in. Think about it, if your team usually totals one or two captures per person did you win or lose? Maybe you grabbed C and B on blind watch and held them to the entire game. Or maybe your team grabbed A... and was completely shut out. A relatively high number of captures, when combined with a good enough k/d might indicate a situational aware team player though...

I get you. Part of me wonders if this would actually kill the joy of playing a bit. I love throwing math at things, so that is fun for me, but I would hate to think people would actually choose to not play with another person based on this number. My hope would be that this would just be an interesting factoid for people.

As long as it was difficult to derive to the point where people weren't dumping out of matchmaking once they saw a 'bad' player was on their team, I don't see how this could hurt. (You could honestly do that now, if you felt like checking their destinytracker page). I wish we could take it a step further and try to determine proficiency specific to loadout (i.e. am I better with pistols or ARs?). That way, you could determine which loadouts were best with specific teammates, which might significantly improve your play.

Also, I just saw an error I forgot to correct last night.. I needlessly tried to shift the first part of the win/loss stat to fall within a range that doesn't make sense for the rest of the equation. The Win/Loss category should read as follows:

=(1/2)[wins/totalgames] + (1/2)(1/π)arctan[wins-losses]

rendering the final forumula:

Score=

1/3*((1/π)arctan[(player1kills-player1deaths)+(player2kills-player2deaths)]+0.5)
+
1/3*((1/π)arctan[player1kills+player1assists-player1deaths]+0.5)
+
1/3*( (1/2)[wins/totalgames] + (1/2)(1/π)arctan[wins-losses])

There's GOT to be a way to mix spreads and ratios together...

As I posted to Beardfade, I try to stay away from variable ratios if possible because of divisions by zero and the intelligibility of the data

IF (death==0): compatibility = 1

That way, the only stat that would influence is whether or not the team won. Which makes sense, imho.

I would love to apply this to some stats, but I'm woefully under-experienced with web APIs. I'm interested to look into it though, maybe there is an interface to it that I would find more appealing.

Yeah, I have very minimal experience with APIs. The only thing I've done is modify existing tools to extract data I want. I'm curious to learn though....

My 3am brain is of little help though, I'm afraid.

I appreciate any and all feedback!

I would say assists are definitely important enough to be included in the "personal score" section - is a straight-up K+A/D not viable? Or something similar but for spread, rather than ratio?

There certainly isn't any harm in including assists in the spread (K+A)-D, other than that it potentially inflates this category's influence. As I posted to Beardfade, I try to stay away from variable ratios if possible because of divisions by zero and the intelligibility of the data, but perhaps I could work with that too.

That being said, and I say this in response to your last paragraph iconicbanana, I think there are many intangibles that would be difficult to measure, such as "role". Playing a support role, such as laying cover fire, would not be measureable (as far as I know). So, while counterproductive would not be the word I would use, I can understand where your coming from.

At the end of the day, I would work on this for the fun of it. I would still play with you, even if the stats said we were bad for each other. You can't measure camaraderie. :)

Both bungie.net and destinytracker pull individual game data, so you could source from there. Although I personally find this data spurious, since it doesn't factor playing with ransoms versus playing with voice-enabled teammates, which matters.

Good point. In my mind, this would be more of a player-initiated comparison where you choose who you are comparing yourself to. That will help self-select players as well.

And I'll be honest, I find this line of reasoning counterproductive. My mindset is to always excel in the role which my team requires; adapting to new challenges or teammates is part of what makes me a better player.

I get you. Part of me wonders if this would actually kill the joy of playing a bit. I love throwing math at things, so that is fun for me, but I would hate to think people would actually choose to not play with another person based on this number. My hope would be that this would just be an interesting factoid for people.

Setting aside the fact that I'm not certain this is possible*, I am curious why we're using a K/D spread and not a K/D ratio? For example, 5 kills and 4 deaths is the same spread as 20 kills and 19 deaths, but the ratios aren't the same.

Games are won by spread, not ratios. Well, that is kind of true, but the data is a bit easier to read, work with, and normalize with a spread. You add up all the spreads and you get the amount your team won by. You add up all the ratios and average them and you get ???? I see why you would like to use a ratio, but it can muck things up because then you have to account for divisions by zero, mapping the #'s onto something that is intelligible, etc. For instance (I'm thinking of 3 kills and 2 deaths or vice versa), most people don't know readily that .67 is the inverse score of 1.5, but they can tell that that +1 and -1 are related.

I'm fine with other solutions, but I'm curious as to what formula you would use to bring k/d into relationship with the other parts of the equation.

Also, there is something to be said about simply the quantitative value of kills and deaths when playing with another person. For example, my average Kills per Match might be 11 when I play with randoms, but 18 when I play with you (ckamp) or 7 when I play with iconicbanana. As you (ckamp) pointed out the other night, a good crucible player will actually absorb more of the available kills and thus my quantity of kills be lower. So, we also need to make an algorithm that gives some weight to the quantity of kills and deaths that cannot be measured solely with a spread or ratio.

Hopefully this is where the aggregate kills and deaths of the two of you will balance that out a bit. The win/loss category will also help account against this phenomena. I'd also like to add assists into the personal part of the equation which will offset kill-absorbing a bit.

I think this also requires some adjustments made for match type. For example, captures lead to increased points per kill. Average captures per match could be useful, though of more use would be how many zones and duration of holding did you get? Not sure how these would way in, but 2 people could be great control partners, but horrible clash partners.

Ooof. Good question. I hadn't even considered control zones. Hopefully that is accounted for in the win/loss category, but I don't know of a way to measure control zone efficiency. You could probably sort the ranking by gametype?

Lastly, what considerations would we need to make in order to make this work for relationships greater than 2? How would we do this between 3-6 players?

I hadn't really thought of that yet, as I was focused on single-person comparisons, but I suppose that in part 1 of the equation you could simply do a combined k-d spread for the team. Each player would have their own score because of the individual component.

*What I need to find out (and I simply haven't looked yet) is if there is a way to pull in info for individual matches. If Bungie keeps stats of matches, great! I was thinking perhaps the best way to do this query would be to pull in an object of player 1's games and then search through that object for games that Player 2 participated in. Seems like a simple way to reduce the amount of data the query needs to process. Might be more challenging as we add Players 3-6. Once we're able to get which games are played together, we then need to evaluate performance separately and apply maths to quantify the relationship.

Sounds solid, but I'm horribly inexeperienced with APIs and the way the Destiny databases are configured.

Setting aside the fact that I'm not certain this is possible*, I am curious why we're using a K/D spread and not a K/D ratio? For example, 5 kills and 4 deaths is the same spread as 20 kills and 19 deaths, but the ratios aren't the same.

Also, there is something to be said about simply the quantitative value of kills and deaths when playing with another person. For example, my average Kills per Match might be 11 when I play with randoms, but 18 when I play with you (ckamp) or 7 when I play with iconicbanana. As you (ckamp) pointed out the other night, a good crucible player will actually absorb more of the available kills and thus my quantity of kills be lower. So, we also need to make an algorithm that gives some weight to the quantity of kills and deaths that cannot be measured solely with a spread or ratio.

I think this also requires some adjustments made for match type. For example, captures lead to increased points per kill. Average captures per match could be useful, though of more use would be how many zones and duration of holding did you get? Not sure how these would way in, but 2 people could be great control partners, but horrible clash partners.

Lastly, what considerations would we need to make in order to make this work for relationships greater than 2? How would we do this between 3-6 players?

*What I need to find out (and I simply haven't looked yet) is if there is a way to pull in info for individual matches. If Bungie keeps stats of matches, great! I was thinking perhaps the best way to do this query would be to pull in an object of player 1's games and then search through that object for games that Player 2 participated in. Seems like a simple way to reduce the amount of data the query needs to process. Might be more challenging as we add Players 3-6. Once we're able to get which games are played together, we then need to evaluate performance separately and apply maths to quantify the relationship.

Both bungie.net and destinytracker pull individual game data, so you could source from there. Although I personally find this data spurious, since it doesn't factor playing with ransoms versus playing with voice-enabled teammates, which matters.

And I'll be honest, I find this line of reasoning counterproductive. My mindset is to always excel in the role which my team requires; adapting to new challenges or teammates is part of what makes me a better player.