EVE Technology Lab

Not sure... I haven't really decided. I was also thinking of merging pilots flown and matches played into one graph.

The order is the order I add it which is actually determined by how I build the list. I currently sort the lists from low to high on a specific attribute. Generally speaking I do it by some factor of how well they are doing. So damage done over damage received, ISK killed over ISK lost, that sort of thing. Can easily be changed in the python code though, just change how the list is returned.

Yea I think I will change it so it goes Fielded / Destroyed / Final Blows / Banned

Clicking your link does nothing but pull up quicktime but does not display anything. Just a "|" in the middle of the page.

I guess I should have mentioned it was a small video link. The code is too immature to put on the site yet but possibly next weekend.

Glad you like it


I just tested on my development environment - had a Bantam drop one drone and I shot at it with some missiles. The pilotstats endpoint correctly displayed the damage done to the drone as well as the damage the drone then did to my ship from auto-aggression.

Was just about to post about this. So here we go then:

In the interest of Science, we are upgrading the realtime info. Work-in-Progress structure can be seen here:
http://public-crest-duality.testeveonline.com/tournaments/5/series/50/matches/0/realtime/300/

Included in that endpoint are drones, missiles and projected effects. That's a lot of data, but as this is an experiment, no sense in holding back =)

we are also introducing an endpoint to get the more static type of information from a scene, which you will need to query if you use the latest realtime data in order to correctly infer what is happening. see:
http://public-crest-duality.testeveonline.com/tournaments/5/series/50/matches/0/static/

Included in that endpoint are planets, nebula and such. Also included are ships and their pilot as well as visible turret information.

Expect some degree of change on both of these tomorrow. Namely missiles will get an id and planets will have extra attribute tacked on. Note from CCP Veritas: Missiles may continue to not have IDs in replays captured prior to these change, but may suddenly receive them later.

One big point on the data contained in these endpoints:
what you get from here is data that you could infer by looking at a ship. Both game design and the tournament organisers are on board with this. As was the case previously this data is delayed by 60 seconds from the actual tournament.

On the subject of versioned endpoints:

If you pay close attention to the headers we return from the first endpoint, you'll notice you are now getting a application/vnd.ccp.eve.TournamentRealtimeMatchFrame-v2+json as Content-Type.

Should you want to get the old format for whatever reason, make your request with the Accept header set to
application/vnd.ccp.eve.TournamentRealtimeMatchFrame-v1+json and you should see the first version data format. Both format will be available for matches from the second and third weekend once the change is out to TQ.

3D match viewer is up. The code is still very much in the make it work phase(alpha). Should work today for live matches (you might have to hit f5 a few times).

Biggest problem is the projection of ship ticks to 2d is happening in software so they lag behind user input a bit, which really sucks but I haven't had time to figure a better solution. It works, it's reasonably right, and fairly fast (solid 60fps for me) but then there's tons of room for improvement. Anyway, I hope some one enjoys it, had a lot of fun making it.

It looks good most glaring thing that is different from the CCP stream is the active rep portion of the top bar is missing.

Great info: good to have out there for the people wanting to look at it really close.