G Torq
ALTA B2O
370
   |
Posted - 2014.01.17 20:54:00 -
[1] - Quote
Hi all,
The following is just a "brainfart"-session, to see if we can come up with a workable kill-feed (aggregate) for DUST514.
First off, this doesn't have to be "mail" based - a feed via CREST would be just as relevant
An interface, read-only, where a tool can request the Kill Feed for a PlayerID:
Request
- CharacterID - publicly known ID of player
- CharacterKey - Shared Secret between player and DUST
- StartDate - First date to include
- (opt) EndDate - EndDate, default to yesterday
(note: for sensitivity and performance, resolution should not go below 1 day)
Reply
- ContractType - Public, FW, PC
- * Kills - Number of kills for date-range
- * Deaths - Number of deaths for date-range
- * Assists - Number of assists for date-range
- * Wins - Number of won matches for date-range
- * Losses - Number of won matches for date-range
- * DNFs - Number of matches left before match-end, for date-range
- * DamageDealth - Total Damage dealt for date-range
- * DamageReceived - Total Damage received for date-range
- * DamageHealed - Total HP healed in date-range
- * AdapterID - TypeID (or tag?) of Suit, Vehicle or Installation
- * * Kills - Quantity destroyed for date-range
- * * Deaths - Quantity lost for date-range
- * WeaponID - TypeID (or tag?) of weapon, turret, deployable
- * * Kills - Number of kills with WeaponID for date-range
- * * Losses- Number of item owned by player, and destroyed/lost for date-range
(some of this is redundant on purpose - let us get a discussion and see what we can ultimately come up with)
By limiting it to "Yesterday-and-earlier", it cannot be easily abused to enter a match, kill someone, and then look up details. Also, should help with caching as the data can be transferred wholesale to a front-end and then queried from there.
For sensitivity of data, I'd propose any DateRange + ContractType combination that results in less than 8 kills be ineligible for polling, and moved to the next valid date.
AdapterID and WeaponID could be extended upon by including simply typeID/Tag for everything destroyed/lost?
You'll note that I've left out CharacterIDs of killed/killing players in the above - I'm not immediately convinced this would be good to share, though I'm certainly open to include it if good arguments can be made :)
@CCP+CPM: Please indicate if this is something you would be willing to support ...
What kind of usage could this see?
Player Statistics sites
Sites like DUST514Stats.com could use it to track performance on a day-by-day basis
Corp internal tools
Some corps may want to track the performance, and engagement, of their players - see who is qualified, and who is absent.
Contract Systems ("Side Missions")
Sites for setting up side-missions a la "kill 5 scouts" (the kind of events we have now, from CCP), where players issue and collect side-mission-contracts.
(note: this should not replace in-game contracts, only allow for more complex contracts)
I fully expect the community will come up with more uses for this.
Team Fairy DUST
HTTP://Dust.Thang.DK/ - DUST514 Fitting Tool based on DUST SDE
|