Release I.N.T.R.A.: A utility for bounty-hunters to find useful mission/target system pairs, and enjoy interesting bounty statistics.

Imperial Navy Intervention and Rescue presents INTRA, a new service for Commanders, designed to help bounty-hunters locate valuable pairs of systems for accepting and completing pirate Massacre missions.

INTRA logo.png

An INIV prototype of this has been supplying me with very nice locations for quite a while. Following some very successful experiments in finding locations for other Commanders, including one for whom we replaced a four-system circuit with a single eight-faction Starport, we built it into a comprehensive utility for all to enjoy.

Searching​

The primary goal of the INTRA Search utility is to find a Shop system with as many useful factions as it can, from which Massacre missions can be obtained, all of which concern a single Arena system with good places to hunt.
  • Eligible system pairs are tracked constantly by monitoring EDDN faction activity over time.
  • Pairs are ranked by accounting for the number of useful factions, Supercruise distances, CNB/RES presence and Powerplay effects.
  • Many further options are available for filtering the Shop and the Arena, and using Hyperspace distance to affect the ranking.
INTRA search.png

Faction states which impact negatively the offering of pirate Massacre missions—or other conditions which prevent said missions—will cause a faction to be considered not useful within a given Shop. Being at war is a common temporary reason, while being an Anarchy faction precludes Shop usefulness permanently. Conversely, one Anarchy faction is required for an Arena to be matched.

For Commanders seeking only a place to hunt with no concern for missions, INTRA supports searching just for a loose Arena system. As a simple courtesy for Commanders not seeking combat, one may also search just for a faction-heavy Shop system without the Arena constraints.


Arena data​

INTRA has but one asterisk inherent to its nascency: We are building its body of CNB and RES information ourselves.
  • We know some limited forms of CNB/RES data exist in a few places, including for the purpose of searching, but we could not find anything downloadable.
  • We know that CNBs can change and can differ between Elite 3 and Elite 4; INTRA already tracks both.
  • We know that cataloguing RESs is a massive effort; INTRA makes this as streamlined as we could imagine it working.

Enter the INTRA Agent, a plug-in for EDMC or any compatible Journal service.

The plug-in reports the CNB statuses of systems you visit, and also any RES signals discovered. Using the Discovery Scanner is enough to update the former, and scanning any (personally) undiscovered ringed planets with the FSS will report the latter. This action alone affects the Arena rankings; a system known to contain a Hazardous RES—plus existing knowledge of its ringed planets—is enough to boost its Arena value.

INTRA agent arena.png

After a system with rings gains a RES report, INTRA then allows Commanders to -declare- the specific ringed body for that RES type, referring to the closest such case to the arrival star. The Arena valuation for that system will then be equivalent to INIV confirming its RESs internally.

For example, an INTRA search lead me to HIP 37735. I encountered all four RES types there, then visited that page to tell it that the Hazardous and Medium were around planet 7 and the High and Low were around planet 5. Of course, ring information declared publicly this way could be mistaken, but any damage is minimal given that the RES ultimately exists somewhere in the system. Moreover, we want to trust Commanders to make useful declarations.

INTRA system.png

Unlike any existing source we could find, INTRA produces the hourly snapshot of its Arena data for anyone to use. The original data deficiency was one of our motivating factors in the first place, so providing ours is very much our way of helping to alleviate the problem, or at least not to exacerbate it.

The above aside, we want to welcome any reliable CNB/RES data, if offered. Merging existing efforts should be no problem for us, as long as the format is clear and consistent!

For sake of retaining an example:
  • HIP 37735 will remain in the Reported state publicly rather than being Confirmed internally.
  • We trust Commanders to leave it set correctly with Hazardous 7, High 5, Medium 7, Low 5.
  • Commanders are welcome to test INTRA by changing the declarations in HIP 37735, though please restore them afterwards.

Statistics​

Finally, and by far my favourite part!

In addition to sharpening the Search function, the INTRA plug-in also reports bounty claim statistics. These are categorised by Starship type and by pilot rank of the pirates you eliminate. INTRA also records whether you used a Kill Warrant Scanner, and separates the bounty claims into the local and foreign parts.

