Oolite Bulletins

Lestradae wrote:

OK, then I will provide the playerStations.js and the OSE-populator.js currently residing on my harddrive:

Thanks, but that is the playerStations.js that I provided before.

Is the next earlier revision of it from the 0.70 release? If so I'll supply the modifications from that instead.

There's just one problem with pmw57's approach: expandDescription collapses an array of alternative strings into just one string. Using the example above, only one of all possible 'mclane-attacked' strings is ever stored inside the this.descriptions object. Using my approach all the mclane-attacked...

So, how do I convert the arrays in descriptions.plist into an JS-array? I haven't yet managed to address the array-entries in descriptions.plist one by one. If I try something like personalities-mclane-attacked[n] , I don't get the n'th entry in the personalities-mclane-attacked array, but the n'th...

<rubs sleep from eyes> 1) The six scripts in the folder now do everything nescessary for the player stations, including placing them in systems if owned, yes? I'll have a look around this evening and see what else there is to be found in the property lists. 2) I can take out all planetinfo.plist ent...

Thanks, pmw57, for looking into it :D The player stations script is now updated. playerStations.7z The last several hours of entertainment has been spent troubleshooting a shipWillExitStation event, to much hair pulling. Anyway, playerStations.js has been updated so that its events will run both wh...

The playerstations still have a part in planetinfo.plist that might get java-scripted instead Would it be possible to java script this instead, and would you do it if the answer was yes? I'll see what I can do. Second thing is, I did randomise the "fluctuating market" for the playerstatio...

Also whilst some people may like the Oobay stations and all the "unusual" player ships and things like that, I can't say personally that I do. I just want a nice mix of ships to look at, but relatively few are of interest to actually fly. Removing oobay is as simple as commenting out a si...

Er, what exactly is this intended to achieve? JavaScript’s Math.random() is not affected by Oolite’s random seed resets. Math.random() doesn’t seem to be an especially good PRNG (although better than either of Oolite’s), but “stirring” it like this shouldn’t give you an appreciably “more random” re...

Instead of bickering, here is a better way to seed a random number based on the time. [code]this.ReserveDutySystemDetermination = function() { var sec = clock.minutesComponent * 60 + clock.secondsComponent, dummy; for (var i = 0 ; i < sec ; i++) { dummy = Math.random(); } this.ReserveDutySystemDete...

Kaks wrote:

One situation I can think of is if an AI.plist needs to access a string. In that case, we definitely want to keep the original string inside descriptions.plist...

Okay, so for now I will cache the desired descriptions when the script loads, to help avoid any cross-use issues.

pmw57, I would seriously consider internalising those descriptions.plist arrays as js arrays and pick a random adjective/name from those. Whenever any description from descriptions.plist is accessed, oolite has to go through a dictionary (obj-c speak for associative array) made up of the sum of all...

I have begin translating the event-based property list script into an event-driven javascript script. I have translated the first third of the code (3000 lines), with a reduction down to 16% of the original size. I was going to provide a first-look at the code, but box.net isn't wanting to load for ...

Get'cher trumble provisions!

Ammo for trumbles

Trumbles for sale
(hot deal today)