EVE Technology Lab

Hey people,

Wanted to give you all a heads up about some changes coming to Sisi later today. Hopefully they will be deployed around 15:00. Here is a brief rundown of the changes:

Alliance resources:
- Version 1 of the Alliances resource is now deprecated.
- Version 2 has been added to fix the awkward formatting of having a href in a href nonsense. Sorry about that.
- V2 has a 5 minute cache.
- Fixed a defect in the Alliance resource where if the executor corp no longer existed the resource would fail to be parsed. Fixing this means the executorCorporation field is now optional.

Universe resources:
- Added ID for the regions collection and individual region resources.
- Added a constellations collection.
- Added ID to the individual constellation resource.
- Added a solar systems collection.
- Added the new constellations and solar system collections as a link in the root of CREST.

Contacts:
- Fixed a defect where if a contact list contained an alliance the resource would fail to parse.
- Finalized work on exposing read and write access for contacts to third-party developers.

Dogma information:
- Added two new collections for dogma effects and dogma attributes to CREST.
- Added information about a types dogma attributes and dogma effects to the type resource.
- Added a link to dogma effects and dogma attributes from the root.

Added character waypoints to CREST:
- This gives developers the ability to send a POST request to the waypoints resource, linked from the character resource, and set a client's auto pilot destination. This will turn off the autopilot on the client.

Other:
- Exposing a characters location with the charactersLocationRead scope and a cache time of 10 seconds. !! THIS CACHE TIME IS SUBJECT TO CHANGE !!
- Added ID attribute for types in market types.
- Added ID attribute for market groups in market groups.
- Added typeID to the type collection and type resource.





This is the current version on Sisi: EVE-2016-ALEX 14.1.993568.993561

You can see the version in the CREST root. When the last two numbers are both equal to or above 994194 it will have been updated to include all my stuff.

Some extra scopes are going to be required for some of these resources to work, namely charactersLocationRead and charactersNavicationWrite. I will post back once I have those on Sisi. I think the contacts write one is already there.

Here is an example of setting a waypoint:

{
    "solarSystem": {"href": "http://crest.regner.dev/solarsystems/30000142/", "id": 30000142},
    "first": true,
    "clearOtherWaypoints": false
}

It only works for solar systems at this time. I will try and add stations for the next release next month.

Anyways, gotta run. Will try and respond with more details later.

As an advisory this is going to be one of the first cases where we really bump a version number and break backwards. Specifically this is in the Alliance resource. If you use that and do not send an Accept header you are going to get the newest version and your **** is probably going to break. You have been warned.

https://eveonline-third-party-documentation.readthedocs.org/en/latest/crest/versioning/

I have added the following scopes to Sisi: characterContactsWrite, characterNavigationWrite, and characterLocationRead

Just solar system. Here is a sample output:

{
  "solarSystem": {
    "id_str": "30000140",
    "href": "http://crest.regner.dev/solarsystems/30000140/",
    "id": 30000140,
    "name": "Maurasi"
  }
}

It will return an empty dictionary of the character is offline.

Oh also, because I have been a bit busy I haven't exposed the new dogma resources in public CREST on Sisi. You should however have no problem getting them from authenticated CREST. Both linked from the CREST root.

See Fox. It's not just me who thinks xyz might be cool!

Thanks Fox for addressing this one;
- Fixed a defect in the Alliance resource where if the executor corp no longer existed the resource would fail to be parsed. Fixing this means the executorCorporation field is now optional.

I will test later with some that used to give the 500 error.

Depends on how much people yell at us.

find two closest stargates in one system, take very fast align/warp ship (taxi ceptor for example) and see how fast he can get from system load in that system to system change while jumping to next one. This should be absolute maximum this timer should be imho.

EDIT: tested for 25k km warp to gate. 11~12 seconds, so please dont make it bigger than 10 seconds. (tested in 1.7 s align time, 12.17 AU/s warp speed ceptor, without taking system loading into consideration but at the same time only to gate flash and not system name change, but those two "should" be comparable)

The idea is, that once You jump into the system there have to be enough time for cache to clear to catch that You are in new system before jumping to next one. I want to plot LIVE movement of my entire corp on map :)

when i thought about those upcoming changes i thought of why not have the eve client tell stuff via a localhost?
that would mean instant info and no TQ load at all?
i am a dummy at such things so i don't know about the technical sides of that brainstorm though.