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

The new forums are live and can be found at

EVE Technology Lab

  • Topic is locked indefinitely.

[CRUCIBLE] Extra implant and blueprint info being added to killmails - Info for 3rd-party devs

First post
CCP Masterplan
C C P Alliance
#1 - 2011-11-21 13:47:58 UTC  |  Edited by: CCP Phantom
Hi all.
As you may be aware, we're adding a couple of extra bits of info to killmails in Crucible. I wanted to make sure that you wonderful third-party developers had up-to-date details, so you can start showing this extra data in your killboards and other apps.

For implants on capsule kills:
  • Killmail
  • Implants will be listed under the 'Destroyed items' section, with a (Implant) marker, similar to how some items in a ship kill have a (Cargo) or (Drone Bay) marker now.
  • API
  • Destroyed items have a flag attribute, showing their location prior to destruction. Currently this can be 5 (Cargo) or 87 (Drone Bay). Fitted implants will have a flag of 89
  • More details here (and in the associated comments thread): My brain was equipped with the following implants

  • For blueprints in cargoholds:
  • Killmail
  • Blueprint Copies will be appended with a (Copy) marker. Blueprint originals will be displayed unchanged
  • API
  • A new singleton attribute has been added to the item nodes in the KillLog API query. For BPCs, this will have the value 2. For all other items (including BPOs) this will have the value 0

    Hopefully this should be clear enough to follow. These changes are on Singularity already, so you should be able to generate test data as required.

    Please note that this extra data will only be valid for kills that occur after the Crucible release. Kills generated before will be in the new format, but won't have the extra useful data.

    If you've any questions about using this new data, feel free to ask here. Can I humbly ask that you keep design questions ("Why can't I extract implants from corpses?") to other suitable threads please.

    "This one time, on patch day..."

    @ccp_masterplan  |  Team Five-0: Rewriting the law

    Lutz Major
    Austriae Est Imperare Orbi Universo
    #2 - 2011-11-21 15:26:35 UTC
    Best plan: Masterplan!

    About the singelton attribute: in the AssetList we have rawQuantity -2 to determine a BPC. In the Killmails we get the singelton attribute +2 :(

    It's not a big deal (we all have to program it anyways) but could you put it more in line?

    Squizz Caphinator
    Stribog Clade
    #3 - 2011-11-21 15:50:29 UTC

    blueprints being identified as copies or original! yay!

    Various projects I enjoy putting my free time into: |

    wanking monkey girl
    #4 - 2011-11-21 16:03:49 UTC
    great implant's and bpoc show up on km's, this makes me happy.
    Here there be Dragons
    #5 - 2011-11-22 04:51:21 UTC
    I'm with Lutz Major it would be nice if you used -2 for the BPCs to make it less confusing otherwise a great change.

    Finds camping stations from the inside much easier. Designer of Yapeal for the Eve API. Check out the Yapeal PHP API Library thread.

    Ph Ranger
    The Ur'Quan Masters
    #6 - 2011-11-23 12:44:32 UTC
    Killmail text contain (Copy) marker, but API don't contain new attribute.

    Killmail text (Singularity):
    Maller Blueprint (Copy) (Cargo)

    API xml (
    row typeID="969" flag="5" qtyDropped="0" qtyDestroyed="1"
    CCP Masterplan
    C C P
    C C P Alliance
    #7 - 2011-11-23 13:10:41 UTC
    I'll have a look into why AssetList uses -2, compared to KillLog using 2. I'm not sure I'll be able to change anything now though, due to code-freeze deadlines etc.

    Ph Ranger - Thanks. I'll go figure out why the test API isn't showing the singleton attribute. I suspect it simply hasn't had a code update pushed to it yet.

    "This one time, on patch day..."

    @ccp_masterplan  |  Team Five-0: Rewriting the law

    Arkady Sadik
    Electus Matari
    #8 - 2011-11-23 13:27:07 UTC  |  Edited by: Arkady Sadik
    CCP Masterplan wrote:
    I'll have a look into why AssetList uses -2
    The asset list uses "rawQuantity". Internally, apparently, singletons are stored as quantity -1, BPCs are now stored as quantity -2. A rawQuantity of 2 would imply a stack of 2 non-singletons. Why use singleton as an attribute to the kill mail API and not rawQuantity as well? (I guess rawQuantityDropped and rawQuantityDestroyed ...)
    CCP Masterplan
    C C P
    C C P Alliance
    #9 - 2011-11-28 13:38:39 UTC
    The test API has just had a code update, so now the singleton attribute should be showing up for destroyed/dropped items

    "This one time, on patch day..."

    @ccp_masterplan  |  Team Five-0: Rewriting the law