These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

EVE Technology Lab

 
  • Topic is locked indefinitely.
 

Incursions/Solar systems API data and DB dump

First post
Author
Sentenced 1989
#1 - 2015-11-12 16:21:01 UTC
I'm updating some of my apps and I was interested if I can find out somewhere in DB how incursions are assigned?
Problem is I can't find either on CREST nor in DB which system is VG, which is AS, which is HQ?

Am I missing here something obvious? Is there some way to figure out which is going to be what programatically which doesn't involve me manually editing my big json object to add an flag after I've visited incursion?

We already own a big file with known systems, but some time ago incursions changed layout and then few days they changed it back. And there are still some of them which haven't spawned in a while and we still don't have those mapped. It would be nice to be able to get that information without having to wait for it to spawn since it's really testing my OCD with incurionType: unknown...


Thx ahead!
Sentenced 1989
#2 - 2015-11-16 09:02:47 UTC
CCP FoxFour on vacation? :D
CCP FoxFour
C C P
C C P Alliance
#3 - 2015-11-16 09:53:08 UTC
Sentenced 1989 wrote:
CCP FoxFour on vacation? :D


Incursion spawning is random. We pick a constellation that has a minimum number of solar systems and fits a few other parameters and yea... random.

The Drifter Incursions are a bit different in that they don't use a constellation, they are still random though.

@CCP_FoxFour // Technical Designer // Team Tech Co

Third-party developer? Check out the official developers site for dev blogs, resources, and more.

Sentenced 1989
#4 - 2015-11-16 10:44:30 UTC  |  Edited by: Sentenced 1989
CCP FoxFour wrote:
Sentenced 1989 wrote:
CCP FoxFour on vacation? :D


Incursion spawning is random. We pick a constellation that has a minimum number of solar systems and fits a few other parameters and yea... random.

The Drifter Incursions are a bit different in that they don't use a constellation, they are still random though.


My question is not about spawning algorithm in the future, it's about the systems itself getting type assigned.

So how to figure out which system will be Assualt for example in given constellation? There has to be a fixed algorithm that isn't random since we always have same Staging/VG/AS/HQ layout (with few anomalies happening couple of months back and CCP releasing in patch notes that it has been fixed)

EDIT:
I'm here talking about getting incursionType value either from CREST, DB, or way to calculate it (http://pastebin.com/fZmxPB5s has small example of our data set). We have DB running as well, and are able to query CREST as well, but we can't find a way to figure out this. Is it based on ID, is it based on distance from staging incursion system, or something completely else?
Sentenced 1989
#5 - 2015-11-18 10:09:42 UTC
FoxFour, had a chance to check my last response, it's under my impression we weren't talking about the same thing before?
Sentenced 1989
#6 - 2016-01-13 09:22:33 UTC
Sentenced 1989 wrote:
FoxFour, had a chance to check my last response, it's under my impression we weren't talking about the same thing before?


FoxFour? :D
CCP FoxFour
C C P
C C P Alliance
#7 - 2016-01-13 10:26:27 UTC
Thanks for the ping.

The code for this starts by taking a list of solar systems (all systems for the selected constellation) that are part of the tale (an incursion is a tale) and the quantity of internal and external jumps for each system. Internal being jumps to other systems in the scene and external being jumps to other solar systems. If I understand this right.

Sudo code is something like this:

stagingLocation = mostExternalJumps[0]

...code to calculate every systems jumps to the staging system...

distanceToStagingList = sorted(solarSystemList, key=lambda k: k.jumpsToStaging, reverse=True)
HQLocation = distanceToStagingList[0]

...code for calculating number of vanguard and assault based on the percentages dictated for this tale...

assaultLocations = distanceToStagingList[1:numAssault + 1]
vanguardLocations = distanceToStagingList[numAssault + 1:-1]

@CCP_FoxFour // Technical Designer // Team Tech Co

Third-party developer? Check out the official developers site for dev blogs, resources, and more.

Sentenced 1989
#8 - 2016-01-13 11:22:26 UTC
Thx, I will play around with this during weekend and see if I can make head and tails out of it.

BTW, is there any plans on including drifter/sansha attribute on incursion endpoint so we can differentiate between them?
CCP FoxFour
C C P
C C P Alliance
#9 - 2016-01-13 13:18:53 UTC
Sentenced 1989 wrote:
Thx, I will play around with this during weekend and see if I can make head and tails out of it.

BTW, is there any plans on including drifter/sansha attribute on incursion endpoint so we can differentiate between them?


Yes, that change should be shipped next month. It is already checked in for the next release.

@CCP_FoxFour // Technical Designer // Team Tech Co

Third-party developer? Check out the official developers site for dev blogs, resources, and more.