How do I? .... (on Debug Console)

[Cholmondely]

Just to say: I've put a summary of everything I've so far found at the top of this thread, together with links to Hiran's indispensible databases (useful for names of equipment/ships recognisable by the debug console).

[phkb]

A couple of notes:

Code: Select all

P.credits = 1000

This will set your credit balance to 1000, not add to it. To add credits, you need to do this:

Code: Select all

P.credits += 1000

On awarding self another ship, I would recommend only doing this while docked, not when in flight.

[Cholmondely]

A couple of notes:

Code: Select all

P.credits = 1000

This will set your credit balance to 1000, not add to it. To add credits, you need to do this:

Code: Select all

P.credits += 1000

On awarding self another ship, I would recommend only doing this while docked, not when in flight.

Umm.. thank you!

[Cholmondely]

Cause a docked dockable (liner, behemoth) etc to buzz off to another system with you inside:

PS.dockedStation.exitSystem(insert number of an adjacent system here).

From https://bb.oolite.space/viewtopic.ph ... 44#p174544 (Commander McLane 2012)

[Cholmondely]

Copied from elsewhere:

Spawning a ship:

Code: Select all

:spawn <roleOfEntityYouWantToSpawn>

e.g. to spawn a pirate you execute :spawn pirate. List of roles:  Oolite Ship Roles

If you want a specific ship, you can use its  shipdata.plist key enclosed in square brackets e.g. :spawn [cobra3-trader]. Note the colon as the first character of the command, in this case it is required.

With the above you can spawn pirate coves, pirates, traders and whatever else you may want to in order to do a test. This way you reduce the 'good luck' factor a lot and hopefully you will be able to perform your tests much faster than having to wait for the game to generate the ideal conditions for you.

Source: another_commander (2016)