EVE Technology Lab

Would really like to test this, but sadly can't access https://developers.testeveonline.com it just times out :(
So I gonna ask here, can you invite people into a specific quad using a POST to /characters/{characterID}/fleets/{fleetID}/members/ ? Because that would be really awesome for my current project. ATM I am not even using the igb invite because I can't have people just put in the first squad with a free space.

Will moving people between squads/wings be looked into as well?

Also, does the fleet info (pilot/ship/location) have the same delay as the ingame fleet composition window?

https://api-sisi.testeveonline.com/corporations/npccorps/

description value in unicode characters. Is it normal?

Will this allow us to create an open-to-all invite to fleet link? I.e., would we be able to build a tool where we create a link, link it in chat, and anyone who clicks it automatically joins the fleet (regardless of standings)?

Single. Best. Fleet. Change. Spectre are going to be happy bunnies.

I hope someone eventually puts this directly into game.

Just drooling, absolutely drooling!

You could always import a list of all the solar system ids/names and do a vlookup.







Also, would it be possible to implement the Concord LP Conversion rate in CREST? Since we can now see the LP Stores and everything it might make a bit of sense. Maybe in the https://api-sisi.testeveonline.com/corporations/npccorps/ or the https://api-sisi.testeveonline.com/corporations/1000026/loyaltystore/ pages?

I am encountering a minor issue/inconsistency. I'm using a outdated JSON script in sheets to import the data so it is a bit more annoying for me.

So i am currently looking at the crest endpoint here.

https://api-sisi.testeveonline.com/corporations/1000046/loyaltystore/

Currently the "average" order for every single entry (on this particular page) is like this

"iskCost":
"lpCost_str":
"iskCost_str":
"requiredItems": [edited out],
"item": {edited out}
"quantity_str":
"lpCost":
"quantity":

But for some reason, the "Republic Fleet Ballistic Control System Blueprint" (Line 4930), and a few others in this specific store, are all special snowflakes, and they look like this.

"iskCost":
"lpCost_str":
"iskCost_str":,
"akCost": 0,
"quantity_str": "5",
"requiredItems": [edited out],
"item": {edited out },
"akCost_str":,
"lpCost":
"quantity":

Not only is it showing the ak cost as well (From looking over some more data, it looks like it should only be showing the ak cost if the value is greater then 0), It's also showing things out of order, like the "quantity_str": above the "requiredItems": array, when compared to the majority of the other entries in the CREST. And because of this, it is causing my spreadsheet to not parse it correctly. I found a fix, but it seems like a bug to me.

I have no idea why the ordering would be different, but as Pete pointed out in no way should you be relying on the ordering of items in a JSON dictionary. The added akCost probably just means the item has an AK cost of 0 authored while the others just don't have anything authored.

At this point I am not going to even look at it until after the deployment on Wednesday. Let me know how things look after that