From what i saw, zkill was put into reinforced (something like cached only) mode for a while after the M-O battle. Anyway, if you not sure about zkills current status, stats are provided here: https://zkillboard.com/ztop.html
You could see there if no kills were processed.
prometh wrote: ↑Fri Dec 09, 2016 19:34
Its a change to the zkb api, limiting the start time to full hours, can you try the attached file (goes to common/includes) ?
Thank you for this. This fixes the problem, but creates a new one:
If there are more than 200 KMs in an hour, the last kill timestamp never advances to the next hour and cron keeps pulling the same set of kills over and over. The fix on the zkill side would be to have it always return at least a full hour worth of kills + one kill of the next hour.
EDIT: Maybe something using pagination or the afterKillID modifier can be done to solve this.
valid point, I didn't think of that. Thanks for mentioning.
I just pushed a fix that makes use of zKB's pagination feature to work around that situation.
is there an easy way to make the fighter killmails more accurate? you only get a fighter killmail if you kill a whole squadron. it can be anywhere from 2-12 fighters which makes the killmail worth considerably more.
example:
Satyr II goes for 8.5mil each in Jita but the killmail only says 8.5mil. a whole squadron (12 fighters) died so it should be 8.5x12 (102mil) for this particular fighter. is it possible to build that into the killboard?