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.
 

[BUG] KillLog API reporting incorrect flag and singleton values for blueprints within containers.
Author
Previous Topic Next Topic
Squizz Caphinator
The Wormhole Police
#1 - 2012-03-06 17:05:11 UTC
Subject says it all, but here are the details:

For items within Containers and Plastic Wrap it seems that the flag and singleton values are always 0. Flag should be 5 since the item is in cargo (this applies to all items, not just blueprints), and singleton should be 0 or 2 depending on if the item is a blueprint and it is a copy or not.

For example, killID 22230763 has many Tech II blueprints held within containers. Every one of these blueprints is being reported as an original, rather than a copy. The raw xml for this kill can be found here.

Various projects I enjoy putting my free time into:

https://zkillboard.com | https://evewho.com
Dragonaire
Here there be Dragons
#2 - 2012-03-07 16:20:13 UTC
https://bugs.eveonline.com/ might actually get it fixed Blink

Finds camping stations from the inside much easier. Designer of Yapeal for the Eve API. Check out the Yapeal PHP API Library thread.
Squizz Caphinator
The Wormhole Police
#3 - 2012-03-07 16:46:49 UTC
Dragonaire wrote:
https://bugs.eveonline.com/ might actually get it fixed Blink


Yup, and this post is for the 3rd party devs, for all 3 of us that are working on killboard code :)

Various projects I enjoy putting my free time into:

https://zkillboard.com | https://evewho.com
Dragonaire
Here there be Dragons
#4 - 2012-03-07 16:58:27 UTC
np just wanted to make sure you'd let CCP know directly so they might actually work on it. So many people just post things on the forums and expect them to see it and do something which doesn't always happen Blink

Finds camping stations from the inside much easier. Designer of Yapeal for the Eve API. Check out the Yapeal PHP API Library thread.
Desmont McCallock
#5 - 2012-03-07 17:31:53 UTC
I have already bug reported this as it also creates a defect when you're trying to parse the API data for contracts.
I don't expect this (or any other API bug) to be fixed soon rather than soon™.
After all FF is ahead and we have a long time till next expansion.