Oolite Bulletins

1. Dev vs Prod installations
2. Setting up a Dev environment
   1. Installing Notepad++
   2. Install 7zip
   3. Install Oolite to a Dev location
   4. 'always-flush-cache'
3. 'Welcome Mat' OXP deconstruction
4. Implementation of the 'Template Script.JS OXP'
5. Rebuilding the 'Unsafe Systems Warning Tool OXP'
   1. Displaying comms messages during witchspace countdown
   2. First test
   3. Troubleshooting issues encountered
      • No connection to debug console
      • Underpowered ship during testing
6. Appendix
   1. Creating a custom Oolite icon for Windows using GIMP

Lone_Wolf wrote:

please, get rid of Config/script.js .
Use world-scripts.plist instead, and put all scripts in the Scripts folder.
This will allow all scripts to have a unique name and helps to prevent clashes.

Never mind about that, I must be blind or something.

Lone_Wolf wrote:

(windows filenames are NOT case sensitive, 99% of linux filenames are.)

Lone_Wolf wrote:

Glad to see you back, bugbear.
Your name is listed in many great oxps as author or co-author.

Lone_Wolf wrote:

The document is interesting, some comments :

Keep the windows specific parts to a minimum and make clear that most of the document is usable for all 3 platforms oolite runs on .

Add a note about case-sensivity (windows filenames are NOT case sensitive, 99% of linux filenames are.)
Easiest way for windows users to ensure their oxps will run on linux/OSx is to use lowercase filenames only.
Folders should start with a Capital letter though.

Lone_Wolf wrote:

give alternatives, for example notepad++ is windows-only but kate offers similar functionality on linux.
7zip is multi-platform, and i think available for all 3 platforms.

Lone_Wolf wrote:

XML format is rarely used nowadays, most people prefer the NS style (Next Step ?) .
I think there's a python utility somewhere to convert XML to NS format.

Lone_Wolf wrote:

Add a chapter about the oxp-verifier ( run oolite -oxp-verify path-to-oxp-folder ) .
It's very handy to detect syntax errors.

Lone_Wolf wrote:

please, get rid of Config/script.js .
Use world-scripts.plist instead, and put all scripts in the Scripts folder.
This will allow all scripts to have a unique name and helps to prevent clashes.

spara wrote:

And about the howto. A few lines about the debug console would be nice.Never mind about that, I must be blind or something. Let me just say: Looking good .

log( this.name, strMsg );

Bugbear wrote:

For example, when testing, is it possible to enter a command that will 'magically' teleport your ship from witchspace beacon to an arbitrary location in system (say just outside main station aegis)?

this.debug = 0;
/** launch from station for testing */
this.shipWillLaunchFromStation = function() {
    if (this.debug != 1) return;
    player.ship.position = system.locationFromCode('OUTER_SYSTEM_OFFPLANE');
    this.$populateSystem(player.ship.position.add([1E4, 1E4, 1E4]));
};

this.$populateSystem = function(pos) {
  // do whatever you want
};

/** have the content appear between the witchpoint and the station */
this.systemWillPopulate = function(station) {
     if (system.scrambledPseudoRandomNumber(clock.seconds) < this.LIKELIHOOD * system.techLevel) {
         system.setPopulator('foo', {
             callback: function(pos) {
                 this.$populateSystem(pos);
             }.bind(this),
             location: 'LANE_WP'
         });
     }
};

Bugbear wrote:

For example, when testing, is it possible to enter a command that will 'magically' teleport your ship from witchspace beacon to an arbitrary location in system (say just outside main station aegis)?

 PS.position = [x,y,z]

PS.position = S.mainStation.position.add([0,0,25000])

"gotoAegis"	= "player.ship.position=system.mainStation.position.add([0,0,25000])";

Bugbear wrote:

spara wrote:

And about the howto. A few lines about the debug console would be nice.Never mind about that, I must be blind or something. Let me just say: Looking good .

Actually, I want to put an section abut how to use the debug console myself, especially with regards to entering commands. I only discovered the other night that the...

Code: Select all

log( this.name, strMsg );

...command will make 'strMsg' appear in the debug console. Saves one from monitoring Latest.log. So there is much that I need to learn about the debug console.
For example, when testing, is it possible to enter a command that will 'magically' teleport your ship from witchspace beacon to an arbitrary location in system (say just outside main station aegis)?

system.addShips("asteroid", 10)

PS.position=[0, 0, -10000]