Moveto() server delay

[oh_Wal]

So I have a script on the server that makes npc, follow around a player:

	while true do		
		local target = character.PrimaryPart

		bodyGyro.CFrame = CFrame.new(cloneRoot.Position, target.Position)

		local targetPositionBehind = target.CFrame * CFrame.new(0,0,offset)
		cloneHumanoid:MoveTo(targetPositionBehind.Position)

		wait()
	end

is it possible to reduce this gap / delay between the clones and the player?

[iATtaCk_Noobsi (Noob)]

You can try setting the characters that are following the player HumanoidRootPart networkownership to the player

NPC.HumanoidRootPart:SetNetworkOwner(player)

Now that I think about it I think you’re gonna have set networkownership of all the NPC’s baseparts to the player…

[EDIT]
Don’t do this, it wont work

[KainagamerTigre]

local pathfindingService = game:GetService(“PathfindingService”)

local function setNetworkOwnership(npc, player)
for _, part in ipairs(npc:GetDescendants()) do
if part:IsA(“BasePart”) then
part:SetNetworkOwner(player)
end
end
end

local function followPlayer(npc, player)
local humanoid = npc:FindFirstChildOfClass(“Humanoid”)
local root = npc:FindFirstChild(“HumanoidRootPart”)
local target = player.Character and player.Character:FindFirstChild(“HumanoidRootPart”)

if not humanoid or not root or not target then return end

humanoid.WalkSpeed = 20 -- Aumenta a velocidade de resposta
humanoid.HipHeight = 1.8 -- Evita travamento em obstáculos pequenos

setNetworkOwnership(npc, player) -- Reduz atraso do servidor

while task.wait(0.1) do
    if not target.Parent then break end -- Se o player morrer, para o loop

    local path = pathfindingService:CreatePath({
        AgentRadius = 2,
        AgentHeight = 5,
        AgentCanJump = true
    })

    path:ComputeAsync(root.Position, target.Position)

    if path.Status == Enum.PathStatus.Success then
        for _, waypoint in ipairs(path:GetWaypoints()) do
            humanoid:MoveTo(waypoint.Position)
            humanoid.MoveToFinished:Wait()
        end
    end
end

end

– Exemplo de uso:
local npc = game.Workspace.NPC – Substitua pelo caminho correto do NPC
local player = game.Players:GetPlayers()[1] – Pegando um jogador aleatório

if player then
followPlayer(npc, player)
end

[Frostice2013]

use a RunService connection instead of while true do. maybe .PreSimulation, .Heartbeat or .Stepped will work, you can find more on RunService here

RunService | Documentation - Roblox Creator Hub

also use task.wait() instead of wait(). many statements have been said on the implications of using wait() which makes it actually hold for double the time you asked it to hold for on some instances as said here

Task.wait(n) vs wait(n)

No. Definitively not, task.wait is definitively better. The differences with wait and task.wait are: wait() can sometimes delay when it resumes the thread because of performance concerns, which is actually bad because you will rarely have those because of it task.wait() updates 2x faster than wait(), therefore more accurate Also: Just note that task.wait, just like wait is still a code smell, usually indicates a bigger structural problem with your code.

if you ALSO really wanna make sure that task.wait() is better preferred over wait() i quote this in the roblox developer documentation:

@Roblox Developer Reference

Unlike the deprecated global wait, this function does not throttle and guarantees the resumption of the thread on the first Heartbeat that occurs when it is due. This function also only returns the elapsed time and nothing else.

see for yourself

task | Documentation - Roblox Creator Hub

[rman501 (crit)]

If you want an instant reaction, you must develop a system around SetNetworkOwner

However, there are other things that are useful to keep in mind.

For example, you can create a unit vector of the players velocity and multiply it by a length to make the AI predict where the player will move. This will make the AI appear to have less delay.

There is not exactly a perfect way to deal with this problem.

The larger issue is that going between clients/server ownership seems to bug the Humanoid.MoveToFinished event (makes it lag). Which makes the solution in almost all cases undesirable :/,

For most use cases, set the network owner to nil (the server) if its multiplayer in any form.