These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

EVE Technology Lab

 
  • Topic is locked indefinitely.
Previous page12
 

Issues with KillLog.xml.aspx
Author
Previous Topic Next Topic
Etil DeLaFuente
Aliastra
Gallente Federation
#21 - 2012-05-27 09:53:36 UTC
Desmont McCallock wrote:
And this is the reason why EVEMon can't have a Kill Reports monitor.
It's been two expansions now and I feel so neglected.



Use EveKill API like the rest of us. Their new EPIC api is quiet good.
Etil DeLaFuente
Aliastra
Gallente Federation
#22 - 2012-05-27 09:59:55 UTC
Artctura wrote:
This is seriously, one of the things that amazes me was not fixed with the new API system. I can't think of a reason why this isn't technologically simple, but it is an absolute pain when your trying to keep track of multiple director API's for a kill board. I need to watch logs, stagger pull times and do all sorts of other stuff because this is a "BY CHARACTER" issue.

I can understand it being by key, I can't understand it being by character. It's almost as if someone put the wrong field in the code somewhere.


Well, i petitioned it, got a "by design" response. Maybe if everyone pissed by this "poorly thought design" petition it, ccp might actually change something. (or not)
Desmont McCallock
#23 - 2012-05-27 10:11:15 UTC  |  Edited by: Desmont McCallock
Etil DeLaFuente wrote:
Desmont McCallock wrote:
And this is the reason why EVEMon can't have a Kill Reports monitor.
It's been two expansions now and I feel so neglected.



Use EveKill API like the rest of us. Their new EPIC api is quiet good.
I don't like EVEMon being depended on another service, except of course CCP's API (data provider) and BattleClinic (host). No offence to Karbowiak for creating it.
And for clarification EVEMon doesn't store the data it retrieves and its design philosophy is not to use a DB.
Etil DeLaFuente
Aliastra
Gallente Federation
#24 - 2012-05-27 10:29:25 UTC  |  Edited by: Etil DeLaFuente
Desmont McCallock wrote:
Etil DeLaFuente wrote:
Desmont McCallock wrote:
And this is the reason why EVEMon can't have a Kill Reports monitor.
It's been two expansions now and I feel so neglected.



Use EveKill API like the rest of us. Their new EPIC api is quiet good.
I don't like EVEMon being depended on another service, except of course CCP's API (data provider) and BattleClinic (host). No offence to Karbowiak for creating it.
And for clarification EVEMon doesn't store the data it retrieves and it's design philosophy is not to use a DB.


It all depends on the benefits your users could get from such a feature. Having to rely on a third party is not so important if the benefit is high. And i suspect evekill is not going to die anytime soon. Look for instance dotlan, if i'm not mistaken, it uses evekill api pretty much in the same way you'd do.

but, i totaly agree that CCP should provide it first.
Artctura
SUNDERING
Goonswarm Federation
#25 - 2012-05-28 17:03:58 UTC
Etil DeLaFuente wrote:
Artctura wrote:
This is seriously, one of the things that amazes me was not fixed with the new API system. I can't think of a reason why this isn't technologically simple, but it is an absolute pain when your trying to keep track of multiple director API's for a kill board. I need to watch logs, stagger pull times and do all sorts of other stuff because this is a "BY CHARACTER" issue.

I can understand it being by key, I can't understand it being by character. It's almost as if someone put the wrong field in the code somewhere.


Well, i petitioned it, got a "by design" response. Maybe if everyone pissed by this "poorly thought design" petition it, ccp might actually change something. (or not)



But why is it even by design. I can't understand the technical limitation here. The API simply reports the last 100 kills and can be walked backwards, presumably to 0, but at least 30 days in the past. It returns less than 100 kills if that is all there were in the last 30 days.

What specifically here requires that there only be 1 external api client hitting this per CHARACTER?

Artctura for CSM 2013
Desmont McCallock
#26 - 2012-05-28 18:20:13 UTC
The fact that the API call was designed when there were limitations and is abandoned since.
Dedaf
United Brothers Of Eve
#27 - 2012-06-03 09:24:27 UTC
I have had the very same problem.
It seems to be true whats being posted here, that you can only have 1 killLog API key per character.
I had 3 API keys for different tools that i use, and i had put mark in all 3 keys to fetch killLog. After removing the killLog marker from the 2 other keys, then it works.
So now the only API key with a mark in killLog is the one i use for the killboard and now it updates fine. But i guess for you guys who need kill logs for other tools than just the killboard, then it sucks.
Hope they will fix this.

Want to know what is best to mine or build at which cost? then try out Dedaf's Industrial Tool http://dedafsindustrialtool.blogspot.dk/
Previous page12