For information and discussion about Oolite.
https://bb.oolite.space/
Thinking about this it would probably easier to have a propertyCapt. Murphy wrote:Hi,
In preparation for future stable releases being in deployment build format, but with developer releases in test-release format could we add a property to the Oolite object - something along the lines of buildType - a string which is either "deployment", "test" or "snapshot". This would allow scripters to continue to utilise non deployment scripting features in OXPs like TAF and scripted screenshots, but automatically disable them if the OXP is running in a deployment context.
Edit to add - alternatively is the status of scriptable TAF/screenshots and availability in deployment builds an item open for discussion?
Oolite.isDeployment - set as true, with an override in between debug flags to set it as false? (He says pretending to know what he's talking about... 
)CommonSenseOTB wrote:However I would like my oxp to be changed by the laser. Specifically, I would like to be able to read the JS of laser teperature so I can make custom gauges for HUDs that show the laser temperature. It's going to be really awkward to spend all the time and effort to make a hud with custom gauges that match and still be stuck with a stock bar gauge to show laser temperature. And when I start using images for gauges they really are going to be a mismatch to the stock laser temperature bar gauge.
Please help me devs...
Thank you, kindly.cim wrote:Phasted wrote:An event-handler (well, two actually) that triggers when the player buys or sells cargo (passing commoditiy name, quantity, and price).playerBoughtCargo(commodity,units,price)andplayerSoldCargo(commodity,units,price)are available as of r4851.
station entity its own market object (along the same lines as the player's manifest object), allowing the harried, overworked OXP-writer direct access to prices and quantities without the need to horse around with that @#&%$ commodities.plist?player.ship.serviceLevel read/write?EQ_RENOVATION, thus avoiding maintenance overhauls, so making it read/write wouldn't create a new 'exploit'. And being able to set it downwards would be a useful feature in a variety of contexts.Added in r4910 (and for NPC ships too)Cmd. Cheyd wrote:
- Ability to read player.ship pitch, roll, yaw values from JS
I think the problem is that we currently have two different sound libraries (CoreAudio and SDL) in use, so any change would need to be made - in different ways - in both. I think I can see what's needed to make the SDL change, but I don't know about CoreAudio and couldn't test it even if I did. So I can see why it was postponed pending moving to a new sound library. I'd need to look at it a bit more to see if that was practical.Cmd. Cheyd wrote:The ability to control relative volume of a SoundSource? A range of 0-100 as percentage? I know Ahruman was talking of overhauling the complete sound system and moving to OpenSound (think it was OS) and this was postponed based on that. I don't know if that's still on anyone's roadmap. Or if this could be accomplished without the overhaul?
is_submunition key be modified or a new key given which would allow proper OXP external weaponry? By this I mean that when they achieve a kill, both the bounty and kill-count increase is automatically passed onto the ship that spawned/fired them, and that when the kill happens the parameter passed to shipDied is the mother/spawner rather than the weapon?In a similar vein, and possible a little more achievable could the contents of thecim wrote:I think the problem is that we currently have two different sound libraries (CoreAudio and SDL) in use, so any change would need to be made - in different ways - in both. I think I can see what's needed to make the SDL change, but I don't know about CoreAudio and couldn't test it even if I did. So I can see why it was postponed pending moving to a new sound library. I'd need to look at it a bit more to see if that was practical.Cmd. Cheyd wrote:The ability to control relative volume of a SoundSource? A range of 0-100 as percentage? I know Ahruman was talking of overhauling the complete sound system and moving to OpenSound (think it was OS) and this was postponed based on that. I don't know if that's still on anyone's roadmap. Or if this could be accomplished without the overhaul?
customsounds.plist keys be made visible to JS and read/write so a script could temporarily switch sound files to either a dummy silent sound file, or null if the core game code can handle it.model parameter of mission.runScreen accept both a role string or a dataKey string as valid inputs? The unique roles of the in-built ships have been removed somewhere around 1.73. I still haven't really understood why.Smivs wrote:Hmmm, intersting. They did used to. The Anaconda used to have roles of "trader oolite_anaconda" and the others had similar, but in the current verion plist they seem to have lost the defining role.
So try to interpret it as a role, and if that fails try to interpret it as a shipdata key? (and the same for addShips, etc.)Capt. Murphy wrote:Can we make themodelparameter ofmission.runScreenaccept both a role string or adataKeystring as valid inputs?