ESI Endpoints for Pyfa

[Ebag333]

So now that ESI is a thing, I'd like to start discussion on how we can leverage it, and what we need that it does/doesn't have. Plan is to figure out what we need and would like, and then we can start opening issues requesting endpoints.

Check mark means it exists and we can pull from it. No check mark means it doesn't. This is also a fairly high level overview, while I put down some of the JSONS that we have that I know about I'm sure I missed some.

Ships/Modules

• [ ] Items/Ships/etc (invtypes) https://esi.tech.ccp.is/latest/#!/Universe/post_universe_names https://esi.tech.ccp.is/latest/#!/Universe/get_universe_types_type_id
• [ ] Item Attributes (basic stats like volume, etc) (dgmattribs dgmtypeattribs)
• [ ] Item Meta Groups (invmetagroups invmetatypes)
• [ ] Item Traits (invtraits)
• [ ] Detailed attribute information (like stacking penalties)
• [ ] Effects list (dgmeffects dgmtypeeffects)
• [ ] Icons (icons)

Market

• [x] Item prices https://esi.tech.ccp.is/latest/#!/Market/get_markets_prices
• [ ] Market tree (invmarketgroups)
• [x] Insurance (we don't do this currently....but it'd be really cool if we did) https://esi.tech.ccp.is/latest/#!/Insurance/get_insurance_prices

Character

• [x] Char list https://esi.tech.ccp.is/latest/#!/Clones/get_characters_character_id_clones https://esi.tech.ccp.is/latest/#!/Live/get_characters_character_id_clones
• [x] Char skills (authed) https://esi.tech.ccp.is/latest/#!/Live/get_characters_character_id_skillqueue
• [ ] Clone status (Alpha/Omega) https://github.com/ccpgames/esi-issues/issues/863
• [ ] Alpha skill list https://github.com/ccpgames/esi-issues/issues/133

NPC

• [ ] NPC Damage Patterns
• [ ] NPC Tank Patterns

API

• [ ] Fits (authed)

Fitting Engine Stuff

• [ ] Buff table https://github.com/ccpgames/esi-issues/issues/144

[aquarhead]

What does these two mean?

• NPC Damage Patterns
• NPC Tank Patterns

[Ebag333]

What does these two mean?

Right now we have profiles built from scraped data off Chruker's pages. We use them to build average resist and damage profiles, so users can load them and see how well they tank and apply DPS against that specific type of NPC.

For example, Serpentis deal damage: EM: 0 Therm: 61.7% Kin: 38.3% Expl: 0%

I think if we got an endpoint that contained what Steve does here we could figure out a way to scrape the data and update it dynamically: https://www.fuzzwork.co.uk/info/?typeid=43604

[aquarhead]

Hi, are these endpoints not the correct ones for "Item Attributes" and "Effects list"? I think they should have all the information as in SDE? (They are ports of respective CREST endpoints)

[Ebag333]

Not only are these the correct endpoints, but the code for using them was done back on April 27th.

https://github.com/Pyfa-fit/Pyfa-fit/pull/68

[aquarhead]

All good, was just looking at your check list :)

[Ebag333]

There are still some things that are missing from ESI, but for the most part there is parity between ESI and the SDK.

The biggest thing that is missing for Pyfa is something that I'm guessing that you can't do, and that's effects (since they are hand written and sitting in a Python file).

Off hand I can't think of anything that's exposed in Crest or the database dump that ESI doesn't have yet.