Would be useful for building more advanced management/planning tools while also allowing for more user friendly tools. EVE has a really good API. Obviously something this extensive couldn't be implemented in one release, so I suggest a small initial release followed by a regular expansion of functionality.

Reasons for implementing:

• Makes the game attractive to people who like developing tools.
• Less work for 'official' developers in the long run.
• Makes the game easier to get into for new players without dumbing
• down actual game mechanics.
• Makes 3rd party tools less 'hacky' to get the information they need.
• Most of the information in initial release already available on the website (not as much work involved?).

Initial release:

• Only one way data requests
• Level
• Skill levels
• Ship inventories
• Cash balance
• Team and rank
• Team ledger data.

Future updates:

• Loot logs
• Credit transfer logs
• [Team] Base logs
• View [Team] Base construction menus
• Limited two way features
• Cash transfer
• Team funds transfer
• [Team] Base management

As always opinions, corrections and further or alternate suggestions welcome. Dev replies on feasibility appreciated greatly ^_^.

I like the idea, and I'm pretty sure that JeffL has wanted something like this for a long time. He talked about ways to manipulate slaves and bases from the web/mobile devices.

-ERMAN

Bump for discussion.

A really solid API, even a basic one, allows for easy dynamic manipulation of the client. Instead of adding new client features, just implement an API and adopt ideas from the community. You can have 50+ people working on client mods instead of just 1 or 2 from the dev team if you have an API in place.

An interesting idea, and I would probably use it, but it's probably damned hard to implement and not high on the priority list... I mean, come on, its been a month or more since our last server/client patch, which we desperately need; you think they're gonna get to this any time soon?

Most of the suggested initial release stuff just involves dumping database info in an organised manner (xml?), which shouldn't be too difficult to establish.

its not that simple, since there is a lot of info in the current xml save that should not be publicly accessible. there are also the security issues and what not.

There are plans to eventually have most of the data accessible via html, so it would be possible to use it as an api at that point. but its not ready yet (and wont be for quite some time).

Its at least good to know that it has been thought about. Thanks.