Chopinator damages itself?

[Tarciryan]

Hello all, nobody seems to have mentioned this and I can't figure out what's doing it.

When I have some chopinators set down, sometimes they start to take constant damage, but only when a mob comes into range. After the mob is dead (and body removed) they still take constant damage.

I have made sure each chopinator is away from each other, and not clipping into terrain etc. I have no idea why it is happening?

[burger boy]

interesting, it may be related to an past bug.
-- the bug was, that upon having an object placed on them ( an makeshift wall light for example ) the choppinators would begin to break down.

that past bug, along with how the choppinator takes damage when it manages to hit something while activated, may be the cause of this issue.
-- best to send in an bug report via the bug reporting form, and if you can, with an recording of it happening in action.

[Kikinaak]

Is this actually a bug or intended? Think lawnmower blade, it gets dull as it works and needs sharpening, taking out dings from rocks, etc.

[Shirumic]

I've seen this happen after a chopinator killed a security bot, it'd continue to be damaged as if it thought the security bot was still there, even though, by this time, I kept repairing it and it already destroyed the security bot.

This persisted even after leaving the area and coming back, and I had to eventually pack up and redeploy the chopinator.

[MechWarden]

This has been going on ever since I started playing in the 2nd playtest.

A bit surprised to see this still happening.

[Caramell Sundoffe]

I'm pretty sure it damages itself because it's still "hitting" something like a corpse, I've watched it's health deplete until the robot I choppinated got gibbed.

[Jartym]

Originally posted by Caramell Sundoffe:

I'm pretty sure it damages itself because it's still "hitting" something like a corpse, I've watched it's health deplete until the robot I choppinated got gibbed.

I consistently see it continue taking damage even after the robot's entire body is destroyed; I didn't even know this wasn't intended behavior. I wonder if the scrap and other pickups could be causing it. I'll go test whether it stops after everything is collected.

Edit: After 2 tests, I can say that it actually does stop, but only about 5-8 seconds after the remains of the robot are destroyed (regardless of litter), which I'd never previously let continue running that long before.

[Teacyn]

I can confirm this happens with anything you use the chopinator to kill. It seems to "queue" damage or something strange like that, and keeps taking it for several seconds after. I've also noticed strange behavior with robots specifically where it seems to cut them up before their death animation can finish, causing them to instantly explode after.

[scavenger]

Been curious about this since started using the chop bot method. Was confused on why it took damage despite not actually getting hit by the bot.
Had a few cases where it did do a attack but would for some reason attack partially behind it. But otherwise just kept walking into it.

[MechWarden]

Enemies do have a simple priority system. If given nothing else to attack (like you or any other player), most enemies will attack what you placed. If you are noticed, they will often stop that and head towards you. It's pretty easy to kite security bots into traps because of this priority system. The enemy behaviors are still very simple.

Also, some attack animations have been a bit jank, with the thing facing the wrong direction and attacking, or on rare occasions even doing post humorous attacks. It is pretty annoying to drop an Order Solider, only to get a few more bullets in the face after he has already hit the ground.

[scavenger]

I have actually had that happen several times which did sorta irritate me. Hope that gets fixed eventually because seems a bit unfair for when you kill a group of soldiers only for one to get that bug and you just get faceblasted with beyond the grave shots.

[Shirumic]

Hoping a dev sees this, it was annoying having to figure out what was going on with my chopinator