Skip to content
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

Add decryptor_type_id to industry job endpoints #1139

Open
4 of 8 tasks
kcbanner opened this issue Aug 26, 2019 · 0 comments
Open
4 of 8 tasks

Add decryptor_type_id to industry job endpoints #1139

kcbanner opened this issue Aug 26, 2019 · 0 comments

Comments

@kcbanner
Copy link

kcbanner commented Aug 26, 2019

Feature Request

It would be nice if we could see the type ID of the decryptor used in an industry job.

Use case

I'm building a industry/trade profit tracking tool (https://evetycoon.com/), and I currently can't accurately model input prices for invention jobs as it is unknown what decryptor was used.

If the type ID of the decryptor was added to the /characters/{character_id}/industry/jobs/ and /corporations/{corporation_id}/industry/jobs/ responses, then I could properly track the number of copies created and add the cost of the decryptor to the overall input cost of the job.

Authentication

Uses the same scopes currently used to read jobs:
esi-industry.read_character_jobs.v1
esi-industry.read_corporation_jobs.v1

Example return

Propose what an example return might look like. E.g.:

[
  {
   ... all existing fields
    "decryptor_type_id": 34202,
  },
  ...99 other jobs
]

Other Information

The game currently does seem to track this information, as viewing past jobs either shows a decryptor icon or not, but you cannot mouse over the icon to see the type.

image

image

Checklist

Check all boxes that apply to this issue:

  • Feature request description is provided
  • Use case exists
  • Feature requires a new route
  • Feature adds data to existing route
  • Feature requires new auth scope
  • Feature can reuse existing scope
  • Feature does not require auth
  • Meta feature, applies to all routes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants