Posted - 2008.12.05 11:51:00 - [1]

 

Edited by: Foolish Bob on 10/12/2008 13:37:04
Edit - this is also discussed to some extent here and I've updated the title to better describe the issue

Whilst we all love the api for giving us access to corp kills and suchlike, there is something missing which I think could be solved fairly easily.
Basically, those of us who measure our worth as human beings on killboards like to have access to our kills, but if we're light tacklers or ecm, then as far as eve is concerned we haven't killed anything at all. If I wanted, for example, to create a local store of my kills, in the same way that I might want a local store of my market transactions for reporting then I'd have to trawl all the killboards I could find for the data. I can understand only listing final blows in the front end, so you might need a new query, and possibly a schema change, in order for the api to return all kills that a pilot was on, but I claim it wouldn't be the hardest change the devs have ever implemented to make our lives easier . Because I hate it when my users make only wooly requests, see the tech section below for update / comment. Else you can stop reading now.

---------------
Kills api implementation - suggestions welcome

Variables: string apikey
int userID
int characterID
int beforeKillID
int onlyFinalBlows

CacheTime: long (1hr)

Notes: As current API implementation but onlyFinalBlows
-- standard boolean assumption - 0=false !0=true
-- default !0
-- if set to false, returns 100 kills which have the characterID listed on the kill and an id code less than beforeKillID
-- if set to true, returns 100 kills which have the characterID listed on the kill as having the final blow and an id code less than beforeKillID