Teleporter teleports all players at once, even if it's supposed to teleport only one player!

[dthecoolest]

See this tutorial which describes the issue very well with touched events on the client.

@colbert2677

Wait - other clients see my actions!

Which is the point of this thread! Understand this: the connection you establish using the above code is still local . With the way Touched works however, that means that the client is actively monitoring any part touches. It’s not that there’s any replication going on here: the client sees that a part touched something and so the signal is fired.

In order to prevent other clients from seeing your actions, you need to verify within the function that the part that touched the object is part of the player’s character. This is only if you’re making local interactions, such as showing shop interfaces like the example a ways above.

To check a part’s association with the character, we simply need to run IsDescendantOf. If you consider the parent-child hierarchy for Roblox instances, we can use this to check if the part is part of the character’s ancestry.

local LocalPlayer = game:GetService("Players").LocalPlayer

shopPart.Touched:Connect(function (part)
    -- Let's check that a Character is valid as well
    if LocalPlayer.Character and part:IsDescendantOf(LocalPlayer.Character) then
        print("Our character touched the shop part!")
        shopGui.Enabled = true
    end
end)

And just like that, you’re set! It’s all about verifying that the touched part is part of the LocalPlayer’s character, if one exists,