Page 1 of 1

Non-malf AIs die when remote controlling mechs, and mech is destroyed - oversight?

Posted: Sun Nov 06, 2022 11:00 am
by Imitates-The-Lizards
So I just played a shift where I was a non-malf AI, and there were AI control beacons installed in a gygax. I controlled the gygax, the gygax got destroyed and... rather than return to my core, I was dead.

I am well aware of the viral mech domination malf AI power, where this behavior is intended, since taking over a mech is supposed to be a last ditch effort of shunting your core process to the mech to escape the crew invading your sat, however, for a regular ai control beacon, I don't see why it would be any different than remote controlling your shell? It seems very inconsistent with remote controlling shells.

Can this be fixed, please?

Re: Non-malf AIs die when remote controlling mechs, and mech is destroyed - oversight?

Posted: Mon Nov 07, 2022 12:14 am
by Rageguy505
Mech code is actually fucked. I don't think taking over the mech is supposed to be a last ditch effort, I thought it was a counter to some Durand punching it's way in.

Re: Non-malf AIs die when remote controlling mechs, and mech is destroyed - oversight?

Posted: Mon Nov 07, 2022 2:28 am
by Helios
Can intellicarded AIs inserted into mechs use equipment yet?
That bug around seemed to be around for years.

Re: Non-malf AIs die when remote controlling mechs, and mech is destroyed - oversight?

Posted: Mon Nov 07, 2022 8:13 am
by Imitates-The-Lizards
Rageguy505 wrote: Mon Nov 07, 2022 12:14 am Mech code is actually fucked. I don't think taking over the mech is supposed to be a last ditch effort, I thought it was a counter to some Durand punching it's way in.
From the wiki:

Viral Mech Domination (Costs 30 CPU): Allows you to hack a mech's onboard computer, causing you to shunt into it and ejecting any occupants. The usefulness of this ability depends entirely on the situation and whether or not the crew built a useful mech. If you're safe and all they have is a RIPLEY, you're better off staying in your core, but if you're about to die and the foolish roboticist built a fully armed and equipped Phazon, jump in and go for a joyride. Unlike shunting into an APC, dominating a mech is one way, and you WILL die if the mech is destroyed with you in it (and fail your objectives if it leaves the z-level), so make sure you're positive before you steal a ride.

So this behavior is clearly intended for malf AI, but, like I said in my opening post, it makes zero sense for non malf AIs using a control beacon, which should work exactly the same as an AI shell - shell dies, you just go back to core.

Re: Non-malf AIs die when remote controlling mechs, and mech is destroyed - oversight?

Posted: Tue Nov 08, 2022 10:38 am
by zxaber
Helios wrote: Mon Nov 07, 2022 2:28 am Can intellicarded AIs inserted into mechs use equipment yet?
That bug around seemed to be around for years.
Yeah, I fixed that a bit ago. All users can use the middle mouse button to toggle safety mode (disables equipment to prevent misclicks), and while the safety is enabled, AIs can use AI clicks.

Re: Non-malf AIs die when remote controlling mechs, and mech is destroyed - oversight?

Posted: Tue Nov 08, 2022 10:58 am
by Agux909
If you get inside a crate and the RIPLEY stores it, then gets destroyed, it will delete your mob. As said above, mech code sucks.