For information and discussion about Oolite.
https://bb.oolite.space/
I don't think it is exposed to Javascript, however if you look at theWildeblood wrote:How do I check within a script whether any particular commodity is on the illegal goods list? Currently I have firearms, slaves and narcotics hard-coded in Trading Assistant, but like most things in Oolite the illegal goods list is easily re-configured.
![[EliteWiki]](/images/elitewikismall.png){kind=small}
Illegal Goods Tweak OXP, specifically illegal_goods_tweak.js in the Scripts directory, you will get an idea as to how you could handle it.Code: Select all
this.playerAttackedOther = function(other)
{
// Your code here
}Code: Select all
this.playerFiredMissile = function(missile, target)
{
// Your code here
}Tricky wrote:Really difficult to work out if the player is actively in combat without these.
Code: Select all
if (player.alertHostiles)shipAttackedOther in the worldScript only triggers on NPC's attacking players. I've tried that method.Wildeblood wrote:shipAttackedOther will work in a worldScript, the wiki is confused/confusing in the way it lists playerShip events, some on the worldScripts page, some on the ship scripts page. See also:-
https://bb.oolite.space/viewtopic.php?f=3&t=12491
Tricky wrote:Really difficult to work out if the player is actively in combat without these.One of the few player, not playerShip, properties.Code: Select all
if (player.alertHostiles)
It worked for my death ray. Too well, in fact. I suspect you're thinking of shipBeingAttacked.Tricky wrote:shipAttackedOther in the worldScript only triggers on NPC's attacking players. I've tried that method.Wildeblood wrote:shipAttackedOther ... See also:-
https://bb.oolite.space/viewtopic.php?f=3&t=12491
It should be easy to copy theTricky wrote:Any chance of these 2 world script events?
Similar to shipAttackedOther and shipFiredMissile ship events.
Really difficult to work out if the player is actively in combat without these.
shipAttackedOther and shipFiredMissile ship events into the shipscript of the player. In that case they only will fire for the player 
Code: Select all
player.ship.script.shipAttackedOther = ......Ah yes. I stand corrected.Wildeblood wrote:It worked for my death ray. Too well, in fact. I suspect you're thinking of shipBeingAttacked.Tricky wrote:shipAttackedOther in the worldScript only triggers on NPC's attacking players. I've tried that method.Wildeblood wrote:shipAttackedOther ... See also:-
https://bb.oolite.space/viewtopic.php?f=3&t=12491
Code: Select all
AGGRESSOR_SWITCHED_TARGET id1 id2It's quite useful (and needed) for what it does, but it's not meant to trigger the AI. Think of it as an internal AI message. You cannot use it meaningfully, because the two ID numbers are part of the message, and there is no way in the world to foresee which unique IDs will be involved when the message is sent.Tricky wrote:There is a really un-helpful helpful AI message...You can't even get the AI to trigger on it.Code: Select all
AGGRESSOR_SWITCHED_TARGET id1 id2
The only way I can think of checking for that is setting up a frame call-back and check the AI message state of the NPC.
Manifest-object.This isn't necessarily a bad thing, though. As far as I understand, the AITradingAssistant is specifically written for the default price ranges in main stations. Thus, it cannot be expected to be compatible with OXPs that change the default price ranges in main stations. I am not aware of any OXP that changes this default, anyway.Rocketman wrote:For example, AITradingAssistant OXP uses manually written prices. This makes it potentially incompatible with any other XPs wich modify commodities.
Most (but not all) of the properties in shipdata.plist and planetinfo.plist can be accessed by scripts. Most of the rest of the configuration is hidden. That's just the way it is.Rocketman wrote:Hello! Is there possibility to access basic game propetries initialized in config .plist files (such as commodities.plist, for instance) by extention pack JS scripts? I walked trough Oolite JavaScript Reference but didn't find solution.
For example, AITradingAssistant OXP uses manually written prices. This makes it potentially incompatible with any other XPs wich modify commodities. I'am pretty sure that there may be a lot of other similar examples.
Isn't that good reason to make such global properties lists reachable by scripts? Or that is already done and I simply didn't find it in manuals?
P.S. english is not my native language, so I'am sorry for any incovenience caused...
