Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Inventor Raccoon]

Okay, admittedly, this could be because there's a line of code or a memory flag that needs to be in place that I've missed, but... Ships with an officer who is set as unremovable (through Misc.setUnremovable) still seem to be able to be set as your flagship, which causes your character to swap with them. They will then become "permanently assigned" to your old flagship.

If the ship is the only one in your fleet, they'll become unassigned. If you gain another ship after that, you can now freely assign the officer to a new ship where they'll be (not so) permanently assigned.

You can't transfer command to them before battle, so that's working as intended. Other officers cannot swap with an unremovable one, so that's also fine.

Before/after screenshots below.

Spoiler

[close]

[Alex]

Thanks, made a note!

[Histidine]

Relatedly:

- You can also remove an "unremovable" human officer by scuttling the ship they're on or losing it in combat.
- The officer can now be assigned to a new ship, but is then stuck on it; have to do the same thing as before or do the trick in OP to change their ship. This is a problem because a player might get an officer glued to the wrong ship without prior warning.

Should the unremovable state be made to apply to the fleet member rather than to the person? Seems like it'd fix the issues, but might introduce new ones.

[Alex]

Ah, hmm - this is getting involved enough that it's pretty unlikely I'd be able to reliably get this sorted out (and have it remain working) without a vanilla use case.

It seems like this could *probably* be hacked around with scripts, though? Although the "scuttled" case is a bit more troublesome and would require remembering which ship the officer was meant to be assigned to.