JS and wormholes

[Commander McLane]

What about wormholes is currently exposed to JS? I haven't found anything in the documentation, except that world script event handler shipWillEnterWitchspace can have "wormhole" as the value of its cause-parameter.

Specifically I'd like to know whether

• there exists an undocumented wormhole JS-object? (S.entitiesWithScanClass("CLASS_WORMHOLE") for instance returns an empty array; also when targeting a wormhole PS.target is null; so I guess the answer is no);
• at least some properties (like duration and destination) can be accessed by JS? Specifically, I'd like to have my script know the destination of the wormhole the player is currently entering; player.ship.targetSystem returns the system selected on the map, not the system the entered wormhole leads to.

[Eric Walch]

From the code:

Code: Select all

			// Should probably pass the wormhole, but they have no JS representation
			[ship doScriptEvent:OOJSID("shipExitedWormhole") andReactToAIMessage:@"EXITED WITCHSPACE"];

The comment says enough: currently none of the code it prepared to pass wormholes as parameter. Wormholes are no ship class.

[Commander McLane]

:sigh: I was afraid so.

I was alerted to a glitch in wormhole_restoration.oxp which can only be solved with JS-knowledge about wormholes:

If the player follows an NPC-wormhole and misjumps, he is of course headed to the NPC's target system, not to his own. Therefore the re-created wormhole out of interstellar space should lead to the NPC's target system, not his own. But the script is only storing the player's target system.

And without being able to read out a wormhole's destination I can't change that.

[Staer9]

So therefore, it could just be a bad understanding, if I misjump and your wormhole_restoration.oxp is active, then if I change my target system and reactivate the wormhole I will go there instead... even if it is on the other side of the galaxy?

[Capt. Murphy]

You can derive duration when you can access the mass of the NPC ship the created the wormhole via JS. Can't help with destination.

duration in seconds = 50 + (mass/4000).

[Commander McLane]

So therefore, it could just be a bad understanding, if I misjump and your wormhole_restoration.oxp is active, then if I change my target system and reactivate the wormhole I will go there instead... even if it is on the other side of the galaxy?

No, the OXP stores your target system the moment you do the misjump. If you target another system while you're still in interstellar space, that won't change anything. The saving wormhole always goes to the system you had targeted when you first misjumped.

So the problem only happens if you had targeted one system, but jumped to another system by following an NPC's wormhole, and this NPC (and therefore you in its footsteps) has a misjump. The chances for that are fairly low.

Nevertheless, I still have an idea how to possibly fix this. I am at it right now.

[Staer9]

Thats a pity, it would be a great way of traveling long distances really fast

[Commander McLane]

You can derive duration when you can access the mass of the NPC ship the created the wormhole via JS. Can't help with destination.

duration in seconds = 50 + (mass/4000).

Thanks, but I only need the destination anyway.

Also, it's effectively impossible to access the NPC. The player may only decide to enter a wormhole when the NPC has already jumped out. The script can't foresee which wormhole the player is going to choose, or if he chooses any in the first place.

[Commander McLane]

Thats a pity, it would be a great way of traveling long distances really fast

The 7LY rule is set in stone in Oolite. There's no way around it.

It's one of the very few absolutely fixed things, because changing it would have a massive impact on gameplay and game balance, to the point of altering the game beyond recognition.

To put it very simply: the 7LY rule is one of the defining features of Elite. Altering it would result in a type of game that is not Elite. But Oolite is a type of game that is Elite.

[Commander McLane]

Another question to the code/JS-wizards: does a function exist that returns a system number or possibly a systemInfo object if fed a set of galactic coordinates?

Never mind, I got it (this.originSystem was stored before the jump):

Code: Select all

this.shipWillExitWitchspace = function()
{
    <snip>
    // the target system of the jump is established
    this.originCoordinates = System.infoForSystem(galaxyNumber, this.originSystem).coordinates;
    this.currentCoordinates = system.info.coordinates;
    this.coordinatesDifference = this.currentCoordinates.subtract(this.originCoordinates);
    this.jumpLength = this.coordinatesDifference.multiply(2);
    this.targetCoordinates = this.originCoordinates.add(this.jumpLength);
    this.targetSystemInfo = SystemInfo.filteredSystems(this, function(other){return (other.coordinates.squaredDistanceTo(this.targetCoordinates) < 0.0000001)});
    this.targetSystem = this.targetSystemInfo[0].systemID;

So in the next version of wormhole_restoration.oxp the wormhole out of interstellar space will always to the correct system, the one you were actually heading for.