Programming

The CREST API has a fistful of endpoints available to 3rd party developers. Interestingly, sending a request to the root endpoint returns a JSON string of all available endpoints; pretty handy. https://public-crest.eveonline.com/ Most browsers will return this object as a download as there is no filetype associated with the response. When sent through an application however, the string can be read as normal. This stuff is pretty straight forward as all that needs doing is identifying the desired endpoint, some examples are outlined below. ...

As a developer it becomes difficult to see games in the same way as gamers. The perfect example of this for me is EVE Online - the fantastically technical MMO. I’ve tried to play it many times - and like many others found it difficult to really get into; now this isn’t a criticism of the game, I guess it’s just not my play style. But what I do love is it’s technical magnificence. ...

Show me what you’ve got! EVE Online does something wonderful with its data, it doesn’t hide it away behind fancy graphics and menus; it puts it on display for the whole universe to see. Almost everything you see in many of EVE’s user interfaces is pulled from a database with IDs, put in a table for you to filter and analyze as you see fit. However, these IDs are not shown in the game, instead their name and description are used to identify items in a market search for example. Requests to the CREST API require an ID, so how can we locate the ID of a given item name such as the common mineral Tritanium? If you’ve spent any time with EVE APIs, you’ll probably know this as 34 - but what about Kernit? or Heavy Missile Launcher I? ...