I know the thingy says that M7s (the android type) are supposed to have a "limited battery life" and whatnot, but the SM7s seem to have a weird glitch where they aren't recognised as androids at all--they refuse to sit in upgrade stations (even if you declare one the owner), and nothing in the description (when you're making the dumb expensive-ass thing) says that they're meant to be temporary.

I can have a pawn jump into the body and force it to charge at a station, but that's about it.

Weirdest thing is that I found this out because I got a "That super-expensive surrogate you haven't used yet just died of {weird message about being hacked or something}" in the middle of a black-out, and I assumed it was a glitch so I jumped back to the last auto-save (I'm all for owning my mistakes but I won't abide a glitch), and found that the SM7 was dying from "EXTREME STARVATION"--with a battery/hunger meter still at about 70%.

I just "rescued" it to a hospital bed (after spending about 2 hours trying a dozen different ways to get it in an upgrade station), and it just... survived as though it had been actually starving and then fed when I put it in the hospital bed. A few hours later it was able to walk around, and I could charge it at the station.

So I have no idea how the crap this thing is supposed to work, but whatever it's supposed to do, it's doing wrong:

- If it's meant to be a completely disposable buff that constantly degrades and will die after a set amount of time no matter what, then you REALLY need to say so, with absolute clarity, in the research screen, and on the build order description.
--- Also, if this is the case, then you shouldn't be able to recharge it.
--- Plus, the "hunger" of the pawn should reflect the time remaining (and possibly have a different label so that users know it can't eat?)
--- Plus, the "Starvation" status should have another name ("Power cells deteriorating" or something), as "Starvation" means something completely different form what's happening.
--- Plus, rescuing a starving/deteriorating unit shouldn't reset its life cycle.
--- Plus, you may want to consider reducing the price a little, as it currently costs about as much as 2 permanent S4s or 3-4 permanent S3s, for something that's supposed to die in a few days.

- If the surrogate version is meant to be an in-case-of-emergency monster that runs out after a certain amount of use, then you shouldn't be able to recharge it.
--- Plus, it shouldn't drain/starve when not in use.
--- Plus, if it's meant to be used in multiple battles, then it should be able to use the upgrade station to undergo repairs between fights. (But the upgrade station shouldn't recharge it either.)
--- Again, if this is the case, then there should be a description somewhere in the build order, to make sure that peoples' expectations are set.

- If the surrogate version is meant to be permanent, then there are a few issues to fix:
--- Everything.
--- Well, they connect fine, and they work as-intended combat-wise, but they can't eat, they can't use the right beds, and they would rather reassign their beds to a hole in the ground than get first aid on an upgrade table.

I'm assuming the same thing applies to the S-HU as well--but I'll be damned if I dump the resources into trying.

TBH the build order descriptions need to be updated anyways. "Creates an surrogate android" is... not helpful. At the very least it should mention that it comes with a cannon so that you don't end up wasting even more resources building a new one.

Once I know what it's supposed to do, I'll chuck something in the bug thread.