Problem with server only parts physics

Help and Feedback Scripting Support
#1

idk why this occurs but when parenting things to workspace.Camera from Server
the thing ends up eventually after about 3 minutes just stops working completely like the server realised its not replicated so decided to stop moving it why is this the case ?

for example you make a part go back and forth on the server parenting to the workspace.camera after about 70-100 seconds it stops working you can try it your self
here: just place script in SSS

you need 2 anchored non collidable parts in workspace .
check in output but eventually the part stops moving
could somebody explain why ?
this occurs with anything even with model:MoveTo
eventually it breaks and server stops throwing any resources at it and completely ignores your code like its having a disagreement with me XD

local Box = workspace.HumanoidBoxBF:Clone()
Box.Parent = workspace.Camera
Box.CFrame = workspace.Part1.CFrame
local BV = Instance.new("BodyVelocity")
BV.Parent = Box
BV.Velocity = Vector3.new(0, 0, 0)

local targetPosition = workspace.Part2.Position
local speed = 24 -- Adjust this value to control the speed of movement
local Direction
local Count = 0

while task.wait(1) do
	local currentPosition = Box.Position
	Direction = (workspace.Part2.Position - currentPosition).Unit
	BV.Velocity = Direction * speed
	Count += 1
	print(Count)
	
	task.wait(0.5)
	
	local currentPosition = Box.Position	
	Direction = (workspace.Part1.Position - currentPosition).Unit
	BV.Velocity = Direction * speed

end```
2 Likes
#2

Having the same issue recently, no found solutions yet.

#3

If you’re working with unanchored, unreplicated parts, you’ll need to explicitly set their network ownership to the server by calling BasePart:SetNetworkOwner(nil). If you do not do this and leave the ownership as automatic, the server may give ownership of the part to a player. Because the part is not replicated, that player’s client cannot simulate its physics, so the part stops moving.

A player’s influence on automatic network ownership assignment is very weak when they first join the game, so that’s why it works for a while but then eventually breaks.

1 Like
#4

Thank you so much! This is the solution :grin: