FTL 1.6.2 Flagship location glitch when re-saving after defeating it

[Vhati]

Dunno if this still applies to 1.6.2.


I was investigating an unknown field in a FTL 1.5.13 saved game.

setRebelFlagshipVisible( boolean )
setRebelFlagshipHop( int )
setRebelFlagshipMoving( boolean )
setUnknownKappa( int? ) // This one.
setRebelFlagshipBaseTurns( int )

It's almost always 0... except when saved immediately after defeating the flagship (seen after both stage 1 & 2). Bouncing to the main menu to re-save causes it to decrement.

This value seems to glitch the hop index. Sometimes resetting both hop and base turns to 0.

• Defeat the stage 1 flagship at the base. Look at the map. The flagship begins moving away from the base.
• Go to the main menu and continue, to reload.
• The flagship is suddenly several beacons away where it started (hop = 0).

There was a crash once, but I don't recall whether crashing was possible purely from repeated bouncing or from my editing hop / kappa combinations.

If I edit it to 1 or 2 when the flagship hasn't reached the base yet, the value almost seems to cause backtracking?

The post-combat event reloading might have something to do with this bug, too.


Edit: Confirmed in FTL 1.6.2 after defeating stage 2 at the base and going to the main menu twice.