These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

EVE Technology Lab

 
  • Topic is locked indefinitely.
123Next pageLast page
 

Delay of the CREST beta for developers

First post First post
Author
Previous Topic Next Topic
CCP Seagull
C C P
C C P Alliance
#1 - 2012-06-28 15:42:37 UTC
Hey all -

Sorry to bring these news, but we need to delay getting CREST into your hands. This is due to a couple of things - it has taken us longer than we expected to get the legal side of the "Developer License" in place, and we are also busy with making CREST work like it needs to for DUST 514.

Once we do get the beta rolling, we will start on Sisi as many of you have suggested. We are also likely to roll out some of the supporting infrastructure before the actual API access - stuff like signing up as a developer, and starting to create apps and select what oAuth scopes you'd like for the app to use. I don't have any release dates for this yet though.

So - no big picture plans have changed - we are releasing CREST to 3rd party devs, it will have read-write functionality, and it will be the same tech as we use ourselves, that we just extend to you through oAuth. We just need a bit more time to get it ready for external consumption.

Thanks for your patience, and let me know if you have any questions.

/CCP Seagull



Senior Producer, EVE Online Development CCP Games Reykjavik
Dragonaire
Here there be Dragons
#2 - 2012-06-28 20:57:11 UTC
Sorry to hear about the delay but can understand it taking a while since it's a major change for CCP as well on the inside to make it happen.

Finds camping stations from the inside much easier. Designer of Yapeal for the Eve API. Check out the Yapeal PHP API Library thread.
Acid Kanshi
AIFAM
#3 - 2012-06-29 08:34:30 UTC
We shall wait!

EVE-Cost is a manufacturing tool for EVE players. http://www.eve-cost.eu
Etil DeLaFuente
Aliastra
Gallente Federation
#4 - 2012-06-30 09:13:08 UTC  |  Edited by: Etil DeLaFuente
Quote:
There will be endpoints for a bunch of public read-only stuff, that require no authentication. Things like starmap data, basic character and corp info and such, item info and so on.


Does it mean the actual API system will be replaced at term with CREST ?
TornSoul
BIG
#5 - 2012-07-08 14:30:01 UTC
Shame about the delay - But such is life (and EVE in particular it seems Twisted)

--

As per the tech-demo from the FF, in it's current form the (implemented) functionality of CREST is very very limited.

Come time this will obviously be expanded.

As one of the first expansions, could I humbly suggest the ability to "give away ISK" (aka transfer ISK from my own wallet to someone else).
Being able to do this via a web-interface, and thus having the ability to automate it would be a HUGE help for me personally.

Currently I'm doing 100+ wire transfers each day of the alliance tournament (betting wins), and it's such a BIG pain in the arse having to manually do those transfers that many times...

I'm aware of other businesses out there who share the same woe as well...

Any word on whether you'd consider this as one of the first "expansions" would be greatly appreciated.
Two step
Aperture Harmonics
#6 - 2012-07-08 18:50:58 UTC
TornSoul wrote:
Shame about the delay - But such is life (and EVE in particular it seems Twisted)

--

As per the tech-demo from the FF, in it's current form the (implemented) functionality of CREST is very very limited.

Come time this will obviously be expanded.

As one of the first expansions, could I humbly suggest the ability to "give away ISK" (aka transfer ISK from my own wallet to someone else).
Being able to do this via a web-interface, and thus having the ability to automate it would be a HUGE help for me personally.

Currently I'm doing 100+ wire transfers each day of the alliance tournament (betting wins), and it's such a BIG pain in the arse having to manually do those transfers that many times...

I'm aware of other businesses out there who share the same woe as well...

Any word on whether you'd consider this as one of the first "expansions" would be greatly appreciated.


I've asked CCP Seagull for this several times, hopefully it makes the early list of functionality.

CSM 7 Secretary CSM 6 Alternate Delegate @two_step_eve on Twitter My Blog
CCP Seagull
C C P
C C P Alliance
#7 - 2012-07-16 13:25:52 UTC
Two step wrote:

I've asked CCP Seagull for this several times, hopefully it makes the early list of functionality.


There is nothing technically hindering this, but it's a call for game design to make. As we get closer to release, Soundwave and other designers will have a proper look at what functionality they are OK with releasing in CREST.

Most of the tricky questions here are around botting scenarios where people could combine legitimate API use with client botting, and get an automation chain that is way too good. So we will likely be careful with moving money around. But the request is noted, and we'll also do our best to release as much as we can that makes life in large-scale EVE operations easier.





Senior Producer, EVE Online Development CCP Games Reykjavik
Bienator II
madmen of the skies
#8 - 2012-07-16 16:46:59 UTC
CCP Seagull wrote:
Two step wrote:

I've asked CCP Seagull for this several times, hopefully it makes the early list of functionality.


There is nothing technically hindering this, but it's a call for game design to make. As we get closer to release, Soundwave and other designers will have a proper look at what functionality they are OK with releasing in CREST.



just make sure that you can write to the fittings, skill queue and read/write the corp chat ;)


market is probably the highest botting risk

how to fix eve: 1) remove ECM 2) rename dampeners to ECM 3) add new anti-drone ewar for caldari 4) give offgrid boosters ongrid combat value
iskflakes
#9 - 2012-07-16 21:49:09 UTC
CCP Seagull wrote:

Most of the tricky questions here are around botting scenarios where people could combine legitimate API use with client botting, and get an automation chain that is way too good. So we will likely be careful with moving money around. But the request is noted, and we'll also do our best to release as much as we can that makes life in large-scale EVE operations easier.


Think of this differently - If you give everybody high levels of automation then suddenly bots have no advantage anymore. Bots will only exist as long as there are tedious and boring things to do like updating market orders, missioning and mining. If mining was done more like PI (where you plan the extraction rather than doing it yourself) we would see fewer bots. Although I don't expect CREST to fix this problem, giving some automation to traders could still be a big improvement.