INTRA agent bounty.png

If you ever wanted to know how bounty payouts differ between Expert and Elite, between Anaconda and Fer-de-Lance or between fitting and removing your Kill Warrant Scanner—this is the answer. Record a lot of bounty claims, and display aggregated results.

Of course, that page contains a lot of numbers. Displaying those tables visually is the first major goal after this release, and behind any great suggestions or data-merging INIV may implement first. At present it displays tables with minimum, average and maximum for local claims and for combined totals with Kill Warrant Scanner; following some conversations with Commanders, it will be a goal to provide numbers only for those cases where a Kill Warrant Scanner revealed a foreign bounty, and a quick chart of how often it reveals multiple foreign bounties.

INTRA stats.png

Downloadable bounty data samples are also planned, presently with caution for monitoring how large a bounty data set may grow. If it looks feasible, the plan is that it could be archived annually; the first set would be kept updated with data from launch, then become fixed on the cusp of 3309, after which a 3309 set commences.

For some lighter entertainment, Commanders are invited to peruse the Starship statistics page. It is quite biased at present, with the majority of its bounty entries being my own, however we are quite excited to see how it evolves.

Thanks​

A lot of thanks to CMDR Vulkarius for making a lot of different technical pieces work together.
For testing and useful discussion, I wish to thank CMDRs. Grawmad, Frank Likes Pie and Firehawk894.

I also wish to thank everyone engaging in interesting bounty-related conversation here; I read much more than I participate, and it helps greatly when it reveals small intricacies not previously considered.

Comments, suggestions and useful data sources are most welcome!

CMDR Aleks Zuno
Imperial Navy Intervention and Rescue
 
CMDR Vulkarius here!
Looks like Aleksandra has done a great job announcing INTRA, and getting me to make a forum account.

INTRA has just been updated to add a population filter, so that hunters can choose shops where the BGS is more stable.
Just put something like "500M" or "1B" into the population field.

Also following an excellent chat with @Vingtetun on Hutton Orbital Live where he mentioned some ideas for integrating INTRA with voice commands, I have formalised and released its search API.
The address https://iniv.space/intra/api/ will show the documentation if you view it in a browser, or access the API if you send a HTTP POST request.

To use his example of a voice command which finds a CNB, some request like this will look for a CNB in Odyssey within 20 Ly of Hutton Orbital, just the arena with no shop requirement:
{"ver":1,"lim":1,"ref":{"x":3.03125,"y":-0.09375,"z":3.15625,"max":20},"arena":{"cnb4":1}}
Response:
{"ok":1,"msg":"","ver":1,"head":{"shop":0,"arena":1},"body":[ { "arena":{"name":"WISE 0855-0714","addr":58144730663760,"edsm":4570,"eddb":19046,"ref_d":4.2,"pop":34825,"pow":"Zachary Hudson","port_d":-1,"post_d":964,"fac":{"all":4,"e":0,"a":0,"f":3,"i":1},"fac_t":1667070870,"cnb3":1,"cnb3_t":1666915280,"cnb4":1,"cnb4_t":1667068508,"ring_d":537,"ring_b":"5","visit":26,"haz":{"r":0,"c":-1,"d":-1,"b":""},"hi":{"r":1,"c":-1,"d":-1,"b":""},"med":{"r":1,"c":-1,"d":-1,"b":""},"low":{"r":1,"c":-1,"d":-1,"b":""}}} ]}
Looks like we have a CNB just 4.2 space miles away in WISE 0855-0714, also a few RESs (no hazardous though).

We have some good data progress - after 4 days of monitoring EDDN, the RES report coverage has just passed 62% of populated systems with rings.
We will continue to add manual confirmations for batches of the more higher-ranking arenas, but either way it's doing VERY well.
Even if the INTRA search just turns out to be a proof of concept and the real value is the arena data download, that's a success for us.
 
