r/evetech • u/Shadowlauch • Jun 24 '16
FoxFour appreciation thread
I just wanted to say thanks for all the hard work you put into the various APIs. You truly made them great again.
I wish you all the best for the future!
r/evetech • u/Squizz • May 10 '18
r/evetech • u/Shadowlauch • Jun 24 '16
I just wanted to say thanks for all the hard work you put into the various APIs. You truly made them great again.
I wish you all the best for the future!
r/evetech • u/Fuzzmiester • Jan 03 '18
r/evetech • u/atrophocy • Oct 26 '21
Hi all,
Quick notice for anyone who uses the Pathfinder mapping tool. The original author Exodus4d has been awol for some time, and as a result the tool is quite severely out of date with the state of TQ (missing pochven, trailblazer, recent wh changes). Come 1st of November his last version 2.0 will be unusable due to the upcoming Oauth changes.
We have a community supported fork that has been updated for all of these changes, and we just released v2.1.4 (typo'd the thread title version) this week to upgrade it to use JWT based auth tokens.
For those who are looking to set up a new Pathfinder server for their organization we have a docker-compose solution that is fairly robust and works well out of the box for most people.
For those who made use of the public pathfinder-w.space, we will have a new public server available shortly.
Join our slack. There's an active community of PF users/maintainers/developers who will be happy to help you upgrade your existing pathfinder to the new version, help you create a new one, or point you in the direction of a public pathfinder that you can use.
r/evetech • u/new_eden_news_bot • Feb 01 '17
http://developers.eveonline.com/blog/article/breaking-changes-and-you
Afternoon developers!
We've mentioned it before, but I'd like to give everyone a clear best-practices guide to how to use alt-routes in ESI to maintain application stability against a constantly evolving API.
Before I get into that though, we previously said we'd be updating a forum thread with all planned breaking changes to ESI. That's turned out to be a bad solution to letting you all know when we're planning to change stuff. It's hard for you to read at a glance, and it's totally outside the tools we use day-to-day to develop ESI.
We've moved this information to the ESI deployment timeline, here:https://github.com/ccpgames/esi-issues/projects/2.
The timeline shows the deployment of totally new routes, but it also shows the deployment of routes that are going to have breaking changes. Consider the following screenshot:
We can see that on the 24th of January, the following happened:
The /dev/characters/{character_id}/ route was bumped to v4. This indicates a breaking change on this route.
/latest/wars stayed on v1, but we're making a breaking change to the spec.[1]
/latest/universe/races was bumped to v1. Since v0's are not a thing, that means this was a newly created endpoint.
In general, you should know what versions of what routes you are using, and keep an eye on this page so you can see if those routes are going to be altered.
I've mentioned /v1 here, but let me expand, because this is important.
If you look at the top of the ESI UI, you will see three buttons: legacy, latest and dev. When you click on one, it will show you a list of endpoints that are available on that route. For example, you can make a curl request to https://esi.tech.ccp.is/latest/characters/95465499/, and get data about my marvelous self. Notice the latest in the middle of the URL.
You can also make requests tohttps://esi.tech.ccp.is/dev/characters/95465499/ (dev) and https://esi.tech.ccp.is/legacy/characters/95465499/ (legacy). These three routes may or may not return different data. Team Tech Co is supporting exactly three versions of a route at any one time:
/dev (where we may test changes with the community before promoting them, if appropriate. There is no stability here, we'll break this one without hesitation.)
/latest (the one you should be using)
/legacy (the previous version of latest, for you to use until you can update your app back to current latest)
These three routes (legacy, latest, dev) are convenience labelsto help you understand what is current at any given time. You should not be using them in your source code, as you will see in a minute.
When Tech Co promotes a change, we take whatever is in /legacy and throw it away. We take whatever was in /latest, and put it in /legacy, and put /dev in /latest. However, there's a problem here. If you're calling the /latest route in your app and we promote a breaking change, the /latest route will change underneath you, and your app will break. The legacy route still has the version you currently rely on, but your app is broken anyway. Sadface.
This is why you should be using versioned alt-routes. if you take a look at the current latestof /characters/{character_id}, you will see at the top a set of alternate routes:
As you can see from the screenshot above, the current alt-routes are /v4 and /dev. These routes are aliases for /latest. This aliasing goes multiple directions. You can infer that /latest and /dev are identical at the moment, because /dev is an alt-route of /latest. /latest is also an alt-route of /dev, and behind the scenes all three are being directed to the same block of code.
However, more interesting is /v4. If you make a request to /v4, you will get the same as /latest. When we next promote the /characters/{character_id} route, we will move/v4 to be an alias of legacy. This means when we promote a breaking change your app will not break if you are using /v4. Instead, you will be smoothly transitioned into /legacy.
Once an alt-route is only available on /legacy (or if you call /legacy directly), your app will start receiving warning headers with every payload, even on 401 unauthorized errors . If your app is running through a CI system, one of your tests should be blindly call every route I use and see if I get a warning header in the return. This will tell you if any of the routes you are using have been moved to legacy, so you can update your app back to latest.
So, to recap, to avoid having your app suddenly break when we push breaking changes to endpoints:
Use the versioned alt-routes for everything.
Never use the convenience label routes in your source code.
Have some kind of test you can run that will aggregate and call all the routes your app uses, and tell you if it gets warning headers.
Keep an eye on the deployment timeline!
And of course, the ever present 5:
If you want to keep up to date with ESI development or ask interesting questions, the best place to do it is in the #esi and #devfleet channels of the tweetfleet slack. You can request a tweetfleet slack login here.
I hope that explains a few things!
Bartender out~~
[1] This is complex, make sure you've read the rest of the blog before you come back to this. The code backing the /v1 route of wars was causing performance problem with the TQ cluster, so we chose to change the endpoint without bumping the version. This bypasses all the best practice stuff I just finished telling you, and risks breaking peoples apps. Because the stability and performance of Tranquility trumps other concerns, we chose to take that risk here. We couldn't afford to have people continuing to use the broken code, so we couldn't move it to legacy. Tricky problems with no good solution like this are exactly why it's important for you to keep an eye on the schedule and idle in the #ESI if you're running anything mission critical. This is not SOP; we only do stuff like this if we're backed into a corner.
r/evetech • u/gfdsayuiop • Jul 04 '21
Don't know if anyone would be interested in this but here's a probably badly written and definitely disgusting looking script to download EVE ships or other assets from the Eve Online server that I made during some of my free times. Also included are .obj 3d models I converted from .gr2 for your convenience.
here you go: https://github.com/puffingprie/GetEveModels
What it does: downloads assets from the server (currently for ships and their assets but you can provide your own resfileindex.txt from SharedCache and modify the script to download other stuff.) Also converts .gr2 to .obj models using gr2convert
Context: I wanted to use some EVE models to use as ships in a game called Stellaris but I found that repos like https://github.com/Kyle-Cerniglia/EvE-3D-Printing only contained .stl files which doesn't contain uv maps and I found that TriExporter wasn't able to display or export models to .obj and kept crashing every time I tried to do so. Luckily I was able to download them from the server and convert them with gr2convert into .obj to use in blender or maya.
There is no kind of error handling at all but it works and that's all matters
r/evetech • u/Fuzzmiester • Mar 29 '21
As I need somewhere for people to be able to get in contact (other than here, Eve, the eve forums, and slack) and I need somewhere to give away the partner skins, I have created a discord for that purpose.
r/evetech • u/EamonnDH • Oct 18 '19
https://forums.eveonline.com/t/wcsii-throttle-background-eve-clients-automatically/196290
tl:dr - limits the CPU usage of EVE clients in the background to stop your CPU setting on fire.
Warp Core Stabilizer II (WCSII) is a little notification tray utility I wrote to help me when running multiple clients. As I often use an ultrabook, it was becoming a problem that when I have multiple EVE clients open they’d use a not insignificant amount of CPU. This would cause heat, and in a small frame like an ultrabook, ultimately throttling. I’d tried ThrottleStop, fancy cooling pads, undervolting, and still couldn’t quite cope with ~4 clients open. When minimized they use a lot less resources, but not quite as few as I’d like, plus often it’s inconvenient to constantly minimize clients instead of alt-tabbing, so I built this utility.
It’s extremely simple and requires no config. Once opened, it’ll add a small icon to your notification area (Please be careful not to option multiple instances, weird stuff could happen). It’ll then monitor for running eve clients (by name, “exefile.exe”), and monitor the process ID of the active window. Any eve client that is not the active window will be forcibly limited to 2% CPU usage via Windows’ JobObject API.
Requirements
Windows, ideally 7 or newer. There will never be a Linux/MacOS version due to the way the utility works.
.Net Framework 4.0 or higher. You should already have this.
Caveats
Closing the utility will immediately close all of your EVE clients, no warning. Be careful!
Any crash within the utility will also cause all your EVE clients to suddenly close.
When running many clients, you might find 1-2 seconds of lag when swapping to a different client as the CPU limit is released and it comes back up to speed.
I literally made this last night and it’s barely tested and probably needs a lot of polish.
Use at your own peril.
Todo
A nice icon instead of the default .Net.
Configurable core assignment for background clients.
Configurable CPU limit for background clients.
Attempt to improve response time when reactivating a client.
A simple ‘homepage’ for the app to keep versions etc. instead of the janky link below.
Current release: https://isk.enterprises/tools/
r/evetech • u/Squizz • Sep 21 '18
Fair warning for those of you here, zkill api will be changing to just killmail_id, hash, and information zkill adds to a killmail sometime soon (TM). As kenneth put it:
> OK, so Zkill won't be changing he just isn't going to play middle man for CCP for free
In short, to hydrate the information you will need to hit the killmail endpoint on ESI.
A couple of questions:
Will this happen on redisq and/or the websocket? No, for now those will stay the same.
Will the limit be upped from 200? Yes, I plan on 1k, and hopefully will do 10k. HOWEVER, if I do 10k it will be cached for 24 hours, encouraging you to finally use redisq and/or the websocket.
r/evetech • u/CCP_SnowedIn • Apr 14 '18
r/evetech • u/new_eden_news_bot • Jan 24 '17
http://developers.eveonline.com/blog/article/esi-mail-endpoints
Greetings developers!
Team Tech Co. is pleased to announce that all mails scopes (esi-mail.organize_mail.v1, esi-mail.read_mail.v1, and esi-mail.send_mail.v1) have now been released and are available for general use. We're excited to see what everyone does with them! (Thunderbird plugin, I want to believe!)
However, I'd like to drop a quick reminder about section 2.3 of the EVE developer license agreement: 'Developer acknowledges and agrees that no Application shall be used [...] (b) as a means of phishing or spamming'
Our third party developers have great judgement when it comes to these types of issues, but I wish to make it clear that one of our key indicators of spam will be whether other people think you are sending spam. Applications that create work for our GM's by sending large volumes of unwanted mail (thus prompting people to create tickets asking us to do something about it) will not be tolerated. I would encourage you all to seek explicit consent to receive mail (above and beyond authorizing scopes) from your applications users, and to empower them to revoke that consent easily if they desire to do so. If you would like further guidelines, especially on the topic of dispatching mail to players who are not users of your application, The Spamhaus Project has a great page on the definition of spam.
Additionally, programmatic use of EVE Gate to dispatch mail is now considered a misuse of the EVE Gate service . We will provide a short grace period until the 7th of February to allow anyone using this mechanism to disable it. After this date, there will be consequences for anyone continuing to use this method to send EVE mails.
Let's all be good netizens, and happy developing!
~CCP Bartender
r/evetech • u/MintNick • Feb 09 '23
Hi, I made a tool to manage the local setting files.
Download: https://github.com/mintnick/eve-settings-manager/releases/tag/v1.0.0
Code: https://github.com/mintnick/eve-settings-manager
Similar to the old tool EANM, it automates the copy, rename, paste process, to make all accounts and characters align to the same setting.
And some other features:
- Cache names so it doesn't need to fetch from API every time
- Can overwrite to selected targets
- Create backup
- Add notes
- Support multiple EVE servers (Tranquility, Serenity, Singularity, etc.)
- Support English and Simplified/Tranditional Chinese
Hope it helps.
r/evetech • u/nixedtech • Sep 17 '20
Its been about a year now and most recently, I updated https://evemarketdeals.com and the Android app to support bulk market items. Other updates include support for publicly accessible Citadels, an Eve Market Browser, and market orders in low and null security systems. Furthermore, I wrote a blog post about I determine what is a deal and how the scoring systems work located at https://evemarketdeals.com/blog/how-does-eve-market-deals-work/. I am interested in any feed back.
r/evetech • u/new_eden_news_bot • Apr 18 '16
http://developers.eveonline.com/blog/article/the-end-of-public-crest-as-we-know-it
Hello everyone,
Really short dev blog to give you all a heads up on a change coming with the Citadel release in how we handle CREST.
We have made a fundemental change in CREST and no longer support public CREST. Instead of having public CREST for public resources and authed CREST for authenticated stuff we are now just going to have CREST on the crest-tq.eveonline.com domain. If you request a resource from CREST that should be public it will just work and won't require any authentication. Wonderful stuff this is! However we are unable to support public CREST when this change is deployed. We will add a 301 redirect from public-crest.eveonline.com to crest-tq.eveonline.com but if you're client doesn't respect 301 redirects you may experience issues.
This change will be going live on April 27th during the downtime for the deployment of the Citadel release to TQ.
CCP FoxFour
r/evetech • u/Squizz • Oct 18 '15
Many thanks to /u/ChribbaX for hosting this 26gb available on eve-files. It decompresses to 283gb!
Enjoy!
r/evetech • u/ccp_foxfour • Mar 11 '14
r/evetech • u/Squizz • Jun 08 '18
r/evetech • u/new_eden_news_bot • Nov 08 '16
http://developers.eveonline.com/blog/article/introducing-the-esi-api
The EVE Swagger Interface is a new framework developed by Team Tech Co to underpin the new ESI API. If you don't know what this is, you should go here to read the blog Introducing ESI - A new API for EVE Online.
This blog will dive a little deeper into the design and technical specifics of ESI, going to get into the base design of ESI to explain a few basic principles of what's going on behind the scenes. Most of this is transparent to the front-end, but may be of interest to some capsuleers regardless.
ESI was designed to be a single interface to all information EVE related. As such, if ESI and the cluster agree on configuration, you can change the datasource query parameter on any route (including /version/swagger.json) to the server name of your choice.
You will see this in the ESI UI as a select menu in the header/nav bar, and in the datasource enum in the spec itself.
As a (potentially) interesting side-note here, there are actually three ESI environments running, an esi-dev, esi-test, and the production esi. With esi-dev or esi-test and a bit of configuration (which will be replaced with tooling), EVE developers can actually query their local development server through ESI.
Auth is still handled by SSO. There are new scopes which ESI uses, you can make new developer keys (or alter your existing) to make use of the new scopes. If an ESI endpoint requires authentication, you will see a red exclamation mark on the route description in the swagger UI. Mouse hovering over this icon will tell you what scope the endpoint requires.
ESI will handle redirecting your authentication header to the correct SSO for verification (depending on the datasource query string argument). SSO is not multi-tenant though, so you will need to create app keys on each SSO backend you intend to use.
ESI itself will have an API version (as defined in the spec), that version number however, is mostly irrelevant to API consumers (it's the version of ESI-lib). Instead, ESI versions each route individually. This allows us to make much faster changes and avoid the awkward situation of global API versioning.
As an example, let's say you have a route /v1/hello/string/, and you want to change the path parameter to accepting an integer instead. With a traditional API, the entire APIs basePath would have to be bumped. This is obviously a little less than ideal, considering there could be hundreds of other unchanged routes.
With ESI, you always (and only) get three complete APIs, /dev/, /latest/ and /legacy/. But each route is also given a numbered path, starting with /v1/. Alternate routes are mentioned in the route description (until something better comes along in the standards?).
/dev/ can change at any point, changes to /latest/ will be announced. After changes are made the previous /latest/ will be available as /legacy/, until the next version bump. If you want to avoid the return schema of your request suddenly changing, you can use the versioned alternate route. In that case, prudent developers may want to create unit tests (watch for the warning: 199 headers) to notify them when endpoints are moved to legacy. Additionally, we will be updating a stickied thread in the EVE Technology Lab subforum as changes happen.
Additionally, endpoints may be deprecated. When an endpoint is deprecated, a line appears through it on the swagger UI, and it begins returning the warning: 299 header. This is slightly different than a warning: 199 header, which you will receive if an endpoint was updated and there is now a newer version of it available. Deprecation is how Tech Co broadcasts an intent to delete a route. Deprecated endpoints may include a recommended alternate source or other message in the 299 warning, and you should move away from them immediately.
Because endpoints are versioned individually, the concept of an overall /v1/ (or 2 or 5) API is not very relevant, and no swagger-ui is provided for these routes. Browsing the API's capabilities should be done via /dev/, /latest/ or /legacy/. However, users who wish to indulge their curiosity may feed a /v1/swagger.json into their own Swagger UI to get an overview, if they wish.
As an aside, all ESI routes end with a /. The only exceptions are the /version/swagger.json routes and routes used by the swagger-ui, which are passed through ESI.
There are no rate limits in place, the plan is to rely on caching more than rate limiting.
ESI returns standard caching headers if the data is cached. Applications should notice and make use of these headers (expires and last-modified) on routes where they are provided.
We briefly touched on this earlier, but one of the major motivating factors of this design was to decouple the API from the monolith itself. As a consumer of the API, you should not have to care at all about the database structure, how or where the data is retrieved. All you should need to know is what inputs are allowed/accepted, and what exactly is being returned.
ESI takes this one step further. There is a generic concept of a data relay inside ESI, built on top of Google's PubSub. Because of this decoupling of data and API, it allows the retrieving end to move out of the monolith gradually and transparently. As long as something somewhere is listening and responding to events via PubSub, ESI will not notice if the service leaves the monolith and becomes standalone.
In the ESI API system, the codebase is split into two separate yet equally important groups: the esi-routers, who proxy routes and aggregate specs; and the esi-[endpoint]s, who fulfill the requests. These are their designs.
The routers are where most of the magic happens. They are the ones integrating with the Kubernetes API. The router finds the endpoints, and from each one, requests all of its swagger.jsons. It then combines all of these partial specs into versioned global specs. It serves the global specs, proxies the swagger-uis, and proxies ESI routes to their appropriate endpoint.
The routers are also a cluster, and use Redis to elect a leader among themselves. The leader continually checks for changes to the distributed spec, and the other routers all check for changes on the leader.
All routers also maintain telemetry on the endpoints, measuring the latency of each call, as well as tracking who made the request.
The endpoints can be considered mini, stand-alone ESIs. If you found a way past the router cluster and hit the endpoint directly, you'd find it serves a swagger.json for each version it has routes for (in addition to dev, latest and legacy), but does not have any other user interface. All authentication and caching happens on the endpoint level. Each endpoint serves one or more routes in its own little cluster (behind a Kubernetes ClusterIP service), able to horizontally scale at will.
Tech Co developers are regularly available on the tweetfleet slack (@ccp_bartender, @ccp_snowedin, @ccp_aquarhead, @ccpchimichanga), and we will be monitoring Reddit and the EVE Online forum thread if you've got questions or comments. We're especially keen to talk about anything you need from us to port your existing applications over from the XML API, so please stop by for a chat!
To the glorious future!
Team Tech Co
r/evetech • u/Squizz • Jun 07 '16
The purpose of this sticky thread it to provide developers with up to date information on API's provided for Eve Online as well as information and links to resources that provide very informative guides. This post will be fluid and subject to change over time. If something isn't found in this post, please check the sidebar too.
ESI
ESI is a the newest API being launched by CCP.
https://community.eveonline.com/news/dev-blogs/introducing-esi/
You can participate in CCP dev and third party dev discussion by joining Tweetfleet on Slack and hopping into #esi
Applications
Register your application for use with SSO functionality here: https://developers.eveonline.com/applications
API
https://eveonline-third-party-documentation.readthedocs.io/en/latest/
Anyone can contribute here, and please do, the documentation is far from complete.
CREST Rate limits:
150req/s for public endpoints
20 concurrent connections
XML Rate limits:
30reqs/s
Citadels
http://eve-guides.fr/index.php?article=132
Developers Blog & Recent Release Notes
https://developers.eveonline.com/blog/article/crest-renovations-2016-06
https://developers.eveonline.com/blog/article/new-crest-resource-for-bulk-market-orders
https://community.eveonline.com/news/patch-notes/patch-notes-for-may-2016-release
At this time there is very little support for Citadels in either the XML API or CREST.
Please contribute your ideas and thoughts to this post. I will do my best to keep it updated and maintained. Thank you!
r/evetech • u/new_eden_news_bot • May 23 '16
http://developers.eveonline.com/blog/article/new-crest-resource-for-bulk-market-orders
Hello everyone!
I wanted to inform you all about a new market resource in the CREST API. Until now, if you wanted to get all the market orders for Tranquility you had to request every type per region individually. That would generally be 50+ regions multiplied by upwards of 13,000 types. Even if it was just 13,000 types and 50 regions, that is 650,000 requests required to get all the market information. And if you wanted to get all the data in the 5-minute cache window, it would require almost 2,200 requests per second. While some of you came up with creative solutions to this problem such as prioritizing faster moving items, we decided we needed a better solution that was both easier to use and reduced load on our servers. As such, we have added a new market resource that is aimed at anyone who is trying to get all of the market data.
The new market resource can be found under/market/regionID/orders/all/ and returns all market orders for a given region paginated, with up to 10,000 results per page. For busy regions such as The Forge, you would expect around 30 pages of data based on the current trading volume. Here is a sample of the output:
{ totalCount_str: 306700, pageCount: 31, items: [ { buy: false, issued: 2016-04-02T02:15:32, price: 5716.55, volumeEntered: 50000, stationID: 60003760, volume: 9756, range: region, minVolume: 1, duration: 90, type: 21368, id: 4386193414 }, ... ], next: { href: https://api-sisi.testeveonline.com/market/10000002/orders/all/?page=2 }, totalCount: 306700, pageCount_str: 31}One of the things you will note about this resource is that we have trimmed down each order to be very slim. We don't include a link to the type, instead we supply just a type ID. We don't include the _str attributes. Everything that could be stripped out has been in order to reduce this resource response in size. Be warned though, even in its stripped-down form each page is several megabytes in size.
This new resource is going live tomorrow on May 24th on TQ, and is currently live on Singularity. We are already working on some performance improvements to CREST and this resource, and are hoping that we can eventually increase the orders per page from 10k to 30k.
One of those changes we are making to help reach the speed and size we want for this resource is removing all the checks we do that verify the response matches the mediatype for this resource. The reason for that is that CREST spends a large amount of time verifying that and on a resource this size it ends up taking far too long. What this means to developers is that while we are mostly confident in the response being what it should, there is a chance that attributes might go missing or be of a type they shouldn't be with no warning. To be clear, this removal of response verification is only happening to this specific resource.
If you have any questions or concerns, please let us know. Hopefully this new resource helps elevate some of the work you are all having to do and makes life easier.
CCP FoxFour
r/evetech • u/BigSako • Feb 25 '16
A well known eve-related news site (cough) states the following:
FoxFour was instrumental in rebooting the stalled third-party Eve developer program within CCP. Without his efforts some, of the third-party tools Eve players use today would not exist. FoxFour is also known for his socks and his soccer skills. He plans to depart CCP in June.
o7 FoxFour, thank you for all your efforts. EvE Dev community would not be the same without you.
Who is going to take over?
r/evetech • u/[deleted] • Jun 16 '18
I recently release a small status page for ESI that summarizes certain endpoints that may or may not be having issues. It refreshes data on the backend every 60 seconds.
EDIT:
Like the dumbass that i am I forgot to include a link to the source code
r/evetech • u/RisingStar • Apr 01 '16