Oolite Bulletins

Wildeblood wrote:

Then you will have also found the shipdata-overrides file.

Diziet Sma wrote:

Wildeblood wrote:

Then you will have also found the shipdata-overrides file.

Yup.. but whom.displayName does the same thing without a whole lot of mucking about having to add every possible entity, or needing to update it every time an OXP adds something new to the Ooniverse.

Wildeblood wrote:

Note also that displayName is incorrectly documented - you can't trust it to actually exist.

Wildeblood wrote:

pagroove wrote:

Is the naming random for the stars or do you maintain a naming list?

If the star's name is set, it reads that. If not, it adds to the planet's name: e.g. "Lave" becomes "Lave Stella". (Does anyone have a preference between Aster, Astra or Stella?)

Disembodied wrote:

Wildeblood wrote:

pagroove wrote:

Is the naming random for the stars or do you maintain a naming list?

If the star's name is set, it reads that. If not, it adds to the planet's name: e.g. "Lave" becomes "Lave Stella". (Does anyone have a preference between Aster, Astra or Stella?)

Of the three, I'd pick "Astra" (actually, I'd pick "Astrum", as singular), but to be honest I think if the star and the planet have the same name, it's not necessary to differentiate them further since you're already adding information on the star type.

Svengali wrote:

...the short interval of consoleMessages with a lot of empty lines renders every notification useless (Oolite and OXPs)....

Wildeblood wrote:

Diziet Sma wrote:

Why only at green alert? Excepting combat, of course, most of the game is played on yellow alert.

Because there are too many other things popping up messages on screen at yellow alert, and no way of predicting or detecting them. There are a limited range of messages that appear at green alert and they can fairly reliably be detected to pause the ETA update while their messages display.

Wildeblood wrote:

Svengali wrote:

...the short interval of consoleMessages with a lot of empty lines renders every notification useless (Oolite and OXPs)....

But previously...

Wildeblood wrote:

Diziet Sma wrote:

Why only at green alert? Excepting combat, of course, most of the game is played on yellow alert.

Because there are too many other things popping up messages on screen at yellow alert, and no way of predicting or detecting them. There are a limited range of messages that appear at green alert and they can fairly reliably be detected to pause the ETA update while their messages display.

Spara's original version has been in the wild for several weeks now, and there haven't been howls of outrage, so I'd say it's less of a problem than Svengali imagines. I added some more interrupts Spara neglected, but I'm sure there are some more still missing. When people notice them and complain, they'll get fixed.

spara wrote:

Obviously the solution used in this oxp and mine is a compromise. To gain something like this you'll have to sacrifice something. I personally find this feature so good that I'm willing to sacrifice. I just don't know what I am missing and how important it is. So far I don't think I have missed a single important message, but how can I know that if I have not seen 'em? So does somebody know what I might be missing?

this.shipTargetAcquired = this.shipTargetLost = this.shipScoopedOther = this.shipKilledOther = this.viewDirectionChanged

The commsMessageReceived handler is sent when receiving a message from other ships. Handler is added in Oolite 1.75
commsMessageReceived = function(message: string, sender: ship)
{
// Your code here
}

Ranthe wrote:

This is a nice OXP, it certainly adds to the ambience.

One niggle though - when using the "spoken voices" game option, "ETA" gets pronounced as "Eh-Ta", not "Ee-Tee-Aye".

/* ===============================================
			CALCULATING & DISPLAYING THE E.T.A.

   In interstellar space compassTarget is undefined, will cause CTD in Oolite 1.76.1.
===================================================== */

this.$updateETA = function()
	{
	if (system.isInterstellarSpace || player.alertCondition != 1) return false;

			player.consoleMessage("\n\n\n\n\n\n\n\n\n\n" + this.$destination);
			player.consoleMessage("ETA " + hours + ":" + mins + ":" + secs);   // <<------------		
			}
		}
	if (oolite.gameSettings.speechOn !== this.$speechOn) this.$restartTimer();
	}

Wildeblood wrote:

Ranthe wrote:

This is a nice OXP, it certainly adds to the ambience.

One niggle though - when using the "spoken voices" game option, "ETA" gets pronounced as "Eh-Ta", not "Ee-Tee-Aye".

Yes, I know. I did consider changing the string from "ETA" to "E.T.A.", but current usage here is not to include full stops in abbreviations, and "E.T.A." looks quaint to me. I can only guess where everyone else is and what looks right to you. Last week I trawled through all Oolite's strings (in descriptions.plist), and the only example I could find used "ETA", so I decided to leave it as is for consistency. [...]

Then a bit further down the function ends like this, where you should change the second line:-

Code: Select all

			player.consoleMessage("\n\n\n\n\n\n\n\n\n\n" + this.$destination);
			player.consoleMessage("ETA " + hours + ":" + mins + ":" + secs);   // <<------------		
			}
		}
	if (oolite.gameSettings.speechOn !== this.$speechOn) this.$restartTimer();
	}

			player.consoleMessage("\n\n\n\n\n\n\n\n\n\n" + this.$destination);
			player.consoleMessage("E T A. " + hours + ":" + mins + ":" + secs);   // <<------------		
			}
		}
	if (oolite.gameSettings.speechOn !== this.$speechOn) this.$restartTimer();
	}