Oolite JavaScript Reference: Ship

Prototype: Entity
Subtypes: Station, PlayerShip

This class was added in Oolite test release 1.70.

The Ship class is an Entity representing a ship, station, missile, cargo pod or other flying item – anything that can be specified in shipdata.plist. A Ship has all the properties and methods of a Entity, and several others.

Stations and the Player are types of ship. Note that these more specific types have additional properties and methods.

Properties

aftWeapon

This property was added in Oolite test release 1.74.

aftWeapon : EquipmentType(read-only)

The currently equipped aft weapon, or null. Identical to the equivalent PlayerShip property.

See also: forwardWeapon

AI

AI : String (read-only)

The name of the ship’s current AI. (See also: AIState, setAI(), switchAI(), exitAI())

AIState

AIState : String (read/write, read-only for player)

The ship’s AI’s current state. (See also: AI, reactToAIMessage(), hasSuspendedAI)

availableCargoSpace (deprecated)

This property was added in Oolite test release 1.72.

availableCargoSpace: Number (read-only integer)

The ship’s free cargo space, in tons. Deprecated in favour of cargoSpaceAvailable.

beaconCode

beaconCode : String (read-only)

If the ship is a beacon, an identifying string. The first character is used for identification on the Advanced Space Compass. For non-beacons, this property is null. (See also: isBeacon)

bounty

bounty : Number (read/write integer)

The bounty on the ship. In the case of the player, it is halved at each witchspace jump.
It is actually the legal status of the ship that is shown here and not the bounty. For all ships both are the same but for anything with scan class Thargoid the legal status is only based on the ships mass and has no relation to its defined bounty.

cargoCapacity (deprecated)

cargoCapacity: Number (read-only integer)

The ship’s cargo capacity, in tons. Name introduced with version 1.72. Old name was maxCargo. Deprecated in favour of cargoSpaceCapacity

cargoSpaceAvailable

This property was added in Oolite test release 1.74.

cargoSpaceAvailable : Number (read-only integer)

The ship’s available cargo space, in tons. Name introduced with version 1.74. Replaces availableCargoSpace.

cargoSpaceCapacity

This property was added in Oolite test release 1.74.

cargoSpaceCapacity : Number (read-only integer)

The ship’s cargo capacity, in tons. Name introduced with version 1.74. Old names were maxCargo, cargoCapacity.

cargoSpaceUsed

This property was added in Oolite test release 1.72.

cargoSpaceUsed : Number (read-only integer)

The ship’s current cargo, in tons. Any ship carrying less than

contracts

This property was added in Oolite test release 1.74.

contracts : Array (read-only NSDictionary)

The ship’s contracts. (For now only available for the player). Each contract contains the entries: commodity: string, quantity: integer, description: string, start: integer, destination: integer, startName: string, destinationName: string, eta: integer, etaDescription: string, fee: Integer, premium: Integer

For example, the information of the first contract can be obtained by:

player.ship.contracts[0].commodity
player.ship.contracts[0].quantity
player.ship.contracts[0].description
player.ship.contracts[0].start
player.ship.contracts[0].destination
player.ship.contracts[0].startName
player.ship.contracts[0].destinationName
player.ship.contracts[0].eta  // Estimated Time of Arrival.
player.ship.contracts[0].etaDescription
player.ship.contracts[0].fee      // The profit of the contract, paid out on successful delivery.
player.ship.contracts[0].premium  // The sum paid to obtain the goods and paid back on successful delivery.

start and destination contain system ID numbers for planets in the current galaxy chart, eta is in clock seconds, fee is the amount that the player will receive when delivering this contract, and premium was the amount the player had to pay to secure this contract.

desiredSpeed

This property was added in Oolite test release 1.72.

desiredSpeed : Number (read/write nonnegative, read-only for player)

The speed the AI will attempt to maintain. The AI core and AI script may change this from time to time. The corresponding AI method is setSpeedFactorTo:; a speed factor of 1.0 corresponds to a desiredSpeed equal to maxSpeed.

