Why is the NetworkOwner randomly changing to server after being assigned to a player?

[straykevin (owq)]

Even though I set :SetNetworkOwner to the player on the server, for some reason, midthrow, the server decides it wants to control the physics, causing the jittering motion. Any Ideas why this is happening?

There isn’t anything happening on the server-side code that changes anything related to the part’s physics.

[Ethanaut]

Hello!

So in this post someone talks about their code setting align orientation to nil and that error forcing server control on the instance.

But the error is not displayed, also I am worried your problem might be what the people at the end of this thread were talking about and not what the OP here ended up solving.

Network Ownership being forced back to the server

I’ve got this mount that I give the client network ownership over so they can control it. The mount is an assembly I move via a BodyVelocity & AlignOrientation entirely on the client. When it makes a collision with an object controlled by the server or another player causing the assembly’s to intersect (because of network delay) resulting in the assembly jumping up out of the other one. About 10% of the time when this happens the server will re take control of the assembly leaving the client n…

[straykevin (owq)]

Thanks! I thinking I guess I’ll just go with the assumption that any minor and unintential action can result in the server securing ownership.

So a loop with :SetNetworkOwner it is