How do i make a part move to a player (5 studs above)

[AlaTomKing (Tom)]

@Vortexuel560 Also please mark my first answer as the solution because it provides the snippets and the further consideration which you have missed.

[Vortexuel560 (Bungar)]

i did mark it as answer
char limit

[AlaTomKing (Tom)]

I meant this:

How do i make a part move to a player (5 studs above)

I have edited my scripts again. And I tested it; It works. local object -- path to object local runService = game:GetService("RunService") local offset = CFrame.new(0,5,0) -- set this to anything you want local alpha = 0.3 -- same with this one local targetPlayer = game.Players:WaitForChild("AlaTomKing") local character = targetPlayer.Character or targetPlayer.CharacterAdded:Wait() local Head = character.Head object.CFrame = (Head.CFrame * offset) runService.Heartbeat:Connect(function() --p…

This is the first answer that I have shared which provides the solution. I might add on the explanation on this answer later.

Thank you.

[AborayStudios]

task.wait() is 60hz wait() is 30hz, a while loop is while its conditions are true, so no they aren’t the same

[VegetationBush (FartedWayTooHard)]

Small correction here.

task.wait() waits one frame. It’s not a static value. If the user is running Roblox at 120 frames per second, task.wait() will also fire 120 frames per second. Conversely, if the user is running at 30 frames, only 30 resumptions will occur per second.

[AborayStudios]

task.wait() uncap is on the roadmap, currently it’s capped at 60hz and tied to heartbeat. roblox is capped at 60fps.

[VegetationBush (FartedWayTooHard)]

It’s important to be specific about behavior. You can already change the FFlag for framerate with apps like Bloxstrap (which has been a thing for quite a while). Even disregarding the FFlag, making a statement that it’s only 60Hz is slightly misleading.