Oolite Bulletins

missionScreenOpportunity wrote:

The missionScreenOpportunity handler is called if there are no mission / report screens active, and the player is docked to a station. It gets fired at game startup, upon docking, and after a docking report or previous mission screen has ended.

Lone_Wolf wrote:

These checks could be done in a missionScreenOpportunity handler, but is it needed to avoid clashes ?

if(!player.ship || !player.ship.isValid || !player.ship.docked) return;
switch(guiScreen){
	case "GUI_SCREEN_OPTIONS":
		set activation
		if !Timer
			new Timer calling this.guiScreenChanged
		break;
	case "GUI_SCREEN_SYSTEM_DATA":
		if activation
			start handling
		- no break here!!!
	default:
		delete activation
		if Timer
			stop Timer
			delete Timer
}

Wildeblood wrote:

How late in the witchspace countdown can you set a scripted mis-jump.

Wildeblood wrote:

how to record how far I've just jumped?

1. How can I get my script to see all ships currently defined by the game? That's ship type, like "[ferdelance]", not spawned instance, so I can have a menu of things from which to select for creative spawning.
2. What's the cleanest way of maintaining "global" state? Specifically, I want to record a running score for a couple of ship groups, and I'd like any ship to be able to signal back to the world script when something's happened that should cause the score to update. I can define callbacks in the world script, but not global state (it seems), because "this._score" resolves to the caller's "_score" variable, not the world script's. I don't need to save "_score" between games, so where should it go? In the Player entity?

jh145 wrote:

How can I get my script to see all ships currently defined by the game? That's ship type, like "[ferdelance]", not spawned instance, so I can have a menu of things from which to select for creative spawning.

spara wrote:

Does adding ships with addGroup rather than addShips affect their AI behaviour?

cim wrote:

A useful trick to avoid having to mess around with 'this':

Code: Select all

this.name = "My world script";
var self = this;

Svengali wrote:

This ends in the global scope. Better avoid it.

this.name = "My world script";

(function() { // this line starts an anonymous function scope to get things out of global space

var self = this;

this.startUp = function() {
  this._score = 0;
}

this._myCallbackFunction = function() {
  // ...
  self._score += 1;
}

}.call(this)); // and this line closes that scope and executes the function to define the variables

cim wrote:

spara wrote:

Does adding ships with addGroup rather than addShips affect their AI behaviour?

Yes - grouped ships will receive messages from ship.requestHelpFromGroup() and ship.notifyGroupOfWormhole(), and be counted as allied for determining combat odds and ignoring friendly fire. There are other effects in a lot of AIs where ships will coordinate actions through their group leader.

Though you can add them with addShips and group them up separately for the same effect - it's being in the same group, not how they got into it, which makes the difference.