Breaking open what I had inside my ManagedAddOns, it turned out to be Spara's In-system traders OXP, not Dr Tripsa's offering.
It comprises a script.js (with a populator and other gubbins obscure to this dumb pilot) and an in-system-traderAI.js
Nomenclature:
1) Spara's In-system traders (v.0.3)
His manifest.plist
"identifier" = "oolite.oxp.spara.in-system_traders";
"title" = "In-System Traders";
His BB thread
[Wip] In-system traders 0.3
Comment: This was my first dive into the new priority AI and it rocks
.
Wiki page
I wrote it, so it proves nothing.
I found this in his thread:
A new wip version (0.2) is up. Lots of rewriting and code reorganizing on top of a couple of important changes.
* Oxp is now much more polite when spawning new traders. Ships with custom AIs are either removed or left untouched. If adding ships to station launch queue, ships with custom AIs are left untouched. Elsewhere they are removed right after spawning.
* Probability for an in-system trader to visit a rock hermits (or other similar stations) is greatly lowered. It's still possible, but very rare.
All logging lines are left in for those who want to test this and monitor it's work. See Latest.log.
2) Dr Tripsa's In System Trader
Version: our Expansions Manager has v.1.40 - but our wiki has v.1.5.2 stored on it
here. It was updated in March 2016 after the debut of Oolite v.1.82 in 2015 with its changes in markets.
Manifest.plist
(new) identifier = "oolite.oxp.ocz.InSystemTrader";
(old) identifier = " oolite.oxp.DrTripsa.InSystemTrader";
(new) title = "In System Trader";
His BB thread
[Release] In System Trader OXP 1.40!
Wiki page
In System Trader (written by DrT)