{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
originally posted in:BungieNetPlatform
1/30/2017 6:01:08 PM
8
What Stats fields do you use, really? (and what do you wish we had?)
We're interested in knowing what stats fields you *really* use, and what stats you wish we had.
Let us know - this information will be extremely valuable to us as we try to figure out how to improve the Stats system (both in scalability in the future by removing unwanted/unused stats, and in usefulness by knowing better which stats would be valuable that we don't yet expose)
English
-
-
1 ReplyLate to the party, but here we go. All entries are presumed to start from "Response.data" from the "/Platform/Destiny/Stats/PostGameCarnageReport/" endpoint, summarized as "game". game.period game.activityDetails.referenceId game.activityDetails.activityTypeHashOverride game.activityDetails.instanceId game.activityDetails.activityName game.entries[].player.destinyUserInfo.displayName game.entries[].values.kills.basic.value game.entries[].values.assists.basic.value game.entries[].values.deaths.basic.value game.entries[].values.score.basic.value game.entries[].values.activityDurationSeconds.basic.value game.entries[].values.team.basic.displayValue game.entries[].extended.weapons[].values.uniqueWeaponKills.basic.value game.entries[].extended.weapons[].referenceId game.entries[].extended.values.weaponKillsMelee.basic.value game.entries[].extended.values.weaponKillsGrenade.basic.value game.entries[].extended.values.weaponKillsSuper.basic.value game.entries[].extended.values.slamDunks.basic.value game.entries[].extended.values.sparksCaptured.basic.value game.entries[].extended.values.medalsPaybackKill.basic.value game.entries[].extended.values.allMedalsEarned.basic.value game.entries[].extended.values.weaponBestType.basic.displayValue game.entries[].extended.values.longestKillSpree.basic.value game.entries[].extended.values.resurrectionsPerformed.basic.value game.entries[].extended.values.medalsAvenger.basic.value game.entries[].extended.values.zonesNeutralized.basic.value game.entries[].extended.values.zonesCaptured.basic.value game.entries[].extended.values.orbsDropped.basic.value game.entries[].extended.values.orbsGathered.basic.value game.entries[].extended.values.relicsCaptured.basic.value game.entries[].extended.values.combatRating.basic.value game.teams[].teamName game.teams[].score.basic.value game.teams[].standing.basic.displayValue My wishlist: - More in depth kill and assist information. For each weapon have a kills and assists array that consists of a displayName and quantity. This would allow you to do a reverse comparison and see what each player was killed by the most, and by whom. - ActivityDetails of PGCR should report custom options set for private matches, such as match length, time of day, and score limit. - Additions to account.characters[] currentActivityHash to show game mode hash, maybe an override for private matches as well.
-
I would like to see some more raid statistics. Was it a fresh run or checkpoint? Was challenge mode completed? How many times has a guardian completed challenge mode? I would also love an endpoint that returns all the current players in someone's game, such as in a current crucible match or raid.
-
"Time equipped while in a combat zone" would be valuable for distinguishing between equippable items of otherwise equal light levels, and would more accurately reflect preferences than the current XP amount available today.
-
3 RepliesEdited by chrisfried: 1/30/2017 9:05:24 PMI'm partial to the following: - period - entries.player.destinyUserInfo.membershipType - entries.player.destinyUserInfo.membershipId - entries.player.destinyUserInfo.displayName - entries.player.bungieNetUserInfo.membershipId - entries.values.activityDurationSeconds - entries.values.fireTeamId - entries.values.team - entries.values.leaveRemainingSeconds - entries.extended.values.secondsPlayed ETA, I'd love to see: - Timestamps of who killed whom, with what - Medal timestamps
-
I am a big fan of [url=http://destinydevs.github.io/BungieNetPlatform/docs/EnemyHistoricalStats/]EnemyHistoricalStats[/url] which would be nice to see a more detailed/consistent breakdown of enemies. Lots of little obscure uniquely named enemies that are not tracked or get merged into their corresponding enemy class. I still need to build my Enemy Bestiary... I would also like to see more information about the current activity in the GetAccount endpoints, at the very least so you can accurately determine what map, mode, game type, etc is currently being played. Fireteam size would also be handy for checking against people on your friend's list you'd want to join. Perhaps it'd be cool to see what type of weapon damage (Solar, Arc, Void) is being used per kill? ie People could then determine how many noobs are using an Arc weapon when it's Solar burn or the spread of damage when its Match Game.
-
It would be valuable for Crucible to include "# of assists associated with my kills" and "with my deaths". This would permit players to discern from their history whether they die frequently to team-shots or to duels, and help focus their personal improvements accordingly. For instance: If I die 10 times in a match, granting 30 assists to their teammates, I might focus on positioning; but if I only grant 2 assists to their teammates, I might focus on dueling.
-
2 RepliesSocial space access ("Can this character visit social space X" given X in { Reef, Iron Temple, Lighthouse }) currently requires iterating over the stats history of every individual activity when in many cases the individual statistics are not relevant beyond "Can this character visit social space X?".
