For our combat system, we let the server take over the character’s physics to ensure that it’s the same for everyone & cannot be exploited. Recently, we’ve made the switch to the new constraint movers because they can be used without parenting to the instance directly.
However, for some unknown reasons, enabling a LinearVelocity which applies force to the player’s character, the network ownership returns BACK to the client!
Had anyone else encountered similar issues and, maybe, has a potential fix??? I’m out of ideas on how this could be fixed at this point.
(If the outline is grey, the server has control over the character’s physics, if it’s green - it’s the client)
UPDATE: It is specifically LinearVelocity that causes this issue, the other constraint movers don’t seem to reset the network ownership.