One week after its official launch, and in response to yet more interesting conversations with bounty-hunting Commanders, the INTRA service already has a couple of new major features. Through providing a solution for some, there is nothing quite like discovering a form of insight into exactly what others are trying to achieve, silently and without any indication that their ideas are unanswered.

Multiple shops​

For Commanders who still wish to make multiple Hyperspace jumps in return for involving additional factions, INTRA now has a solution for optimising that as well.

When missions from two or more Shop systems each converge upon one Arena system, these are now collected together and presented as one combined entry. Immediately after this update, I requested a simple report with no specific options:

INTRA 2 multi-shop.png

The Lambda Arae system—already a great seven-faction Hazardous RES result with the Powerplay voucher bonus—indicates that three additional factions can be included by visiting the Kairos system, albeit at a small Outpost. Note that Kairos would have added five factions if not for an ongoing war, and six if the Arbor Caelum Internal Defense faction was not prevented from offering Massacre missions due to owning the Arena system.

LTT 2099 and Sceptrum are another great Shop combination with an extra faction, though lacking the voucher bonus. It is a goal to tune the ranking slightly so that the extra faction prevails; at present both entries receive the same boost for having one extra Shop, leaving Lambda Arae ahead due to the Powerplay bonus in the Arena.

It is worth noting that INTRA also removes factions from the additional Shops if they have already had their coverage accounted for, so that only the genuinely new factions are displayed, as with this example:

INTRA 2 multi-shop duplicate.png

The LTT 12058 and LTT 2974 systems actually both had seven useful factions each, none of which own the Arena system, however the Revolutionary Party of LTT 2974 faction was common to both and thus excluded in the second Shop listing. Their missions may still be taken, if it helps to balance the contractual obligations of the bounty-hunter.

Search API​

Exactly as V has so kindly provided, Commanders wishing to use INTRA results as part of their own clever systems should find everything needed to do so at the INTRA API page.

Ironically, it occurred to us that the multiple-Shops feature already marks the start of a new version, leaving the above slightly outdated. For what it is worth, V assures me that a version 2 search is performed the same way, just with a slight difference in the results when multiple Shops are present which should not be difficult to deduce.

Otherwise, performing a version 1 search will continue to work exactly as documented.

Fixes and known issues​

43 systems have been updated to include their Asteroid bases at the same level as a full Starport. In most cases this has now added a Starport where INTRA previously considered such absent, and there are also a few cases where the extra Asteroid base has reduced the Starport travel distance.

Planetary ports are still not considered at present; INTRA is aware that their systems are populated and is able to use the system as a Shop, however their results will fall to last place unless elevated by being part of a multiple Shop result with a system which does have a Starport or Outpost. This can be seen by running a normal search with a reference system such as Asura:

INTRA 2 missing planetary.png

The systems Sovereign's Reach and Eol Procul Centauri show no Starport nor Outpost, however their planetary ports Harold's Respite and Fort Mug should both be valid for collecting missions. Present thinking is to replace the Port and Post display with a single Planetary number in such cases—and after updating INTRA with such a feature, of course.
 
Just applied a small fix for arena-only searches so that it no longer sends you across the galaxy just to get the ALD/Grom powerplay bonus.
Using the Colonia bridge as an example, searching from CB-56 (Eol Prou GE-A c1-29) right at the end would still narrowly favour the bubble just for that bonus.
Some irony there is that CB-55 (Dryooe Flyou WB-T b47-10) has a perfectly good CNB.

The problem was that an arena-only search could not assign any shop faction benefit, so any small powerplay bonus becomes disproportionate, effectively placing ALD/Grom systems in their own league above anywhere else.
It now gives arenas a sensible amount of initial benefit when shops aren't involved, diluting the powerplay bonus down to a more appropriate level.

An "ignore" option for powerplay is also now on the to-do list.
 
A second round of updates for the INTRA service:

Powerplay​

A new Arena option is available for ignoring the bounty voucher bonus in systems within the territory of Arissa Lavigny-Duval and Yuri Grom:

INTRA 3 powerplay ignore.png

