open All Channels
seplocked Assembly Hall
blankseplocked [Request] API Update to change reporting of kills
 
This thread is older than 90 days and has been locked due to inactivity.


 
Author Topic

Foolish Bob
Caldari
The Dirty Rotten Scoundrels
HYDRA RELOADED
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 Smile. 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

Tusko Hopkins
HUN Corp.
HUN Reloaded
Posted - 2008.12.06 11:22:00 - [2]
 

I could support this initiative if it does not put a big load on the EVE database itself, with killboard fetching kills like crazy all the time.
I suggest adding the specifcation of the cache duration (preferably long = 1h) for this feature.
Furthermore, you should rename the thread to something that better fits the assembly hall naming scheme and better describes the problem, e.g. [Request] Addition of final blow filter to Killmail API


Hesod Adee
Dark-Rising

Posted - 2008.12.06 21:26:00 - [3]
 

Edited by: Hesod Adee on 06/12/2008 21:26:09
This thread was asking for everyone on a killmaill to be sent a copy. Even if it meant that killmails wouldn't go out at all until the next downtime.

That would be a good solution for me as the only reason I want killmails to come through fast is so that I can keep hassling whoever gets it until they post it. But if I know I will be getting a copy, that won't be an issue.

Ignition SemperFi
No Falcons Allowed

Posted - 2008.12.07 01:08:00 - [4]
 

I can agree with this as long as the final blow/victim still receive the killmail stat instantly. While others participating receive it at downtime

Foolish Bob
Caldari
The Dirty Rotten Scoundrels
HYDRA RELOADED
Posted - 2008.12.10 13:42:00 - [5]
 

Edited by: Foolish Bob on 10/12/2008 13:43:49
Edited by: Foolish Bob on 10/12/2008 13:41:55
Originally by: Ignition SemperFi
I can agree with this as long as the final blow/victim still receive the killmail stat instantly. While others participating receive it at downtime


Updates made as per CSM request - cache time was already listed in the spec, but the killmail api is already an hour so I don't propose changing that.

Ignition / Hesod - this is an api change only - anyone using the client would see exactly the same functionality with this proposal

1 exception - Perhaps the corp mail kills in the client could run along the same lines, but I'm weary about the implentation of this, precisely for the reasons outlined by the CSM. I also don't see the point - any use I can think of for needing it, the api would be better suited for anyway.

Edit for failspelling


 

This thread is older than 90 days and has been locked due to inactivity.


 


The new forums are live

Please adjust your bookmarks to https://forums.eveonline.com

These forums are archived and read-only