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 Information Portal

 
  • Topic is locked indefinitely.
 

New dev blog: Briefly About Kill Reports

First post
Author
Previous Topic Next Topic
Genu
Sebiestor Tribe
Minmatar Republic
#61 - 2012-05-26 19:53:13 UTC
The API and text Killmails now show different information for super kills.

The API version includes ships e.g. a mammoth stored within a super - it then also includes items stored within these flagging them up as flag=0 i.e. none.

These items are not included in the dropped/destroyed text on the exported text version of the killmail.

This is fairly confusing behaviour - is this expected or a bug?
CCP Tuxford
C C P
C C P Alliance
#62 - 2012-05-28 22:19:59 UTC
Genu wrote:
The API and text Killmails now show different information for super kills.

The API version includes ships e.g. a mammoth stored within a super - it then also includes items stored within these flagging them up as flag=0 i.e. none.

These items are not included in the dropped/destroyed text on the exported text version of the killmail.

This is fairly confusing behaviour - is this expected or a bug?


Are you talking about the stuff stored in the ship maintenance array then it's intentionally left out to keep the export as text functionality compatible with pre-inferno. I'm totally willing to include it but it means that every website that supports pasting this text to them will need to update their code. Tbh at that point it's probably just better to copy them as xml code.

https://gate.eveonline.com/Profile/CCP%20Tuxford/StatusUpdates
MailDeadDrop
Archon Industries
#63 - 2012-05-28 22:54:16 UTC
CCP Tuxford wrote:
Are you talking about the stuff stored in the ship maintenance array then it's intentionally left out to keep the export as text functionality compatible with pre-inferno. I'm totally willing to include it but it means that every website that supports pasting this text to them will need to update their code.

The text version should have a "version" stamp in it at the beginning, so that parsing sites will have a clue that the kill report is newer than the parsing site is programmed for. (Presumably the API kill report has this functionality already; if not, then shame on you.)

MDD
Genu
Sebiestor Tribe
Minmatar Republic
#64 - 2012-05-29 21:51:56 UTC
CCP Tuxford wrote:

Are you talking about the stuff stored in the ship maintenance array then it's intentionally left out to keep the export as text functionality compatible with pre-inferno. I'm totally willing to include it but it means that every website that supports pasting this text to them will need to update their code. Tbh at that point it's probably just better to copy them as xml code.


Yes I was - It was actually the EDK killboard software that highlighted this - as we had the api fed items in the ship maintanence array turning up as part of the fitted ships, and then complaining that was wrong as the item was not on their ship. The raw text differing to the api version adding to the confusion.

It'll be interesting to see if anyone else has any opinions on this.

P.S. "Tbh at that point it's probably just better to copy them as xml code." -> having an xml version of the kill that could be copied out of the client in the same format as the API version would make life easier for 3rd party sites if that's what you meant :)
Ph Ranger
The Ur'Quan Masters
#65 - 2012-05-30 16:45:13 UTC
CCP Tuxford wrote:
Genu wrote:
The API and text Killmails now show different information for super kills.

The API version includes ships e.g. a mammoth stored within a super - it then also includes items stored within these flagging them up as flag=0 i.e. none.

These items are not included in the dropped/destroyed text on the exported text version of the killmail.

This is fairly confusing behaviour - is this expected or a bug?


Are you talking about the stuff stored in the ship maintenance array then it's intentionally left out to keep the export as text functionality compatible with pre-inferno. I'm totally willing to include it but it means that every website that supports pasting this text to them will need to update their code. Tbh at that point it's probably just better to copy them as xml code.

Still I think it's better to update the code even if every website will have to do this. In my opinion it's better than getting killmails with different information.
CCP Explorer
C C P
C C P Alliance
#66 - 2012-05-30 21:41:00 UTC
Genu wrote:
CCP Tuxford wrote:

Are you talking about the stuff stored in the ship maintenance array then it's intentionally left out to keep the export as text functionality compatible with pre-inferno. I'm totally willing to include it but it means that every website that supports pasting this text to them will need to update their code. Tbh at that point it's probably just better to copy them as xml code.
P.S. "Tbh at that point it's probably just better to copy them as xml code." -> having an xml version of the kill that could be copied out of the client in the same format as the API version would make life easier for 3rd party sites if that's what you meant :)
Yes, that's exactly what we are wondering.

Erlendur S. Thorsteinsson | Senior Development Director | EVE Online // CCP Games | @CCP_Explorer
Ph Ranger
The Ur'Quan Masters
#67 - 2012-06-05 05:38:03 UTC  |  Edited by: Ph Ranger
Example of "pre-inferno compatible" - [url]http://killboard.solar-fleet.ru/index.php?op=kill&id=1002695[/url]

P.S. Fixed link