Oolite Bulletins

Ahruman wrote:

It seems to me that it could be beneficial for the extra hermit to be added after shipWillExitWitchspace, so that it doesn’t need to happen if OXPs have already added secondary (immobile) stations.

cim wrote:

Switeck wrote:

I would just remove unwanted ships (in this case a Rock Hermit and associated nearby asteroids) myself...but I get occasional crashes-to-desktop when .js scripts move (or remove) ships while my ship is cloaked.

But only while cloaked, and not when ships are (re)moved by non-JS means?

Switeck wrote:

There are also graphical glitches associated with moving and/or removing "unwanted" ships on arriving at a new system. Normally, this is unseen...but it can be particularly jarring in the case of Thargoids in interstellar space, as these are both semi-large and often immediately in front of the player's ship when this happens

shipWillExitWitchspace occurs before anything is actually drawn for the new system, though, so any changes made there shouldn't be visible to the player. And then the next several frames are the break pattern.

this.scriptedAI = function(delta) 
{
    // delta = duration of frame. Often irrelevant unless you're doing
    // ultra-high-precision turns, or want a manouevre to last a particular
    // length of time

    // calculations happen here
    return flightParameters;  
}

• stickRoll: number between -ship.maxRoll and ship.maxRoll
• stickPitch: similarly for pitch
• stickYaw: and for yaw
• desiredSpeed: number at least 0. If this is above ship.maxSpeed, and the ship has usable injectors, it will use them.
• chosenWeapon: "FORWARD", "AFT", "PORT" or "STARBOARD"

this.scriptedAI = function(delta) 
{
  return { stickPitch: -0.2;
           desiredSpeed: this.ship.maxSpeed;
           chosenWeapon: "PORT"; };
}

cim wrote:

[*]chosenWeapon: "FORWARD", "AFT", "PORT" or "STARBOARD"[/list]
The ship will then respond to the virtual joystick. If a large change is requested - say the ship is in level flight, and the virtual joystick is moved to maximum clockwise roll - then it will take some time for the ship to respond and accelerate to that roll rate: quite possibly more than one frame.

If the attack version of the AI is selected, and the ship's current target is in the sights of the selected weapon (and there is a weapon there, and it's ready to fire, etc.), the weapon will be fired.

For example:

Code: Select all

this.scriptedAI = function(delta) 
{
  return { stickPitch: -0.2;
           desiredSpeed: this.ship.maxSpeed;
           chosenWeapon: "PORT"; };
}

will make the ship perform a fairly wide loop, and in attack mode, firing its port laser if the target crosses its sights.

Smivs wrote:

So NPCs can have and use side lasers?

cim wrote:

This OXP adds a number of police ships to planetary orbit in the safer systems, and then uses a scripted AI to make them actually orbit the planet.

Smivs wrote:

Missed that earlier.

cim wrote:

A new feature for trunk: scriptable flight AI.

cim wrote:

• desiredSpeed: number at least 0. If this is above ship.maxSpeed, and the ship has usable injectors, it will use them.

Commander McLane wrote:

This can of course be done with desiredSpeed: this.ship.maxSpeed * speedFactor, but since the traditional AI programming allows both setSpeedTo: and setSpeedFactorTo:, it might be more easily accessible to have two different methods in the scriptedAI as well.

CommonSenseOTB wrote:

1)currentWeapon working to query the npc's currently selected or used laser, if that's even possible. The currently chosenWeapon?

CommonSenseOTB wrote:

2)weapon positions exposed to javascript as a read property for at least the player ship.

CommonSenseOTB wrote:

3)thrust as a writeable property for the player ship(already writeable for the npc's)