displayName

displayName : String (read/write, read-only for player)

The name of the ship as seen by the player. By default it is the same as name(name key in shipdata.plist). This property is changed from shipDisplayName in 1.72

entityPersonality

entityPersonality : Number (read-only integer)

A random number in the range 0..32767 which is generated when the ship is created. Equivalent to the entityPersonalityInt uniform binding.

equipment

This property was added in Oolite test release 1.74.

equipment : Array of EquipmentInfo  (read-only)

The equipment a ship is carrying.

escorts

escorts : Array (read-only array of Entitys)

The ship’s deployed escorts.

escortGroup

This property was added in Oolite test release 1.73.

escortGroup : ShipGroup (Class added with Oolite 1.73)

The ship’s deployed escorts.

forwardWeapon

This property was added in Oolite test release 1.74.

forwardWeapon : EquipmentType(read-only)

Identical to the equivalent PlayerShip property.

See also: aftWeapon

fuel

fuel : Number (read/write)

The ship’s current fuel capacity, in LY. The game will limit this to the range 0..7, and round it off to the nearest tenth. (See also: Player.fuelLeakRate)

group

This property was added in Oolite test release 1.73.

group : ShipGroup  (Class added with Oolite 1.73)

Contains ship’s belonging to each other. Added pirate groups are an example or a station with its launched defenders.
A group is an individual object that can be linked to several ships belonging to the same group. When a ship dies and the group object has still owners, the group stays active as object. The group is only removed from memory after the last ship that had this group as property is removed.
Adding a group to a ship does not automatic puts that ship in the group. For that to happen you need also use the addShip() command. e.g.

this.ship.group = new ShipGroup();
this.ship.group.addShip(this.ship);

groupID

Removed in 1.73. Use group instead.

hasHostileTarget

hasHostileTarget : Boolean (read-only)

true if the ship’s AI is trying to kill something, false otherwise. Always false for the player.

hasSuspendedAI

hasSuspendedAI : Boolean (read-only)

true if the ship has suspended AIs, false otherwise.

heatInsulation

heatInsulation : Number (read/write)

The ship’s heat insulation factor. 1.0 is normal, higher values mean more resistance to heat.

isBeacon

isBeacon : Boolean (read-only)

true if the ship is a beacon (i.e., can show up on the Advanced Space Compass with a character indicating its identity), false otherwise. (See also: beaconCode)

isCloaked

isCloaked : Boolean (read-only)

true if the ship has a cloaking device which is currently active false otherwise. If the ship has a cloaking device and sufficient energy to use it, you can activate it by setting isCloaked to true.

isFrangible

isFrangible : Boolean (read-only)

true if the ship is frangible (i.e., its subentities can be destroyed separately from the main ship), false otherwise. (See also: subEntities)

isJamming

isJamming : Boolean (read-only)

true if the ship has a military scanner jammer which is currently active false otherwise.

isMine

This property was added in Oolite test release 1.73.

isMine : Boolean (read-only)

true if the ship is a mine, false otherwise.

isMissile

This property was added in Oolite test release 1.73.

isMissile : Boolean (read-only)

true if the ship is a missile, false otherwise.

isPirate

isPirate : Boolean (read-only)

true if the ship is a pirate vessel, false otherwise. Currently equivalent to primaryRole == "pirate".

isPirateVictim

isPirateVictim : Boolean (read-only)

true if the ship’s primary role is listed in pirate-victim-roles.plist, false otherwise. This is the same test used by the pirate AI to select victims.

isPolice

isPolice : Boolean (read-only)

true if the ship is a police vessel, false otherwise. Currently equivalent to scanClass == "CLASS_POLICE".

isThargoid

isThargoid : Boolean (read-only)

true if the ship is a Thargoid vessel, false otherwise. Currently equivalent to scanClass == "CLASS_THARGOID".

