Oolite Bulletins

var beacon = system.addShips("x__beacon",1,x_ship.position,50);
beacon.primaryRole = "x__beacon"; //set explicitly; is this necessary?
beacon.position = x_ship.position.add(x_ship.heading.multiply(x_ship.collisionRadius+1)); //shift the beacon outside the target's collision zone 
log(this.name, "x_spawnBeacon spawned beacon for " + x_ship.displayName);
beacon.target = x_ship;
log(this.name, "x_spawnBeacon assigned a target to it of " + beacon.target);

• 16:14:17.027 [x_Loc]: x_spawnBeacon spawned beacon for Chopped Cobra
  16:14:17.027 [x_Loc]: x_spawnBeacon assigned a target to it of [Ship "Chopped Cobra" position: (5609.6, 11493.7, 20624.9) scanClass: CLASS_CARGO status: STATUS_IN_FLIGHT]

var beacons = system.shipsWithPrimaryRole("x__beacon");

jnorichards wrote:

Hi, I'm debugging an OXP that my son is writing...

Smivs wrote:

Cool! My son is only three, but I'm sure he'll go over to the 'Dark Side' when he's a bit older. Give your lad a cookie

Thargoid wrote:

Maybe we should start a sticky thread for such things, or perhaps use the scripters cove for such tips and findings.

jnorichards wrote:

Smivs wrote:

Cool! My son is only three, but I'm sure he'll go over to the 'Dark Side' when he's a bit older. Give your lad a cookie

When he gets home, perhaps. I was debugging 'cos I'm retired and although the problem was driving him nuts, he had to go out to work!

jnorichards wrote:

EDIT: OK, I've seen it. system.addShips() returns *an array*, so the target assignment is going astray: it should be beacon[0].target = x_ship;

I'll leave this post here as a memorial to the invisibility of the obvious... with hindsight!

Switeck wrote:

Another thing you can do is use:

Code: Select all

var beacon = system.addShips("x__beacon",1,x_ship.position,-50)[b][0][/b]; //(-50 since if it's behind the ship, the ship shouldn't run into it.)

...Then you don't need to do beacon[0].whatever to call up information about what should be 1 beacon.

Assuming there's supposed to be only 1 beacon ever, ...

jonathan@Odin:~/.Oolite/AddOns$ find . -name '*.js' | while read f; do grep -iH 'latest_puzzle' "$f"; done

jnorichards wrote:

We've cannibalised things from Escape Capsule Locator, Trackers, and others.

Eric Walch wrote:

jnorichards wrote:

We've cannibalised things from Escape Capsule Locator, Trackers, and others.

Or you could make an oxp that only works from 1.77 onwards. In that version will beaconCode become a writable ship property.

jnorichards wrote:

Thanks, guys. My most-used command at the moment:

Code: Select all

jonathan@Odin:~/.Oolite/AddOns$ find . -name '*.js' | while read f; do grep -iH 'latest_puzzle' "$f"; done

find . -type f -name '*.js' -exec grep -iH 'latest_puzzle' {} \;

Tricky wrote:

OT: That can be simplifed with the -exec argument of find.

Code: Select all

find . -type f -name '*.js' -exec grep -iH 'latest_puzzle' {} \;

Svengali wrote:

But be aware that changing beaconCodes of other OXPs entities breaks AIs (targetFirstBeaconWithCode, targetNextBeaconWithCode)