[Droid803]

I believe this thread is the reason why you typically don't explain the technobabble unless it's absolutely necessary, especally since

Well if you're going to explain exactly how it works be prepared to get picked apart for it~

[Legate Damar]

Because then they might find a way around it... better to let them think it's working, then when they try to fly it then they die and it autoplots a jump to the nearest Shivan base. So they get their fighter back. Sort of like, did you see Stargate SG-1? They put a failsafe in the Goa'uld fighter that made it fly back to the base when it was captured.

See in FS1/FS2 a Shivan fighter always gets captured, figured they would get wise to that and take precautions against it.

[NGTM-1R]

Apparently, Shivans don't have a big enough colon to serve as a chemical propellant chamber for long space flights.

They do if they use this much bull**** physics!

[Droid803]

Because then they might find a way around it... better to let them think it's working, then when they try to fly it then they die and it autoplots a jump to the nearest Shivan base. So they get their fighter back. Sort of like, did you see Stargate SG-1? They put a failsafe in the Goa'uld fighter that made it fly back to the base when it was captured.

See in FS1/FS2 a Shivan fighter always gets captured, figured they would get wise to that and take precautions against it.

If I can find a way around shutting down everything, I can find a way around shutting down of one system. Most likely. Just sayin'.
Better off not letting them fly anything at all than just nerfing one capability. Just make it shut itself down and fly back with the live pilot inside, for questioning, or disposal. Don't wait on them *discovering* how to activate something which will kill them. That's really silly. What if they never activate it and use it to infiltrate your ranks again anyway?

Disabling one non-critical system solves nothing. Shut the whole thing down, have it seal itself, and return to the carrier. Might still bite you in the ass due to giving your position away, but at least you're eliminating the possibility of it coming back to haunt you as much as possible.

Don't bank on "OH HEY THIS IS A WORKING FIGHTER I WONDER WHAT THIS BUTTON DOES>", why bother with such a stupid failsafe? It's not very "fail safe" at all, and is rather prone to actually failing to do anything.

[NGTM-1R]

See in FS1/FS2 a Shivan fighter always gets captured, figured they would get wise to that and take precautions against it.

Assumes they care. They might not; numbers are small and effect they can determine may not be serious. (Particularly when there might have been no survivors to tell anyone in FS1.)

[Legate Damar]

Because then they might find a way around it... better to let them think it's working, then when they try to fly it then they die and it autoplots a jump to the nearest Shivan base. So they get their fighter back. Sort of like, did you see Stargate SG-1? They put a failsafe in the Goa'uld fighter that made it fly back to the base when it was captured.

See in FS1/FS2 a Shivan fighter always gets captured, figured they would get wise to that and take precautions against it.

If I can find a way around shutting down everything, I can find a way around shutting down of one system. Most likely. Just sayin'.

Not if it suddenly happens when you're in the cockpit and you die instantly from inertial forces.

Better off not letting them fly anything at all than just nerfing one capability. Just make it shut itself down and fly back with the live pilot inside, for questioning, or disposal.

Shivans aren't exactly big on capturing enemies... they did it to Bosch but that was a special case.

Don't wait on them *discovering* how to activate something which will kill them. That's really silly. What if they never activate it and use it to infiltrate your ranks again anyway?

If they capture the ship but never try to activate it? What good is it to them then?

Disabling one non-critical system solves nothing. Shut the whole thing down, have it seal itself, and return to the carrier. Might still bite you in the ass due to giving your position away, but at least you're eliminating the possibility of it coming back to haunt you as much as possible.

It would only have to shut down after it's already in flight and ready to jump, else it would be analyzed and maybe reactivated again.

Don't bank on "OH HEY THIS IS A WORKING FIGHTER I WONDER WHAT THIS BUTTON DOES>", why bother with such a stupid failsafe? It's not very "fail safe" at all, and is rather prone to actually failing to do anything.

There is no button... the pilot doesn't need to do anything to make it happen. It just happens when the ship's computer detects that it is safe to jump and there is a non-Shivan flying it.

Assumes they care. They might not; numbers are small and effect they can determine may not be serious. (Particularly when there might have been no survivors to tell anyone in FS1.)

Well for the purposes of this idea let's say they do care.