isTrader

isTrader : Boolean (read-only)

true if the ship is a merchant vessel, false otherwise. Currently equivalent to primaryRole == "trader" || isPlayer. Note: isPirateVictim may be a better choice in many cases.

isWeapon

This property was added in Oolite test release 1.73.

isWeapon : Boolean (read-only)

true if the ship is a weapon, false otherwise. Currently equivalent to isMissile || isMine , but new categories of weapon could be added in future.

lightsActive

This property was added in Oolite test release 1.74.

lightsActive : Boolean (read-write)

Setting this property to true turns on all the entity’s flashers, and setting it to false turns them off. Setting it sets the lightsActive property for all subentities, but subentities’ setting can also be manipulated separately. In addition to affecting flashers, the value can be used by shaders.

Note: lightsActive is always true when a ship is spawned, although individual flashers may be off because they have initially_on set to false in their shipdata.plist declarations.

maxCargo

maxCargo : Number (read-only integer)

The ship’s cargo capacity. This property is renamed to cargoCapacity in 1.72.

maxSpeed

maxSpeed : Number (read-only)

The ship’s maximum speed under normal power. Note that speed may exceed this when witch fuel injectors or hyperspeed are in use. (See also: speed)

maxThrust

This property was added in Oolite test release 1.74.

maxThrust : Number (read-only)

The ship’s maxThrust. This value is the one defined as thrust in shipdata.plist.

missileCapacity

This property was added in Oolite test release 1.74.

missileCapacity : Number (read-only integer)

The ship’s maximum number of missiles it can carry.

missiles

This property was added in Oolite test release 1.74.

