Not a fan of each frame nearestObjects, but it's not like you're carrying stuff all the time.

The array _disabledCollisionObjects should be stored on the object and not on the PFH. That way dropObject_carry can be called from everywhere.
I also don't see this ever being executed on the remote machines. Does it even work like this in MP?
Why is it not done for dragging?

I suggest making an independant framework for disabling collisions of an object with everything that works in MP and handles JIP.

The array _disabledCollisionObjects should be stored on the object and not on the PFH. That way dropObject_carry can be called from everywhere.

Good point.

I also don't see this ever being executed on the remote machines. Does it even work like this in MP?
Why is it not done for dragging?

Dragging doesn't cause collisions like that, I am pretty sure it's because I was testing with a small object, should try something bigger to make sure.

I suggest making an independant framework for disabling collisions of an object with everything that works in MP and handles JIP.

👍

Dragging doesn't seem to be a problem at all (unless you release the object inside someone).

I still need to test how locality works on that command.

Yeah, globally and rerun on each locality change of either object. It seems like I won't have much time to work on this, setting to 3.12, can change back if I do it this weekend.

box setMass 0.000000000001;

This works in local hosted MP. Client can't damage another client or the host. Mass has be set to >0 however, but that seems to be enough.

Tested, works in MP.