New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Characters Assets: strange location_id #684

Closed
GoldenGnu opened this Issue Dec 18, 2017 · 7 comments

Comments

Projects
None yet
5 participants
@GoldenGnu
Copy link
Member

GoldenGnu commented Dec 18, 2017

Bug

Characters assets are returning some very strange values for location_id
Example: 9001359308000569359

Request

/characters/{character_id}/assets/
Reproduce with: Neugeniko

Response

As It's not my own character, I can not produce a result via esi.tech.ccp.is.
The bellow are reconstructed via jEveAssets data and may not be 100% correct.
location_id, item_id, and type_id should be correct, though.

 {
    "type_id": 33077,
    "location_id": 9001359308000569359,
    "location_type": "other",
    "item_id": 1025271267554,
    "location_flag": "AutoFit",
    "is_singleton": true,
    "quantity": 1
  },
 {
    "type_id": 17931,
    "location_id": 9001352597000041864,
    "location_type": "other",
    "item_id": 1025056159281,
    "location_flag": "AutoFit",
    "is_singleton": true,
    "quantity": 1
  },

Expected

No strange location_id

@tsuthers-ccpgames

This comment has been minimized.

Copy link
Contributor

tsuthers-ccpgames commented Dec 21, 2017

By the looks of it, your inventory is bugged. ESI is accurately reporting this item location as it is given in the DB, but obviously that value is not valid.

If this is your character, file a support ticket with the item ID's, and request a GM help you move them somewhere real.

@Neugeniko

This comment has been minimized.

Copy link

Neugeniko commented Feb 15, 2018

I've submitted support ticket #560452 to try get these items in a real location.

Cheers,
Neug

@GoldenGnu

This comment has been minimized.

Copy link
Member Author

GoldenGnu commented Mar 24, 2018

It’s a little unclear to me, if this have been fixed yet. If it’s not fixed, could you re-open the issue until it is fixed. Otherwise just confirming it’s fixed would be nice. 🙂

GoldenGnu added a commit to GoldenGnu/jeveassets that referenced this issue May 4, 2018

GoldenGnu added a commit to GoldenGnu/jeveassets that referenced this issue May 4, 2018

GoldenGnu added a commit to GoldenGnu/jeveassets that referenced this issue May 4, 2018

@ccp-zoetrope

This comment has been minimized.

Copy link
Contributor

ccp-zoetrope commented May 9, 2018

This has now definitely been fixed :)

@SpeedProg

This comment has been minimized.

Copy link

SpeedProg commented May 9, 2018

Is this fix in as they found out why some items are in strange locations or as in we just hide your bugged assets from you now and you will never get them back? :(

@GoldenGnu

This comment has been minimized.

Copy link
Member Author

GoldenGnu commented May 9, 2018

I can answer that:
It turned out that the first reply by tsuthers-ccpgames was not correct.
The true nature of the 9e18 assets, are that they're an artifact from a eve-online bug.
All the stuff you didn't manage to get from each exploration end up as 9e18 assets.
So, the correct thing is simply to hide them, as they don't exist in-game.

zoetrope may be able to explain it better, but, that is how I understand it

@tsuthers-ccpgames

This comment has been minimized.

Copy link
Contributor

tsuthers-ccpgames commented May 9, 2018

That's pretty close, but to expand, this issue as I understand it is restricted to blueprints. Please tell me if you find examples where that's not the case.

When you interact with a hacking site container, we fill it with "fake items", which are signified by very high ID's, so that you have something to scan. These items exist in the simulation, but are never persisted to the database. If you loot the container, the "fake items" get turned into real items and persisted. However, if no one loots the container and the site despawns or if someone fails the hack and it explodes, then it's contents are never persisted.

However, blueprints are silly, and because of Reasons™ they can't be created as fake items, so they get made as real items with you as the owner. If you fail to hack the container and it explodes, the simulation just forgets about everything inside it, but because the blueprints weren't a fake item they're actually in the DB as an item you own, but they're located inside a fakeitem that doesn't actually exist anywhere.

So, to be 100% clear on this: you never really owned that item. You failed the hack and it was destroyed or possibly left the site without looting it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment