AP 3.0, Autojump, Gateless sectors

[Shimrod]

I found that if autojump is enabled on a ship in AP 3.0 and it's told to move to certain gateless terran sectors, it'll just sit there and do nothing. Specifically:

1. Enable autojump in ship settings
2. Use navigation commands and select a terran sector which is:
a. Not directly jumpable
b. Is about 2 sectors away from any other jumpable sector

Script debugger shows !move.jumptogate.nearest -> !move.jump -> !move.stay invoked a 999999ms wait.

AP 3.0 !move.jump :-

Code: Select all

042   |$r = [THIS] -> use jump drive: target=$target
043   |gosub Check.Jump.Capable

047   Check.Jump.Capable:
048   skip if $r == FLRET_ERROR
049   |endsub
050   [THIS] ->set command: COMMAND_NONE
051 @ $target = [THIS] -> call script '!move.stay' : 
052   return $r

So it looks like 'use jump drive' returned FLRET_ERROR, and decided it's safest to invoke !move.stay rather than return with the error code.

I happened to have a copy of an earlier version of an AP script folder. Comparing the code from that below, it looks like this stay call has only recently been introduced.

Some earlier revision of AP !move.jump :-

Code: Select all

039   skip if [THIS] -> is of class Big Ship
040   |$r = [THIS] -> use jump drive: target=$target
041   
042   return $r

[Nanook]

I found that if autojump is enabled on a ship in AP 3.0 and it's told to move to certain gateless terran sectors, it'll just sit there and do nothing. Specifically:

1. Enable autojump in ship settings
2. Use navigation commands and select a terran sector which is:
a. Not directly jumpable
b. Is about 2 sectors away from any other jumpable sector...

That's not a bug. It's normal behaviour and does the very same thing in TC. Autojump requires a jumpgate, or a beacon, in the destination sector. The game is not programmed to allow a partial jump and then fly to destination command.