With the Power set to Ignore, the only contributing factor in the ranked results should be the factions involved. Please note that Supercruise distances still apply as a detracting factor, and that a default search with the Power set to Any will still grant the Powerplay bias as before.


System statistics​

A new main System statistics page has been added, its address replacing one of the two locations at which the Claim statistics page was available. The Ship statistics page remains as before.

The first row shows an overview of populated systems which have received signal reports, either via the INTRA Agent or via EDDN:

INTRA 3 system stats.png

These will approach 100% ever more gradually as those seldom-accessed systems are visited eventually.

Next are the Navigation Beacons:

INTRA 3 CNB stats.png

The Known count will approach the total number of populated systems, as their beacon statuses are reported for the first time. The CNB count will increase similarly for those cases where the beacon is Compromised, though may also change in either direction when an actual beacon change is reported. The percentages should stabilise around the proportion of Compromised beacons across the Galaxy.

Finally, we have the Resource Extraction Sites:

INTRA 3 RES stats.png

As with the Beacon percentages, these will stabilise around the actual proportions of systems which contain each type of RES; for example, the above snapshot states that the chance of encountering a Hazardous RES in a populated system selected randomly is 31%—much of the deficit due to lacking a planetary ring. It is quite pleasing that this turns out to be well-balanced between the RES types, at least with the data INTRA has at present.


RES confirmations​

With the basic search functionality available and at least able to work with RES reports, much of our attention at INIV is now directed at the actual cataloguing of RESs throughout the Galaxy. Also available on the statistics page above is our progress report:

INTRA 3 RES confirmation.png

Within the set of systems which have planetary rings, these are the systems we have visited and recorded the nearest RES of each type, or absence thereof. This INTRA update has also provided us with a very convenient way to visit and record batches of star systems, to the extent that a hundred systems per day is actually a reasonable affair, at least until the majority of Bubble systems are exhausted.

With that rate having become the case, note that any prospect of merging an existing RES table now has to justify its opportunity cost. Quite reasonably, we will not merge a RES table if it would take more time to do that than to continue confirming systems ourselves, and even then it will have to be of very high quality and repute. In effect, we are just going to perform a full sweep of RESs per system ourselves.

INTRA searches will reflect those confirmations as more are added, and that same set is always available from the INTRA data page, along with all the signal reports and the up-to-date Beacon statuses as well. The eventual hope is that no longer will authors of bounty-hunting utilities have to imagine what excellence could have been for lack of strong Arena data.
 
So, can I use this to hunt bounty-hunters?

A bold question; it is neither within the scope of INTRA to endorse nor disavow the act of attacking bounty-hunters, but it is reasonable to suppose that INTRA could help to locate bounty-hunters, given that such could be at least a bit more likely to be found by visiting high-ranking Arena systems than by dropping at random. It is presumed that bounty-hunters know the risks of following lucrative locations before allowing such to effect their presence, just as bounty-hunter-hunters know the risks of interfering.

Additionally, we wish to caution prospective bounty-hunter-hunters to consider carefully that a similar process also could be used by bounty-hunter-hunter-hunters. Further iterations are unlikely, for at that point the altercation will have evolved into becoming the great Hunter Parity War with deadly skirmishes of Even versus Odd strewn across the populated Galaxy, forever embattled over their conflicting conviction regarding the question of who should hunt whom.
 
A third INTRA update has been deployed, this time to introduce a gentle step toward some consideration for Shops which have multiple Arenas.

Improvements​

Following the introduction of Arenas which have multiple Shops in the first update, the benefit value of multiple Shops has been reduced in cases where some of those extra Shop systems themselves had multiple Arenas. Such cases were never reported in an INTRA search, as indeed its present design demands a singular Arena system, however they were contributing to the rank with undeserved effect.

The service component has also received several performance improvements to its storage of star systems and factions, resulting in searches and system look-ups which complete much more quickly. The prior peasantry of awaiting results for more than one second—for which we apologise, of course—is now bygone.

Nearby systems​

As promised, and moreover to help expose more useful information about a star system under consideration, the System look-up now displays Shop and Arena information for nearby locations. Here is the view¹ for the Siriaba system, one of my older favoured Arena locations I encountered without automated assistance:

