EVE Technology Lab

Hey guys,

I know a lot of people around here have a lot of requests for new features, fixes of old features, and just general herpity derpity. What I would like to do is get a bit more of a central location for us, CCP and you guys, to discuss what you as a community would like to see get done.

To be clear, nothing said here is a promise to get things done. Mainly a way for us to get a better feeling for what the community would like to see get done. This will then be balanced against what we would like to do and hopefully result in cool **** being done. Cool **** should also include fixes, because those are cool as well, not just new features.

A couple of ground rules:

• If you would like to request a feature or a fix for either the EVE API or Public CREST make a detailed post with an example use case, a brief description of why, relevant repro steps if it's a bug (and bug name if you submitted a bug report).
• Simple +1s of features, ideas, fix requests and such will be ignored. If you want to support another feature make a post that describes something else useful that you would like to see. If you make a good post about your own ideas and add a few +1s to the bottom of the post that will be acceptable.
• Keep all discussion civil or go away.\
• Please do discuss things, offer counter points for why something shouldn't be done, or why something should have a high priority/low priority. Again, if it comes down to just a +1 post we will ignore it. Add something more to the discussion or be ignored.
• There is a like button on the forums, please use that instead of making a post just to +1 an idea if you have nothing to add to the discussion.

This is a test, we may find a better way to do this or may just scrap it if this doesn't really work out.

Please also keep in mind that as it stands the EVE API and Public CREST are pet projects and are worked on in spare time. Don't go expecting a mad rush of new changes. Limited time is a big reason why we would rather be doing highly requested things instead of just completely random things.

Example post:

============================================
Idea: Allow us to query char/ContractItems in bulk
Description: Lots of players when they have contracts have a number of contracts and it's rare that we want just the information from one. Allowing us to query the contracts in bulk would ease our pain as developers and probably increase performance. :D

Idea: Some other idea
Description: Some description of the other idea.

Salpun's suggestion for exposing the DUST map layout via CREST would also benefit me greatly in this application I have over on this site because...
============================================

Lets get this discussion going shall we! :D

Any chance of getting x, y, z position on kilmails? That , plus more accurate than a second timestamps would make for some awesome battle visualizations

you mentioned the dust version of the system map could be accessed via crest

[common stuff]
Similar to eve/OwnerID (names=abc,def,ghi) please add eve/OwnerNames (ids=123,45,678) then we would have the same functions like CharacterNames and the CharacterID endpoint which could be deprecated cause ownerID+ownerNames would be more useful.

[factionwarfare]
The newly introduced api is great, but you forgot to add the upgradeLevel. you can view this ingame on the fw dashboard. afaik this level is needed to calculate the war progress (there's a nice progress bar on the dashboard which (with some math) can be shown out-of-game as well.

[indizies]
military/strategic/industry indizies of nullsec systems. To not increase the already huge file of the Sovereignty API you could add an additional api just for the indizies only (solarSystemID + 3x indizies) otherwise combine them (which will make the api call just bigger). It depends on what works better for you and the cache/api system.

[cyno beacons and fields]
especially cynobeacons cause they're stationary, won't change very couple hours and are watchable ingame anyway, cyno fields can expose to much likely when I would track this activity over time (game design decision?) (hidden fleet movement if combined with the Jumps api).

[pilots in space/docked]
nice to have (as you can see it ingame anyway), but could expose to much maybe intel if tracked over time (game design decision?).

[outpost]
eve/StationDetails: instead of just having a list, this would be for single stations only including the station/outpost description of the owner

[alliance]
eve/AllianceSheet: similar to CorporationSheet, but with more details including the description text (which atm you can only scrape from gate.eveonline.com)

[wars]
oh yes. Not sure which way is the best. List all ongoing wars? (maybe to many?, I've now clue how many wars are always active). Maybe add an endpoint where you can throw IDs of corporation and alliances and get the wars they're involved in. This way I could list "current" and "old" wars on the alliance or corporation representation on my site.

-- dream section --

[sovereingty contested]
First off: I don't want to get the old failed SovereigntyStatus API back, but a "contested" flag for SolarSystems (as soon as somebody onlined (not anchored) a SBU (which takes some hours) the system could receive a contested flag meaning this system is vulnerable and somebody is fighting over it. At that time the owner itself and the coalition partners usually know this already. Downside: this could lead to SBU tourism (it's just a dream).

--

enough for today: i guess when looking at other threads there're lots of good ideas

There are ongoing discussions about this very topic, I would rather not discuss it any further at this time. Sorry.

Idea: 'live' market data
Description: To complement the history option, full order information. Ideally with a cache as entirely live data on demand could be very disruptive

Idea: aggregate market data
Description: Hand it multiple ids in a single region, get back the buy and sell prices averaged over the 5% highest buys/lowest sells as well as the total volume of the market. Again with a cache.
Explanation: Averages over the whole market have a tendency to be more easily gameable. The percentile less so.

Idea: Blueprint data
Description: Hand in ML, PL, ME and industry, get back data on production times. (yes, it's in the SDE. would be nice to have another way to get it.)

Idea: The dust map layout
Description: We wants it we do. the pretty map layout.

Idea: Location api updated with nearest celestial
Description: Right now with the location api, we get the x,y,z, within the system. There's no indication of system (that's in the asset api) and to get the nearest celestial, you have to hit mapDenormalize.

Idea: Map data api
Description: Hand it a system id, get back the mapDenormalize entries for that system. hand it a region id, get the constellations and systems. Hand it a celestial id, get the data about that celestial

Idea: API to see Jump Bridge links that you can see on the starbase manager today.

Idea: Tower Mod Stats. Big pipe dream I know, but being able to map this would be so awesome!

sorry forgot the stats I wanted, on/off, Shields, Armor, Hull.

Idea: Blueprint details
Description: It's not exactly a new idea but I'd still like to have it: add blueprint details like ML, PL and remaining runs of owned BPs to the API.

Idea: include more precise location for in-space assets in api. Nearedt celestial or naybe even pos id/planet/moon for pos modules and content within those modules

This would save a lot of dewelopment time for pis assets trackers and fuell management