Not really. The only way to fix that would be to severely screw with the physics of it, which would just make it buggier. Think of it this way - if there's something stuck in the ground, it's hard to pull out with a rope. CC actors are always slightly stuck in the ground, so it ends up working this way. Sorry

Sure, I'll add that in later.

Yeah, I should probably fix that. It's not really intended for multiplayer anyway.

Unfortunately, this is just one of the things that CC does, and I have no control over it. Lua seems to make it worse, and I would guess that this is the problem (my test computer has 6 gigs of RAM so clearly it isn't a problem).

Huh. I'm thinking your computer would pretty much eliminate a large majority of lag crashes.

I got an issue once where Lua ran out of memory and did some weird ♥♥♥♥ and dropped movableman's actor tables.
EDIT:
With this as the only hacky mod runing at the time.

Except for the occasional crash, I am REALLY enjoying this mod. Be very careful when handling any braincase, as it will smash when you go one pixel too far.

I made the mistake of deploying this as my brain into my impenetrable mega doom fortress of epic size, which was already lagging. I had to put the computer out of its misery and pull the plug after it started making a loud WHIRRRRR sound and the FPS dropped to >0.1

This is probably due to the fact that my processor speed is 2.20GHz and my RAM a pitiful 512MB.

Basically; if your computer isn't some raging beast of processing, don't try putting this thing on a crowded map.

My biggest issue with this mod is the fact it'll cripple your machine EVEN AFTER CLOSING CORTEX COMMAND.

How much memory does it use??

Since CC is 32 bit, having 6 gigs of RAM doesn't actually do you any good. On 32 bit machines (running 32 bit apps, of course), any given process can access up to 2 GiBs of RAM, and on 64 bit machines running 64 bit apps each process can access 1.71798692 × 10^10 GiB of RAM.

That, good sir, is alot.

If you use the /3GB start swich, 3GB of ram can be used. Or atleast on windows.
EDIT:
Assuming the application has some flag that says it works with 3GB.

Regardless, there is definitely a memory leak. I'm going to do what I can to find which function is causing it, but there's a lot of code to sift through. Any help would be appreciated.

Cortex Command has a tendency to leave its process lingering and using up memory. Check your process list and see if there are any CC processes open.

EDIT: Upon further investigation, I may have been wrong. CC's memory allocation is odd - somehow, 5 seconds into the brain's creation, even with all Update functions commented out, memory starts rising. 10 seconds later it stops. I tried re-enabling the code and the same thing happens. Given that, it's certainly not the code causing problems.

Does it only start when the brain is placed? that would be odd, especialy since 2-player brains are allocated to a player once the game starts, brains can't use that much memory can they?

Yeah, been playing this since build 13. I terminate the process every time it crashes, I remember when it used to be so crude you had to kill the process even when cleanly shutting down the game.

The memory was STILL 'injured' even after that!!

Strange how, even when I got a dual core 2.0ghz processor and only a puny 1GB stick of ram, and even leaking ram at the point of using 70% of it (96% with windows processes) I don't get any kind of performance problems, and when I close Cortex Command the ram goes back where it should be, after 10 seconds within closing cortex command.
Also, I crash a few seconds after eveytime I right click with this brain unit selected, but it isn't a big problem since it's the only thing I need to kill my enemies
Also, don't fix the lasso tool, as it is like a interdimensional rope that makes everything dissapear after getting to a certain speed, and if used correctly it can make any puny piece of solid matter into a deadly airbust or crushing bomb.

The lasso is no fun. It doesn't work.

Make a tool that makes a black hole appear at the pointer.

And a tool that drops crabs, 4 teh lulz.

Maybe copy and paste cursors? The copy cursor will store the instancename of the selected item, and paste will spawn it, regardless of what you put it on. Should be fun exploding coalition's heads with dummy gibs.