Please refer to the official ROBLOX Wiki page on Network Ownership for further information on this topic. If you set the network owner of a part that is connected to other unanchored parts, those parts will also inherit the network owner change.You cannot set the network owner of an Anchored part.When the player leaves, the part is destroyed: local controlPart = Instance.new('Part') When the player enters, a part is created and assigned to the player. So all you need to do is get a server-side script to call SetNetworkOwner on that control part you mentioned: controlPart:SetNetworkOwner(player) By using BasePart:SetNetworkOwner(player), you can dictate what client should be responsible for handling the physics of the object. That is probably why your part seems to freeze up when it gets close to another player.Ī while back, ROBLOX added some helpful methods that allow game developers to override the default physics delegation that I described above. Therefore, if you have a part a player is controlling, the part might actually be physically controlled by another player's computer if it is closer. If no player is close, the server itself takes on the duty of simulating the part. This distance is based on where the player's character is in the game world.

When a part is physically simulated, the actual work of simulating the part is delegated to the closest client. (Mashed Bandicoot) You cant touch this Ocean man.

You can easily copy the code or add it to your favorite list. It’s one of the millions of unique, user-generated 3D experiences created on Roblox. I believe this is due to how ROBLOX simulates physics. Here are Roblox music code for Marshmello - BoUnCE Roblox ID.

Roblox touch to bounce