Oolite Bulletins

• It only supports selectors that are used in the script I was testing on. Fixing this is mostly drudgery, not very complicated.
• It only supports selectors that have JavaScript equivalents (call() doesn’t count).
• It doesn’t support all of the syntax of the legacy script engine. In particular, it would break on a condition with more than two spaces in it, like something_string equal two words.
• In its current state, it would do the wrong thing for non-player ship scripts.
• The legacy scripting engine’s text expansion thing is pretty wacky. In particular, it rewrites all of every statement except the leftmost word before execution. When text expansion is used in a sane way, the translator can handle it – for instance, foo [local_a] bar %R [local_b] baz translates to "foo " + this.local_a + expandDescription(" bar %R ") + this.local_b + " baz". What it can’t deal with is variables being used to specify multiple parameters at once:

  Code: Select all

  ("set: local_thing foo 1", "addShips: my_[local_thing]")
  // Equivalent to:
  ("addShips: my_foo 1")

  I’d consider that pretty bad style, but if anyone is actually doing it I’d like to know. :-)
• There’s room for optimization, in particular turning STATUS_EXITING_WITCHSPACE, STATUS_LAUNCHING and STATUS_DOCKING conditions into event handlers, and adding separate tickleDocked and tickleInFlight handlers for STATUS_DOCKED/STATUS_IN_FLIGHT conditions. Manually rewriting scripts to use appropriate event handlers will always be better, though.

• Added JS player.rank.
• Added player.legalStatus (Clean/Offender/Fugitive, equivalent to legacy commanderLegalStatus_string; legalStatus_number is player.bounty).
• Renamed Ship.shipDescription to Ship.name. (This no longer conflicts with player.name because of the player/player.ship split.)
• Renamed Ship.shipDisplayName to Ship.displayName.
• system.countShipsWithRole() now takes optional relativeTo and range arguments, like the other search methods.
• Added system.countShipsWithPrimaryRole() for a pleasing symmetry.
• Added system.pseudoRandomNumber (per-system number, less than 1; precision is 24 bits), system.pseudoRandom100 (per-system integer, less than 100 – the same as legacy pseudoFixedD100_number) and system.pseudoRandom256 (per-system integer, less than 256 – the same as legacy pseudoFixedD256_number).
  Note: The legacy versions reset the PRNG used to generate various other numbers, and pseudoRandom100/pseudoRandom256 preserve this behaviour; pseudoRandomNumber does not.

Ahruman wrote:

• :tnearest role – sets the player’s target to the closest ship with the specified role. Example. :tnearest coriolis
• :find expression – sets result to an array of entities matching expression, which is a predicate using the variable entity. For example, to find all planets, use: :find entity.isPlanet
• :findS expression – similar to :find, but only looks for ships. Example: :findS ship.scanClass == "CLASS_BUOY"
• :target expression – like :findS, but sets the player’s target to the closest found object.

• Oolite 1.65
• Oolite 1.70
• Assassins 1.3
• Asteroid Storm 3.46
• Ionics 1.2.1

LittleBear wrote:

...ten handed Internet Brothel case...

Star Gazer wrote:

... my mispent youth of 5 people in the same bed...

• randomFloat (a random number is generated when the ship is spawned, like the entityPersonality binding, but you can have as many as you want).
• randomUnitVector (a vec3 of length 1, in a random direction, equivalent to JavaScript Vector.randomDirection())
• randomVectorSpacial (a random vec3 with the same distribution as Vector.random())
• randomVectorRadial (a random vec3 with the same distribution as Vector.randomDirectionAndLength())
• randomQuaternion (a random unit quaternion, as a mat4x4, or vec4 if asMatrix is set to no)

uniforms =
{
    uRandomFive =
    {
        type = "randomUnitVector";
        scale = 5.0;
    }
}

uniforms =
{
    uVector = (1, 2, 3);
    // Equivalent that works in 1.71:
    uVector2 =
    {
        type = "vector";  // "vec3" also works
        value = (1, 2, 3);
    }
}

another_commander wrote:

I am generally a fan of programs that contain themeselves in their own little space and don't spread files all over the place.

HOMEPATH=%APPDATA%\Oolite