missiles : Array (read-only array of EquipmentInfo's)

The ship’s loaded missiles.

name

name : String (read/write, read-only for player)

The name of the ship type (name key in shipdata.plist). This property was changed from shipDescription in 1.72

passengerCapacity

This property was added in Oolite test release 1.72.

passengerCapacity : Number (read-only integer)

The ship’s maximum passenger capacity.

passengerCount

This property was added in Oolite test release 1.72.

passengerCount : Number (read-only integer)

The ship’s current number of passengers.

passengers

This property was added in Oolite test release 1.74.

passengers : Array (read-only NSDictionary)

The ship’s passengers. (For now only available for the player). Each passengers list contains the entries: name: String, start: integer, destination: integer, startName: string, destinationName: string, eta: integer, etaDescription: string, fee: Integer, premium: Integer
For example, the information of the first contract can be obtained by:

player.ship.passengers[0].name
player.ship.passengers[0].start
player.ship.passengers[0].destination
player.ship.passengers[0].startName
player.ship.passengers[0].destinationName
player.ship.passengers[0].eta
player.ship.passengers[0].etaDescription
player.ship.passengers[0].fee  // The final fee, paid out on successful delivery.
player.ship.passengers[0].premium  // The advance fee, already paid on acceptance of the contract.

start and destination contain system ID numbers for planets in the current galaxy chart, eta is in clock seconds, fee is the amount that the player will receive when delivering this passenger, and premium shows the amount the player received when the passenger boarded the ship.

potentialCollider

potentialCollider : Entity (read-only)

The entity the ship is currently trying not to crash into, if any.

primaryRole

primaryRole : String (read/write, read-only for player)

The main role of the ship; the role for which it was created. For instance, if a ship’s shipdata.plist entry specifies the roles “pirate trader(0.5) escort”, and a ship of that type is spawned to be a trader, its primaryRole is "trader", its roles is ["escort", "pirate", "trader"] and its roleProbabilities is { "escort":1, "pirate":1, "trader":0.5}.

See also: roles, roleProbabilities.

reportAIMessages

reportAIMessages : Boolean (read/write)

Debugging facility: set to true to dump information about AI activity to the log.

roleProbabilities

roles : Object (read-only)

The probabilities for each role in roles. Example:

this.pirateProb = ship.roleProbabilities["pirate"]

See also: primaryRole, roles.

roles

roles : Array (read-only array of Strings)

The roles of the ship. This consists of the roles specified in the ship’s shipdata.plist entry, as well as the primaryRole if it is not among those.

See also: primaryRole, roleProbabilities, hasRole().

savedCoordinates

This property was added in Oolite test release 1.74.

savedCoordinates : Vector (read-write)

The savedCoordinates of the ship in system co-ordinates. The savedCoordinates vector is only used by AI scripting to store a coordinate that can be used by other AI commands like setDestinationToCoordinates. It are the same coordinates that are set by the AI command: "setCoordinates: X Y Z"

scannerRange

scannerRange : Number (read-only)

The range of the ship’s scanner.

script

script : Script (read-only)

The ship’s script.

scriptInfo

scriptInfo : Object (read-only)

The contents of the script_info key in the ship’s shipdata.plist entry, if any. This may be any property list object, but the reccomended approach is to use a dictionary whose keys have a unique prefix (such as you should be using for file names, ship names etc.). A property list dictionary is converted to a JavaScript object with properties corresponding to the dictionary’s keys. All other property list types used with Oolite have directly corresponding JavaScript types.

shipDescription

shipDescription : String (read/write, read-only for player)

The name of the ship type (name key in shipdata.plist). This property is changed into name in 1.72

shipDisplayName

shipDisplayName : String (read/write, read-only for player)

The name of the ship as seen by the player. By default it is the same as shipDescription(name key in shipdata.plist). This property is changed into displayName in 1.72

speed

speed : Number (read-only)

The ship’s current speed. (See also: maxSpeed)

subEntities

subEntities : Array (read-only array of Ships)

The ships subentities, or null if it has none. Special subentities such as flashers and exhaust plumes are not included. (See also: isFrangible)

target

target : Ship (read-write)

The ship’s primary target, i.e. the entity it will attempt to shoot at. This value is automatically co-ordinated between a ship and its subentities.
Starting with 1.74 a current target can be deselected by setting "target = null". (Before defining null resulted in an error)

temperature

temperature : Number (read/write)

The ship’s temperature, normalized such that a temperature of 1.0 is the level at which a ship starts taking heat damage.

thrust

This property was added in Oolite test release 1.74.

thrust : Number (read/write (For player read-only))

The ship’s thrust. This value is maximised by maxThrust. This value determines how fast the ship accelerates or decelerates. Speed-change in m/ses per sec.

weaponRange

weaponRange : Number (read/write)

The maximum range of the ship’s primary weapon. For the player it is the range of the weapon that fired as last, even when the view direction changed.

withinStationAegis

withinStationAegis : Boolean (read-only)

true if the ship is within the aegis of the system’s main station (i.e., no more than 51 200 game metres from the station, or twice scanner range).

Methods

abandonShip

This method was added in Oolite test release 1.74.

function abandonShip() : Boolean

Returns true when the ship has an escapepod. It will launch all escapeposd on board leaving the ship behind as a empty hulk. (scanClass = CLASS_CARGO). This command does nothing when no escape-pod is present.
Pressence of an escapepod can be tested with: hasEquipment("EQ_ESCAPE_POD")

awardContract

This method was added in Oolite test release 1.74.

function awardContract(quantity: Integer, commodity: String, start: Integer, destination: Integer, eta: Integer, fee: Integer) : Boolean

Adds a contract to the ship. (Currently only for the player). eta is in seconds and must be greater than the current time. start and destination are the ID numbers of the system.
It returns false when there is no room for the cargo or the eta is chosen wrong or there is not enough money to accept the contracts. e.g.

player.ship.awardContract(12, "Food", 34, 67, clock.seconds+7*24*3600, 5000)

If successful - and in galaxy chart 1 - the player will have 12 more food containers on board, the manifest will show that the cargo was picked up at Inus, to be delivered at Cemave, within exactly 7 days from now, and the player will be given 5000 credits if the cargo is delivered on time (early or late delivery will affect the amount paid). N.B. Normally to get a contract, the player will have to buy the cargo at the local market price. Using this method, no inital payment is made.

awardEquipment

This method was added in Oolite test release 1.74.

function awardEquipment(equipmentKey : String)

Adds the given piece of equipment to the ship. Example: ship.awardEquipment("EQ_ECM") (before 1.74 this command was only available for the player's ship)

awardPassenger

This method was added in Oolite test release 1.74.

function awardPassenger(name: String, start: Integer, destination: Integer, eta: Integer, fee: Integer) : Boolean

Adds a contract to the ship. (Currently only for the player). eta is in seconds and must be greater than the current time. start and destination are the ID numbers of the system.
It returns false when there is no room for the passenger or the eta is chosen wrong. e.g.

 player.ship.awardPassenger("cmdr Jameson", 34, 67, clock.seconds+3*24*3600, 1500)

If successful - and in galaxy chart 1 - the player will have cmdr Jameson as a passenger, his documents will show that he boarded the ship at Inus, to go to Cemave, within exactly 3 days from now, and the player will be given 1500 credits if he gets there on time (early or late arrival will affect the amount paid). N.B. Normally a passenger will pay the captain a small advance upon boarding. Using this method, no inital payment is made.

commsMessage

This method was added in Oolite test release 1.72.

function commsMessage(message : String) : Ship

Make the ship type entity broadcast the specified message. Works on buoys and subentities as well as normal ships and stations.

deployEscorts

function deployEscorts()

Launch the ship’s escorts, if any.

dockEscorts

function dockEscorts()

Dock the ship’s deployed escorts, if any.

dumpCargo

This method was added in Oolite test release 1.71.

function dumpCargo() : Ship

Ejects one item of cargo from the ship, and returns the cargo item. Returns null if the ship has no cargo, anything has been ejected in the last 0.5 seconds, or if sent to the player while docked.

See Also: dumpCargo, ejectSpecificItem

ejectItem

This method was added in Oolite test release 1.71.

function ejectItem(role : String) : Ship

Spawns a ship of role role immediately behind the ship, with a slight backwards velocity. (Note: an equal and opposite reaction is applied to the parent ship, so doing this with large ships is rarely useful. player.ejectItem("station") may seem funny, but don’t come running to me if you have someone’s eye out.) Returns the generated ship, or null if no ship is generated. The scanClass of the ejected item will always be CLASS_CARGO.

See Also: dumpCargo, ejectSpecificItem

ejectSpecificItem

This method was added in Oolite test release 1.71.

function ejectSpecificItem(itemKey : String) : Ship

Spawns a ship with the shipdata.plist key itemKey immediately behind the ship, with a slight backwards velocity. The scanClass of the ejected item will always be CLASS_CARGO.

See Also: dumpCargo, ejectItem

equipmentStatus

This method was added in Oolite test release 1.74.

function equipmentStatus(equipmentKey : String) : String

Tests whether the specified type of equipment is installed, and whether it is functioning. Returns one of the following strings: "EQUIPMENT_OK", "EQUIPMENT_DAMAGED", "EQUIPMENT_UNAVAILABLE". (was before 1.74 only available to the player)

See also: setEquipmentStatus()

explode

function explode()

Like it says. Works on otherwise-indestructible main station, and everything else too.

exitAI

function exitAI()

Exit the current AI, restoring the previous one. Equivalent to the exitAI: AI method. May not be used on player. Will generate a warning if there are no suspended AI states.

See Also: AI, setAI(), hasSuspendedAI

fireECM

This method was added in Oolite test release 1.73.

function fireECM()

activates an ecm burst, identical as the AI command.

fireMissile

This method was added in Oolite test release 1.74.

function fireMissile([missile]) : Ship

fireMissile() will try and fire the first available missile and will return the missile fired, or null if no missiles can be fired at this time. It can take the optional missile identifier parameter, to allow for a specific missile to be fired. Missiles cannot be fired if the NPC ship hasn't got a valid target, or if the previous missile was launched less than missile_load_time seconds before. If a missile type was specified, and not found on the ship, no missile will be fired.

hasEquipment

This method was added in Oolite test release 1.73.

function hasEquipment(equipmentKey : String [, includeWeapons : Boolean]) : Boolean

Returns true if the given piece of equipment is present on/in the ship, false if it is not. If includeWeapons is false, primary weapons (lasers) and secondary weapons (missiles and mines) are excluded. If includeWeapons is not specified, true is assumed.

Prior to Oolite 1.73, hasEquipment() is only available for the player’s ship and includeWeapons is ignored (treated as always false).

Example: if (player.hasEquipment("EQ_TRUMBLE")) log("Oh noes, I has a trumble!")

hasRole

function hasRole(role : String)

Returns true if the ship has role among its roles, false otherwise.

See Also: roles

reactToAIMessage

function reactToAIMessage(AIState : String)

Immediately execute the ship’s AI in the specified state.

remove

This method was added in Oolite test release 1.72.

function remove()

Like it says. Works on otherwise-indestructible main station, and everything else too. Same as explode except for the explosion itself

removeEquipment

This method was added in Oolite test release 1.74.

function removeEquipment(equipmentKey : String)

Removes the given piece of equipment from the ship. Example: ship.removeEquipment("EQ_ECM"). (before 1.74 this command was only available to the player) This function can also be used to remove missiles (and mines). If more than one missile of the same type is found on board, only one of them will be removed.

selectNewMissile

This method was added in Oolite test release 1.74.

function selectNewMissile() : equipmentKey

selectNewMissile() will automatically select a missile for a specific ship. It uses the missile_role shipdata.plist key to find out which missiles to select. As with the system populator, there's a small chance that missiles other than the missile_role specified in shipdata will be selected. e.g.

this.ship.awardEquipment(this.ship.selectNewMissile())

will automatically add the 'right type' of missile to a ship, i.e. one that its captain would normally choose.

setAI

function setAI(AIName : String)

Set the current AI, leaving the old one suspended. Equivalent to the setAITo: AI method. May not be used on player.

See Also: AI, switchAI(), exitAI()

setEquipmentStatus

This method was added in Oolite test release 1.74.

function setEquipmentStatus(equipmentKey : String, statusKey : String)

Changes the status of the given piece of equipment from the ship. The two only valid status keys are "EQUIPMENT_OK", "EQUIPMENT_DAMAGED". (was before 1.74 only available to the player)

See also: equipmentStatus()

setScript

This method was added in Oolite test release 1.71.

function setScript(scriptName : String)

Set, or completely replace, the javascript code associated to a ship entity.

spawn

This method was added in Oolite test release 1.71.

function spawn(role : String [, count : Number]) : Array

Attempts to create count (maximum: 64) ships of role role close to the ship – specifically, inside the ship’s collision radius. (Since creating ships may fail, the number created may be less than count). The created ships are returned in an array. If count is not specified, one will be assumed.

spawn() is intended for cases when a ship splits into multiple parts or drops parts. In particular, it has the following special behaviour:

• The spawned ships inherit most of the temperature of the parent.
• If the parent is a missile and a child has the is_submunition property, the child will be considered a missile, its target will be set to that of the parent and the child’s owner will be set to the parent.
• spawn() does not set up escorts for the new ships, or generate witchspace effects, or do any special AI handling.

spawnOne

This method was added in Oolite test release 1.71.

function spawnOne(role : String) : Ship

Convenience method which calls spawn(role) and returns the first element of the resulting array, or null if spawn() fails.

switchAI

function switchAI(AIName : String)

Set the current AI, exiting the old one. Equivalent to the switchAITo: AI method. May not be used on player.

See Also: AI, setAI(), exitAI()