In other news, I would like to see CREST give access to corpse names, as currently these are not available through the existing API for some reason.

-
Desmont McCallock
#10 - 2012-07-16 22:07:02 UTC  |  Edited by: Desmont McCallock
iskflakes wrote:
In other news, I would like to see CREST give access to corpse names, as currently these are not available through the existing API for some reason.

I suppose you mean corp members names. Doesn't MemberTracking API call suffice?
Mikokoel
Mining Industry Exile Foundation
Synergy of Steel
#11 - 2012-07-17 08:04:36 UTC
Desmont McCallock wrote:
iskflakes wrote:
In other news, I would like to see CREST give access to corpse names, as currently these are not available through the existing API for some reason.

I suppose you mean corp members names. Doesn't MemberTracking API call suffice?


I think he really means Corpse names. In your inventory, every corpse is a "Corpse". But if you call show info, you get the actual name, e.g. "Mikokoel's corpse". I think he wants that information to be available through the API (AssetList for example)

Mikokoel | Head FC League of Unaligned Master Pilots
Two step
Aperture Harmonics
#12 - 2012-07-18 13:49:23 UTC
Mikokoel wrote:
Desmont McCallock wrote:
iskflakes wrote:
In other news, I would like to see CREST give access to corpse names, as currently these are not available through the existing API for some reason.

I suppose you mean corp members names. Doesn't MemberTracking API call suffice?


I think he really means Corpse names. In your inventory, every corpse is a "Corpse". But if you call show info, you get the actual name, e.g. "Mikokoel's corpse". I think he wants that information to be available through the API (AssetList for example)


Did you try the locations API? It gives the name of cans, I think it might work for corpses.

CSM 7 Secretary CSM 6 Alternate Delegate @two_step_eve on Twitter My Blog
iskflakes
#13 - 2012-07-18 17:13:49 UTC
Two step... I love you! It works perfectly.

Though seriously, was this documented? I never even considered using the locations API to retrieve item names. If it was called the "ItemNamesAndLocations" API then maybe it would make sense?

-
Two step
Aperture Harmonics
#14 - 2012-07-18 22:50:44 UTC
iskflakes wrote:
Two step... I love you! It works perfectly.

Though seriously, was this documented? I never even considered using the locations API to retrieve item names. If it was called the "ItemNamesAndLocations" API then maybe it would make sense?


Well, can you say any of the API functions have been documented? It was mentioned when the locations API came out, as it was (and still is) the only way to get the names for POS mods and ships.

CSM 7 Secretary CSM 6 Alternate Delegate @two_step_eve on Twitter My Blog
Desmont McCallock
#15 - 2012-07-19 07:01:29 UTC
Truth is that the API functions (except for the Location) is documented but for the Legacy keys. As I said on another thread, personally I don't intend to update the documentation (in EVElopedia or EVE Dev) until CCP pulls the plug on the Legacy keys.
TornSoul
BIG
#16 - 2012-07-31 20:36:02 UTC  |  Edited by: TornSoul
CCP Seagull wrote:

Most of the tricky questions here are around botting scenarios where people could combine legitimate API use with client botting, and get an automation chain that is way too good. So we will likely be careful with moving money around.


It would be very naive to think that any bot-operators aren't already doing this via *gosh* bots/macros if they feel they have the need to do so.

I'm a programmer myself, and it would in fact be rather trivial for me to write a program to control my mouse clicks, and enter the necessary text in to the wire ISK menu.

So I repeat : Any money launderer/whatever who needs this kind of functionality already has it and are already using it.
They couldn't care less if this feature was added or not, it would make no difference to them.

Those it _would_ make a difference for however, are those of us choosing to abide by the TOS/EULA,

Please consider that.
Artem Valiant
NecroRise Squadron
Galaxy Spiritus
#17 - 2012-08-05 08:04:17 UTC
Have you any assumption when will be released a beta version? I really can't wait to try it.
Captain Thunk
Explode. Now. Please.
Alliance. Now. Please.
#18 - 2012-08-05 11:54:10 UTC
Desmont McCallock wrote:
Truth is that the API functions (except for the Location) is documented but for the Legacy keys. As I said on another thread, personally I don't intend to update the documentation (in EVElopedia or EVE Dev) until CCP pulls the plug on the Legacy keys.


Legacy keys are better. They can do everything CAK can do and more.

If I have an account with 3 directors of different corps then I would need 4 CAKs to be able to access every page available. With legacy keys, I need only 1.
Steve Ronuken
Fuzzwork Enterprises
Vote Steve Ronuken for CSM
#19 - 2012-08-05 16:56:04 UTC
Captain Thunk wrote:
Desmont McCallock wrote:
Truth is that the API functions (except for the Location) is documented but for the Legacy keys. As I said on another thread, personally I don't intend to update the documentation (in EVElopedia or EVE Dev) until CCP pulls the plug on the Legacy keys.


Legacy keys are better. They can do everything CAK can do and more.

If I have an account with 3 directors of different corps then I would need 4 CAKs to be able to access every page available. With legacy keys, I need only 1.


So a legacy key can expose only a certain page, when I don't want to hand a lot of extra information to, say, a killboard site?

Blink

Would be nice if CAKs allowed multiple corp data on a single key, but I guess that would be a trifle complex.

Woo! CSM XI!

Fuzzwork Enterprises

Twitter: @fuzzysteve on Twitter
Captain Thunk
Explode. Now. Please.
Alliance. Now. Please.
#20 - 2012-08-05 17:57:04 UTC
indeed, if only it were somehow possible to run both systems concurrently Roll
123Next pageLast page