Oolite Bulletins

Wildeblood wrote:

But there are two buttons - N to select mode, and n to activate - maybe you just want to edit your key configuration to change the N to a different - lower case - button, so you don't need to hold the shift key?

Kaks wrote:

It should allow for a fairly natural 'double click' effect...

Mauiby de Fug wrote:

I may be misunderstanding, but what I think timer is asking for is another key so that the set-up is as follows:

Key 1) Cycle and choose between the primeable equipment; Currently done with N/Control-N.
Key 2) Cycle and choose between the modes of the currently selected equipment; As far as I am aware, this is has to be done via N/Control-N, thereby clogging up the selection process.
Key 3) Activate/deactivate the currently selected equipment; Currently done with n.

Thargoid wrote:

• Making beacon code read/write rather than just read - so beacons can be added to existing ships without having to do a swap-over to a like_ship version with it set. So ships can be tagged and untagged on the fly.

[/color]

cim wrote:

Thargoid wrote:

• Making beacon code read/write rather than just read - so beacons can be added to existing ships without having to do a swap-over to a like_ship version with it set. So ships can be tagged and untagged on the fly.

[/color]

ship.setBeacon(code) is made available in r4840. Using the empty string will clear an existing beacon.

------------------------------------------------------------------------
r4840 | cim | 2012-04-11 13:20:29 +0300 | 3 lines

- fix bug in ASC where destruction of first or last beacon broke compass
- add ship.setBeacon(code) to scripting

------------------------------------------------------------------------

cim wrote:

ship.setBeacon(code) is made available in r4840. Using the empty string will clear an existing beacon.

Phasted wrote:

An event-handler (well, two actually) that triggers when the player buys or sells cargo (passing commoditiy name, quantity, and price).

cim wrote:

Phasted wrote:

An event-handler (well, two actually) that triggers when the player buys or sells cargo (passing commoditiy name, quantity, and price).

playerBoughtCargo(commodity,units,price) and playerSoldCargo(commodity,units,price) are available as of r4851.

cim wrote:

Phasted wrote:

An event-handler (well, two actually) that triggers when the player buys or sells cargo (passing commoditiy name, quantity, and price).

playerBoughtCargo(commodity,units,price) and playerSoldCargo(commodity,units,price) are available as of r4851.

Capt. Murphy wrote:

I also know someone who would appreciate a

this.playerBountyIncreased = function(penalty,reason)

Wildeblood wrote:

I'd like a way to be able to script galaxy jumps with more than one shift, specifically, with a parameter defining the number of shifts from either 0-7 or 1-8 so that the player can be jumped straight from galaxy 1 to galaxy 2, 3, 4, 5, 6, 7, 8, or back to a point in galaxy 1.

For people who like the eight galaxies in a ring scenario, seven shifts would allow the creation of a "reverse direction" galactic hyperdrive. For those of us who think the eight galaxies and one-shot galactic hyperdrive look suspiciously like "finish level 1 being proceeding to level 2", scripting that varied the number of shifts depending on the departure system would allow the eight galactic sectors to be arranged in any apparent relationship.

When returning the player to his starting galaxy, the process should proceed normally including that the playerEnteredNewGalaxy event should still fire, rather than create any special "jump failed" alternative. That would allow time travel/alternative universe/twilight zone scenarios to be created. "Unexpectedly, you arrive back where you departed from, everything is the same, yet somehow subtly different." [Cue spooky music.]

Wildeblood wrote:

cim wrote:

Phasted wrote:

An event-handler (well, two actually) that triggers when the player buys or sells cargo (passing commoditiy name, quantity, and price).

playerBoughtCargo(commodity,units,price) and playerSoldCargo(commodity,units,price) are available as of r4851.

Price per unit or total price?

Wildeblood wrote:

Not nearly as much as I'd appreciate this one:-

Wildeblood wrote:

I'd like a way to be able to script galaxy jumps with more than one shift, specifically, with a parameter defining the number of shifts from either 0-7 or 1-8 so that the player can be jumped straight from galaxy 1 to galaxy 2, 3, 4, 5, 6, 7, 8, or back to a point in galaxy 1.

For people who like the eight galaxies in a ring scenario, seven shifts would allow the creation of a "reverse direction" galactic hyperdrive. For those of us who think the eight galaxies and one-shot galactic hyperdrive look suspiciously like "finish level 1 being proceeding to level 2", scripting that varied the number of shifts depending on the departure system would allow the eight galactic sectors to be arranged in any apparent relationship.

When returning the player to his starting galaxy, the process should proceed normally including that the playerEnteredNewGalaxy event should still fire, rather than create any special "jump failed" alternative. That would allow time travel/alternative universe/twilight zone scenarios to be created. "Unexpectedly, you arrive back where you departed from, everything is the same, yet somehow subtly different." [Cue spooky music.]

Really I didn't think it would be particularly difficult...?

Capt. Murphy wrote:

Are you going to do...
this.equipmentRepaired = function(equipment) which is another outstanding request and would be useful (lots of OXPs currently need to use Timer's to monitor for repair).

I also know someone who would appreciate a

this.playerBountyIncreased = function(penalty,reason)