INTRA 4 nearby systems.png

We had quite a bit of discussion regarding exactly how to display those systems. The potential for confusion exists insofar as the Shops on the left pertain to Siriaba's bounty-hunting opportunities on the right, and the Arenas on the right are served by Siriaba's docks and factions on the left, indicated by the cross-over arrows. However, un-crossing those would involve swapping the Shop/Arena lists or swapping the Shop/Arena system information, neither of which would keep intact our original design decision always to place Shop-like items to the left and Arena-like items to the right.

In any case, the purpose is to reintroduce some of the details which the main INTRA search suppresses by design (for now...). For example, consider the Djaghire system, to which the original INTRA prototype lead me for use as a Shop:

INTRA 4 Djaghire.png

A logical outcome; it has only one Arena at the Backlum system, as expected for an INTRA search result. It is also very common for high-ranking Shop results to lack an anarchy faction given that such usually displaces a mission-bearing faction, with the result that not even Backlum itself can be used as a Shop location for Djaghire.

Suppose we follow that link and take a look at Backlum:

INTRA 4 Backlum.png

Interesting. Djaghire served Backlum exclusively, but now we can see that the Goman system is also within range to act as a second Shop, with some factions and a similarly close Starport. We know its missions cannot be exclusive, for if so then Goman would have been included in the original search result, but with how many other targets will its missions be shared? Let us follow that trail one more step to Goman:

INTRA 4 Goman.png

The best-case scenario; just one other target. Goman shares its missions with the Hap system, but it can at least be used to supplement income while otherwise hunting in Backlum. Not only that, but the hazardous RES in Hap also makes for a very good Arena, thus actually making Goman a great Shop system on its own merit. It may not be in the single-Arena league as Djaghire is, but it is well above average, and almost as good as my pre-INTRA Shop in Chicomoztoc—when not in simultaneous War and Election, of course.

RES confirmations​

Since just under a week ago, and with none at all confirmed yesterday, the updated count is:

INTRA 4 RES confirmation.png

I believe V flew out just to get Ceos done then started a RES tour back through the Pleiades. In the meantime, we established RES distances for every system within 55 light-years of Achenar—and within 37 light-years of Sol, as it happens. As usual, a data download for all reported and confirmed RES locations thus far is available from the INTRA Data page.

We will achieve and provide RES data for the entire populated Galaxy.




1. That is to say, the system information view for Siriaba, not a literal view of its RES location. Regardless, I wish to avoid any undue disappointment which may be caused by the lack of said picture, and I find those rings to be subtly pretty in a way which would make me feel remiss not to show them.

INTRA 4 Siriaba 1080.jpg
 
A couple of minor INTRA updates, plus an idea we would really like to implement if we can!

Information expiry warning​

For results listed in a search and for nearby systems in a System look-up, there are now colour-coded warnings where the information should be considered unreliable and in need of a fresh report via EDDN:

INTRA 5 stale.png

The Faction ("Fac") display and the individual CNB displays (Elite 3.8 and Elite 4.0) each show in red when the information gets a little stale, and moving the pointer over those will display exactly how old they are. There has been no change to the underlying INTRA service; the age information was already present, just not used prior in its user interface.

The present thresholds are 24 hours for Faction information and 7 days for Navigation beacons. There may be a case for setting a longer Beacon duration, however the Faction duration really ought not be longer, for any more would allow an upcoming War state to pass through Pending and become Active without any alert in the meantime. If anything it ought to be something like 20 hours, but we will see how it goes.

Arena data spreadsheet​

A human-readable version of the Arena data has been added to the available data downloads:

INTRA 5 data.png

The Arena list download is available here, and has been designed for viewing and searching with a spreadsheet program. As with INTRA itself, note that the CNB and RES reports are only as good as we can read via EDDN broadcasts, and that the confirmed RES locations will update as we scan them.

Speaking of which—

RES confirmations​

