 |
Every time? I didn't notice this when I tested them earlier. |
 |
I have done some further tests. What tends to happen is that when slain, the bot gradually sinks into the floor, but some invisible part of it remains in existence and blocks movement. Item two: when hit with a sword, it produces a non-metallic collision sound. I don't know if this should count as a separate issue but here is is. |
 |
I'll add a test map showing a lanternbot death. Also, in my case, a lanternbot slain by an AI doesn't sink slowly into the floor. He drops out of sight, as if the floor opened up under him. |
|
|
I uploaded a test map, lb_dies.map. It includes a lanternbot and guard on patrol. Both on team 0, so they won't bother you. The carpet is under a trigger that will damage the bot as he crosses. The guard will lap the bot, so you can see when the guard walks across the carpet, he isn't blocked. He'll continue around the loop. When the bot crosses the carpet, he dies. The model lifts up off the floor and is immobile. When the guard comes around again, he behaves as if the dead bot isn't in his way, and he bumps up against it and his forward movement is stopped. He'll continue his walking animation, though. As if his forward motion has been transferred to the dead bot, the bot begins sliding forward beyond the carpet. Halfway to the far wall, he keels over and continues his slide until he hits the wall. He'll go halfway into the wall and stop, but the model continues to twitch. The guard is quite happy walking in place. You can walk up to the blockage and it'll stop you as well. If you bump the dead bot before the guard comes around, your motion is NOT transferred. The bot simply acts like an immovable object. |
 |
the af hasa been readded to the lanternbot .def that fixes the issue of the collision bering present after bot dies, it also fixes the floating/sinking issue. |
- Anonymous
