

Moderators: winston, another_commander
I've seen that a few times, but one or both has always turned out to be a pirate cove.Rese249er wrote:Not sure if this has happened to anyone else, but whilst tooling about G1, Ususor, a Poor Agro Feudal system with TL2, I came upon TWO Rock Hermits within scan range of each other. I just had to stop and scratch my head... I've got the game paused looking at these Hermits while posting this.
cim wrote:Well, I suppose you can have those.Code: Select all
r5190: [...] Add ship.max(Pitch|Roll|Yaw) properties [...]
Code: Select all
backgroundSpecial: "LONG_RANGE_CHART"
It’s \037.cim wrote:(Character \031 can now be used as an alignment control character as it is defined to be very narrow)
widths
table must be changed to 0.1 (it’s generally the last one that’s exactly 6) and the line " " = "\037";
must be added to the substitutions
dictionary. (That’s a Unicode “hair space”, not a normal space.) The necessary changes have been made to the encoding template OXPs.requires_docking_clearance
key in their shipdata.plist are not affected by the global setting.Wow, this looks really great! Beginings of a 'Fontier' style bulletin boardcim wrote:...Also some extra features for mission screens: these passenger contracts lookalikes are done entirely as mission screens....
Sort of. That and a few other things.Griff wrote:Beginings of a 'Fontier' style bulletin board
Code: Select all
Resources/Scripts/oolite-contracts-parcels.js
+1. Muchas gracias, cim.Commander McLane wrote:There were a number of requests over the years to use the F4-key for some purpose or another, and none was actually implemented, which always left the freedom for the F4-key to be used for the really most important thing at some time in the future. Now the future becomes present.
Cabal_Common_Comms provides inflight ship2ship and worldScript2ship communications without using a missionscreen. This way you don't loose control about your ship while communicating.Commander McLane wrote:My question (and possibly request) is whether this interface can also be used in-flight for communication with other ships. So you would target a ship (or station) and press F4 in order to bring up a screen which would allow for some dialogue. (I think the game also ought to be paused—or at least slowed down to the smallest TAF—until exiting this in-flight screen.)
Yes. Looking back through them, almost all of the requests for what should go on the F4 screen were either a variation of the interface functionality, OXPable as an interface, or had already been implemented elsewhere, so it turned out to be a fairly easy choice (though I did check that no-one else had other plans for it first, yes).Commander McLane wrote:There were a number of requests over the years to use the F4-key for some purpose or another, and none was actually implemented, which always left the freedom for the F4-key to be used for the really most important thing at some time in the future. Now the future becomes present.
Not easily, since the F4 key already has an in-flight use, and I'm not sure that encouraging mission screens in flight is a good idea.Commander McLane wrote:My question (and possibly request) is whether this interface can also be used in-flight for communication with other ships.
cim wrote:Not easily, since the F4 key already has an in-flight useCommander McLane wrote:My question (and possibly request) is whether this interface can also be used in-flight for communication with other ships.