Oolite Bulletins

The only way to travel: it's a shame. I imagine the game could be changed (with some work) to allow allow a manual switch from one system to another. If so, then when one leaves one's ship running its jump drive in deep space and comes back, what, a few days later (or less than that if one is using ...

The OXZ at issue with the latest problem you found seems to be: Additional Planets SR Others Gas Giants pack. The maintainers of that seem to be 'Redspear, spara and collaborators'. I suggest you contact Redspear or Spara - if you don't hear from them - by commenting on one of their threads or, perh...

You might want to ask on the Linux subforum about freeware programs (for, even if you are not on Linux, those folks are likely to know of freeware stuff - some of which might work on other operating systems). As to unweaving the rainbow, as it were: I haven't found that this diminishes my appreciati...

Good stuff, phkb!

Thanks very much Rustem. I'm seeing what I can get working . .

Thanks! I'll have a go with that code and with the ideas offered elsewhere by rustem.

Dear all I am after a way of setting a (any) perpendicular course from a celestial object (sun or planet or secondary planet - or, better: a roughly - not exactly, i.e. I want some randomisation. I know how to get the celestial entity - with all its properties, I think - as an element in an array, b...

phkb, Yes indeed! That's the stuff! The magic of Oolite and Javascript! I now have the escorts recognising - without too much system load - when they are close to celestial bodies, messaging the player about it, and sometimes temporarily refusing to go further. The next and - for the moment, last - ...

Thanks, phkb! One more (slightly involved) thing, if I may. I'm making progress, but I'd like the calcAltitudeForShip function to return, additionally, a boolean that is true if and only the player is moving towards the nearest celestial body. To that, I imagine we'd need to check the ship's speed (...

Also, I've forgotten how to get AI state changes - using plist AIs - to get logged in the main Oolite log. The following, in a ship script, doesn't seem to do it (even though I have the debugOXZ installed). this.debug = true; var consoleDebugMessages; if ( this.debug === true ) { this.logging = true...

Hmm! I have not yet tested - I've only just finished the first draft of my code - but: The aegis check is part of the system update and messages needs no command to generate them. The following messages are only generated when the status changes. "AEGIS_CLOSE_TO_PLANET": Within 3x planetary radius o...

Marvellous. I will use that code - in conjunction with the automatically generated AI messages. For, I'll do this. When a hiredGun receives a 'CLOSE_TO_<SOMETHING>' message, I'll start a timer that calls your js code and reacts to its findings; when a hiredGun receives an 'AWAY_FROM_<SOMETHING>' mes...

phkb: thanks for the reply. Now . . > What I did notice is that the older plist AI methods have some messages you can respond to: AEGIS_CLOSE_TO_MAIN_PLANET, CLOSE_TO_PLANET, CLOSE_TO_MOON, and CLOSE_TO_SECONDARY_PLANET. I'm not sure if equivalent functions exist in the newer PriorityAI. I am using ...

Dear all I'm updating Thargoid's HiredGuns OXP (with his permission). One thing that needs changing is the tendency of the escorts (the 'hired guns') to crash into planetary bodies. Now, I am having trouble determining how close they are to such bodies. True, there are various messages Oolite gives ...

OK, thanks!