Difference between revisions of "Oolite JavaScript Reference: Oolite"

From Elite Wiki
(gameSettings: this will now be in 1.77.1 as it was needed to fix a bug)
(gameSettings: 1.80 documentation update)
Line 15: Line 15:
 
  procedurallyTexturedPlanets : Boolean
 
  procedurallyTexturedPlanets : Boolean
 
  reducedDetailGraphics : Boolean
 
  reducedDetailGraphics : Boolean
  shaderEffectsLevel : String ("SHADERS_OFF", "SHADERS_SIMPLE", "SHADERS_FULL", or "SHADERS_NOT_SUPPORTED")
+
  detailLevel : String ("DETAIL_LEVEL_MINIMUM", "DETAIL_LEVEL_NORMAL", "DETAIL_LEVEL_SHADERS", or "DETAIL_LEVEL_EXTRAS")
 
  speechOn : Boolean
 
  speechOn : Boolean
 
  wireframeGraphics : Boolean
 
  wireframeGraphics : Boolean
 +
 +
Before 1.80 there was no <code>detailLevel</code> property but there was a <code>shaderEffectsLevel</code> property.
  
 
The gameWindow property contains the following properties:
 
The gameWindow property contains the following properties:

Revision as of 21:43, 20 November 2014

Prototype: Object
Subtypes: none

The Oolite class represents Oolite itself. It allows scripts to access information about the application. There is a global instance of Oolite, named oolite.

Properties

gameSettings

gameSettings : Object(read-only)

This property allows an OXP to detect various game settings. It has the following read-only properties:

autosave : Boolean
gameWindow : Object (see below)
keyConfig : Object (from v1.77.1 onwards, see below)
musicMode : String ("MUSIC_OFF", "MUSIC_ON", or "MUSIC_ITUNES")
procedurallyTexturedPlanets : Boolean
reducedDetailGraphics : Boolean
detailLevel : String ("DETAIL_LEVEL_MINIMUM", "DETAIL_LEVEL_NORMAL", "DETAIL_LEVEL_SHADERS", or "DETAIL_LEVEL_EXTRAS")
speechOn : Boolean
wireframeGraphics : Boolean

Before 1.80 there was no detailLevel property but there was a shaderEffectsLevel property.

The gameWindow property contains the following properties:

height : Number
width : Number
fullScreen : Boolean

The keyConfig property contains numeric (decimal) KeyCode values of all Keyconfig Entry in oolite.app/Resources/Config/keyconfig.plist file. Keyconfig Entry - KeyCode pairs are documented in Oolite_Keyboard_Controls.

You can use the standard Javascript String.fromCharCode() method to convert KeyCode to a string:

var button = String.fromCharCode( oolite.gameSettings.keyConfig.key_ident_system );
player.consoleMessage( "Press " + button + " to turn on the ident system." );

Things like tab, escape, arrow keys, etc. would need to be handled separately.

jsVersion

jsVersion : Number (read-only)

The version of the JavaScript language implemented by this version of Oolite, multiplied by 100, as an integer. For instance, for JavaScript 1.7 (used in Oolite 1.74), this will be equal to 170.

jsVersionString

jsVersionString : String (read-only)

The version of the JavaScript language implemented by this version of Oolite, as a string. For instance, for JavaScript 1.7, this will be equal to "1.7".

version

version : Array (read-only)

The version of Oolite, as an array of version components. For instance, for Oolite 1.74 this is [1, 74]. For version 1.73.4, it is [1, 73, 4].

versionString

versionString : String (read-only)

The version of Oolite, as a string. For instance, for Oolite 1.74 this is "1.74". For version 1.73.4, it is "1.73.4".


Methods

compareVersion

function compareVersion(versionSpec) : Number

Compare the version of Oolite to versionSpec, which may be either a string or an array (in the format given by version). If the current version of Oolite is less than versionSpec, 1 is returned. If the current version of Oolite is greater than versionSpec, -1 is returned. If they are equal, 0 is returned. Example:

if (0 < oolite.compareVersion("1.80"))
{
    // Oolite version is older than 1.80.
    log(this.name, "An old version of Oolite (" + oolite.versionString + ") is in use. Some features of SuperDuperOXP will not be available.")
}
else
{
    // Enable advanced features here.
}