We celebrated reaching one-sixth, then remembered that the intervals between celebrating unit fractions will only increase, so we did a little extra on the path to one-fifth:

INTRA 5 confirmation.png

Mission-tracking idea​

As a distilled version of the information available via various existing utilities for tracking pirate massacre missions, and specifically to assist with accepting the missions in a way which balances the required kills, we tried integrating it as a test:

INTRA 5 missions.png

It is far from ready for publication, but it looks like it could work in theory, and we really like the idea of having that service tucked away in a browser tab. Its top feature priorities are a couple of things I wish personally that OD Massacre Stack Manager would have:
  • Total/Difference numbers which follow the remaining kills, not the total kills.
  • Total solo/wing material rewards as well as the credits reward.
As a service, the biggest problem (and potential usage annoyance) is that the only way to handle that data responsibly is to use the Frontier log-in as a means of confirming the Commander which should be displayed. That said, it occurred to us that such could also become a very nice extra option for allowing Commanders to provide INTRA with their bounty statistics, if we can get that part to work.

Please do not wait for that feature to materialise, though. Conversely, if V appears with questions related to the Frontier log-in, now you will know why!
 
With the upcoming split between Elite 3 and 4, we will need a much more first-class way to separate their EDDN messages, so we can keep two versions of all the faction information across the galaxy.
EDDN instructs uploaders to use the the "horizons" and "odyssey" flags which represent the CMDR expansion access, but what we actually need for INTRA is whether the game client is 3 or 4.

I can see that EDDN has specified a "gameversion" header field, however the broadcasts do not seem to include it at all.
Literally while writing that, a few EDDN messages with a valid "gameversion" just arrived!
It looks like EDDI and Journal Limpet are complying with that, so for the moment I will presume that others are to follow (great job everyone, very much appreciated!).
Unfortunately I think it will have to skip "CAPI-journal" messages because it is critical whether they came from 3 or 4, but the concept is there.

That makes for a much better outlook, so I'll go ahead and prepare INTRA so it knows to stop accepting reports which have no "gameversion" information.
In addition to tracking CNBs for 3 and 4 already, the plan is to do the same for powerplay, system controlling factions, and the entire faction presence/state information.
The plan for the front-end is the relatively easy part - remove the CNB 3/4 option, and add a global option which changes the entire view and report ranking between 3 and 4.
 
Ahead of Odyssey update 14 and its galactic divergence, INTRA now should be ready for it!

Dual galaxy​

INTRA now has expanded support for Commanders across both Elite 3.8 and Elite 4.0. To a limited extent, this was already present insofar as Compromised Nav Beacons were reported for each version, however this idea now spans everything else which will diverge:
  • System factions and controlling faction
  • Powerplay effects
  • Data update times
With deepest thanks to EDDN and to several utilities which feed it with data, we take full advantage of the recent efforts to update everything such that the specific version is included in broadcasts. The INTRA system uses this to maintain two tables of everything it needs to rank hunting locations for everyone. For utilities supplying data, the remarkably swift deployment of updates gave us a lot of assurance that we can both require and rely on that version information.

For reporting bounty statistics, the INTRA plug-in for EDMC should just continue working as before with no changes. This is because its messages already contained the version information independently of its inclusion via EDDN.

Version switch​

The main header has been made more compact, and provides an extra toggle now:

INTRA 6 header.png

Switching between Elite 4.0 and Elite 3.8 in the top-right will change all system information immediately on any report search and any system look-up page. It also affects which version of the galaxy should be used when ranking the systems it reports, and this will be the case for the next report generated.

To be clear about that, if you generate a report with Elite 4.0 then switch the view to Elite 3.8, your list will contain systems which were chosen and ranked for you based on their 4.0 information, but you will be viewing their 3.8 information. This is indicated by a quite prominent warning:

INTRA 6 version warning.png

It should remember your version setting.

Options adjustment​

The previous dual CNB options for 3.8 and 4.0 have been replaced with a single CNB option:

INTRA 6 arena options.png

This now refers to the CNB status of the version you selected above. Filtering by Powerplay or by Shop factions will do likewise, applying your rules to the version of the galaxy you chose. Again, please note that switching the version after generating a report will display information which was not used for filtering the results and therefore may breach your original specification.

Fixes​

Powerplay systems with Edmund Mahon should now display correctly and should work correctly as a search filter.
 
Update 14 brought a "few" more 3.8–4.0 deviations than anticipated, but INTRA now has solutions for it!

Fixes​

Immediately after the update, INTRA started discarding reports from evacuated/abandoned systems; some were being considered irrelevant to its task, others completely invalid. For example, it would ignore systems reported with zero population without considering that the population has changed to zero. Report admission checks now account for this!

Additionally, star systems are now allowed to have zero population, where previously such systems were excluded from being listed by INTRA at all. There is no plan to remove any systems, and if there were, it would be only if they become completely empty on both 3.8 and 4.0.

Thargoid warnings​

As the primary cause of said problem with reporting and in addition to tracking systems which reach zero factions and population, INTRA now also watches Thargoid activity. Search results will now display this warning; for example, this is a search for Shops close to the Nihal system:

INTRA 7 thargoid warning.png

The systems Imeut, HIP 25679 and Matshiru still have factions present, however it is now clear that they are being attacked by Thargoids, originating in this case from Maelstrom Taranis. We can take a closer look at the Imeut system:

INTRA 7 thargoid attack.png

The system information shows the warning, and similarly for its nearby systems. The invasions also give us a great demonstration of the 3.8–4.0 split, using the Hupang system. By default, its info page uses the 4.0 galaxy:

INTRA 7 Hupang 4.png

With one click to switch INTRA to 3.8:

INTRA 7 Hupang 3.png

Unfortunate for the Brazilian League of Pilots faction. The Maelstrom invasions have almost no effect on typical INTRA search results at the moment, but it will be ready if there is more to come.

Thargoid report​

While it is not a specific goal of INTRA to track Thargoid activity directly for anti-xeno purposes, it does have an activity list for the above purpose, so we decided to make it available. By default, this shows a single list with Maelstrom proximity:

INTRA 7 thargoid report 1.png

This can also be grouped by Maelstrom, including a final group for other systems with Thargoid presence regardless of those invasions:

INTRA 7 thargoid report 2.png

This additional data should update automatically from reports via EDDN, and it can be downloaded from the INTRA Data page.

Thanks​

Until last weekend, all we had available was a loose indication of whether a Commander owns Odyssey conflated with whether 3.8 or 4.0 is being used and is even aware of Odyssey. The introduction of the explicit Elite version into EDDN messages has been of critical importance for INTRA, as has the corresponding support from data contributors such as ED Discovery, ED Market Connector, et alia.

None of us had the appropriate notice about that, so major thanks to all involved with transporting data, and to @Athan in particular for both sides of that process. Thanks also to every Commander who kept their journal utilities updated, continues to do so, or joins the growing club of those submitting data!
 
I found a Arena system, BIBARIDJI, that has 4 shop systems and I don't see this in any search. Any ideas?

It is present, though the result is too poor to compete with better options. Here is a search with Bibaridji as the reference system, 20 Ly limit, and no other specific options:

Bibaridji.png

Interestingly HIP 3551 gets promoted to the top despite having only one faction; this will be because the other three systems only contain planetary ports, a feature which was intended but put on-hold following the changes needed for update 14.

Either way, jumping to four different systems and landing at three planetary ports just to layer 12 factions is a quite poor prospect! There exist Shop pairs which can give you 12 factions from Starports (HIP 12716 and Quechua both for HIP 13841, for example). Widening the search within 50 Ly of Bibaridji drops it to 16th place, and it falls completely out of the report when widened somewhere between 70 and 75 Ly. To be sure, the reference system distance is part of the rank process, but not so much that better nearby results are demoted!
 
Thank you for the reply. If one doesn't mind the planetary landings, this could be a very lucrative spot. I saw this on a post on steam forums and I'm giving it a try. It may take a few cycles till to get my rep up.

Thanks for the great tool!
 
Top Bottom