Hayabusa Override

Is it possible to override certain parts of a fighter from the bridge? For example: If there is a fighter in combat does the bridge have the ability to remotely deactivate such things as the engines, weapons, shields, etc?

People need to not be overridan me when I got some planning going on.

Apart from what's going on in the Illustrious currently, its still useful information to know and can be adapted as needed if later situations ever arise. Overall it doesn't hurt to know, just in case.

So the question still stands.

Basically sounds like you are talking about some kind of command code, while it could be useful in the case of the fighter gets damaged the crew is unconscious. There comes the risk with enemy craft attempting to take control of the fighter. Would probably have to have some kind of failsafe condition that would allow the override.

Such as not overriding the controls when the pilot is still alive or conscious.

To be honest though, an "Override" for Yamatai is the same as "Self Destruct" considering the use of ST.

Ception' to if they have important information of course.

The Sharie-class has a KAMI unit. It could override a Hayabusa's CIES unit without too much trouble. The CIES could reject the pilot and the KAMI would take control, or whoever the KAMI would give control to.

Doshii,
Without some sort of failsafe what you are saying would put every PA, and fighter at risk of being taken over by the Mishhu. They have captured a number of starships with KAMI computer systems.

If what you are saying is true that that the starship computer can override any fighter and power armor, any character of mine would be looking at replacing the computer with something else at least during the NMX campaign.

Nashoba

There might be failsafes — it's kind of an unexplored portion of how the quantum computers work.

My statement is based off of when Yukari used Miharu's MEGAMI to override the AIES-level systems of an NH-28. I inferred from that fact.

A KAMI is several levels above a CIES (EIES and MEGAMI are between it), after all. Maybe there ought to be some way for lower-level systems to identify hostile IES units and reject their attempts to subjugate it?

Well perhaps the term is the issue, subjugate, override.

Perhaps a better approach is that a lower system, can when requested by an identified friendly higher system can slave itself to it.

A Hayabusa can be controlled by its parent starship (not by other ships not in its chain of command). The pilot, however, can tell the computer to disregard those commands (at the risk of disciplinary action when he gets home). Breaking the control link immediately alerts the parent ship though and the fighter's status goes from friendly (green) to neutral (yellow) on the targeting screens of other Star Army units.

IFF Conditions:

Blue (VIP): Star Army units will fire automatically to protect a VIP unit (unarmed YSE diplomacy ships)

Green (friend): Star Army units cannot target or fire on friendly units (other Star Army ships and fighters)

Yellow (neutral): A unit can be targeted (Nepleslians)

Orange (hostile): Automatically targeted (NMX ships, etc)

Red (KOS): Automatically targeted and fired upon (incoming missiles, enemy pods, etc)

To prevent hostile takeover you could use the following measure:

Inform the machine via secure lines of a white-list of accepted communication frequencies and codes. If the white-list update contains false information (working toward a cyphered organic-arising pattern), it will check it three times before blocking the sources and keep a note of the attempt for the crew to go over later.

If it receives a request for command over these frequencies, the pilot is prompted to confirm (they can still deny).

If the pilot is unable to confirm (unable to respond), it'll send this back and a second confirmation code known only by bridge-officers will be requested.