Oolite Bulletins

Commander McLane wrote:

The only thing you have to add below is an additional return after each adding-command:

Code: Select all

   { 
      system.addShipsToRoute("casinoship", 1, 0.995); 
      return;
   }

This way you make sure that the code execution stops after successfully adding any one of the stations. No need to further evaluate the odds for the other stations.

Switeck wrote:

how much more work would it be to give a system or individual stations a "station destroyed" status, so if the OXP station/s get destroyed they won't be there when you come back?

Switeck wrote:

Commander McLane wrote:

The only thing you have to add below is an additional return after each adding-command:

Code: Select all

   { 
      system.addShipsToRoute("casinoship", 1, 0.995); 
      return;
   }

This way you make sure that the code execution stops after successfully adding any one of the stations. No need to further evaluate the odds for the other stations.

For what it's worth, the Hoopy Casino is special...I expect it to be in ADDITION to other stations since it's not a "general" purpose station and has very few items for sale or buy. It's not as big as the others and only sees specialty traffic. But for the rest, yes return; would work.

Switeck wrote:

I would however have to add the first_launched = true before that return, more for consistency than anything else...a station might be destroyed and I wouldn't want it coming back just due to a relaunch.

   if(system.sun.isGoingNova || system.sun.hasGoneNova || system.isInterstellarSpace || !this.firstLaunch) 
      { 
      return; 
      }
   this.firstLaunch = false;

Switeck wrote:

Come to think of it...how much more work would it be to give a system or individual stations a "station destroyed" status, so if the OXP station/s get destroyed they won't be there when you come back?

Commander McLane wrote:

By the way: the Biosphere is another randomly added station in the aegis, and could be included in the mix. I wanted to link it, but I notice that it doesn't even seem to be on the Wiki.

Commander McLane wrote:

I like the idea. Seeing some consistency, and also making the player's actions having some impact (like, if you destroyed a station, it's gone) would definitely be an improvement.

Kaks wrote:

Commander McLane wrote:

I like the idea. Seeing some consistency, and also making the player's actions having some impact (like, if you destroyed a station, it's gone) would definitely be an improvement.

IIRC, the idea behind making main stations indestructible was related to them being the only 'saving points' - yes, there's saving anywhere, but without a main station saving anywhere won't work...

To get round that problem, we could create damaged stations (at least retexture them on the fly with a damaged texture) in 1.74 and - not tried that yet - I think we can play with conditions & system variables in planetinfo.plist to make sure that 'myDamagedStation' always appears in system X if mission variable 'damageXStation' is set to 1 (and use 'myUndamagedStation' if that variable is set to 0).

Commander McLane wrote:

I wasn't thinking of destroying main stations. I am all for them to be indestructible. (But I can't speak for Switeck, of course.)

Switeck wrote:

About the one place they *WON'T* go...is a secondary station in orbit around the planet...because chances are there's at least 1 closer station of some kind (friendly or otherwise) for them to dock with instead.

Commander McLane wrote:

I think that could be modified, so that at the end of HEAD_FOR_PLANET there is a random chance to go to the nearest station instead of the main station. If the main station is also the nearest, or there is no other station in the aegis, nothing would change. But if there is another station in the aegis, and it is a little closer to the ship's current position, the ship would dock there instead.

@ Eric: Does that seem viable to you?

Eric Walch wrote:

Differentiating between main and secondary planets was added in 1.73. With all those added planets it would just seem stupid when the trader would first fly to the nearest planet, but than go tho the main station. When extra planets have a station and a trader is added closer to that planet than the main planet, the current trader AI should dock him to that station.

Eric Walch wrote:

The only thing that would work is creating a new command that looks for the nearest station that allows npc-traffic.

Switeck wrote:

The simplest solution I've seen is the suggestion of setting a role for all secondary stations so there's only 1 (or 0) per system. Then ai's in AI.plist files could choose to dock with whatever that role is, regardless of where it is...and even fall back to the main station or nearest station if not found.

		"AEGIS_CLOSE_TO_MAIN_PLANET" = ("rollD: 4");
		"ROLL_1" = ("setStateTo: GO_TO_SECONDARY_STATION");
		"ROLL_2" = ("setStateTo: GO_TO_MAIN_STATION");
		"ROLL_3" = ("setStateTo: GO_TO_MAIN_STATION");
		"ROLL_4" = ("setStateTo: GO_TO_MAIN_STATION");

Commander McLane wrote:

I actually wondered how the trader gets to the secondary planet in the first place. The ship only enters the GO_TO_SUB_STATION state when it receives the CLOSE_TO_SECONDARY_PLANET message. But for this it has to pass by the secondary planet while in state HEAD_FOR_PLANET. In other words: if the secondary planet isn't close to the corridor (less than 3 radii), the ship will never get there.

Mauiby de Fug wrote:

So, I, with the aid of the ever useful Oolite BB search plugin, go digging about
...
My thanks to all who have helped me once again attempt to manipulate the fabric of the 'verse!