Steps to reproduce:
Easiest way is to create teleport using 2 parts which rely on Touched event. Then create 2 parts somewhere 1 wall and 1 floor sticked to eachother and in each of them put a script which only function is to subscribe for Touched event. Then teleport your player trought 1 teleport and try to touch at the same time the wall-floor combo.
Expected result: nothing weird happens
Actual Result: Player gets teleported back to the first teleport part location.
I think this is a bug in your engine, Touched event should be fired only for the parts that are touched and not for the others.
Expected behavior
I expect my character to stay on the same location where the 2 parts wall and floor are, and not to change its location to the first teleport part location.
This works as expected since you’re teleporting yourself to another location, which will fire the touched event. You aren’t putting the correct safeguards in place to make sure touched doesn’t fire in certain conditions.
You misunderstood what I meant. What I meant is that firing touched event for 2parts at once (doesnt matter if its teleport, gear giver or some other…) will trigger Touch event for the previous part that was touched (which shouldn’t happen). Imagine it that way you touch part 1, then go far away where you touch 2 parts at once. Touch event for the first part will be fired as well.
I’m not sure I fully understand the issue as described. To avoid any confusion, could you share a minimal repro project? It would be much easier to debug if I can see the exact setup you’re referring to.
Here is a video of the issue I recorded it doesnt let me upload it for some reason so there is Mediafire link to it 2026-02-02 20-54-46. I hope the video is good enough to show how to repro the issue. I will send you the code of the scripts as well
teleport1f code
local modelname = "teleporter1g";
local replStorage = game:GetService("ReplicatedStorage");
local teleportEvent = replStorage:WaitForChild("TeleportEvent");
local touched = false
function onTouched(part)
if not touched then
teleportEvent:Fire(part,script.Parent,script.Parent.Parent.Parent[modelname]);
touched = true;
end
wait(4)
touched = false
end
script.Parent.Touched:Connect(onTouched)
Touched1 code
script.Parent.Touched:Connect(function()
end)
Touched2 code
script.Parent.Touched:Connect(function()
end)
TeleportersManager server script.
local teleportEvent = Instance.new("BindableEvent",game.ReplicatedStorage)
teleportEvent.Name="TeleportEvent"
teleportEvent.Event:Connect(function(plrPart, sender, target)
print("Teleport operation started")
local teleportfrom=sender
if teleportfrom.Enabled.Value==1 then
local teleportto=target
if teleportto~=nil then
teleportto.Enabled.Value=0
local humanoid = plrPart.Parent:FindFirstChild("Humanoid")
local torso = humanoid.Parent.Torso
local location = {teleportto.Position}
local i = 1
local x = location[i].x
local y = location[i].y
local z = location[i].z
x = x + math.random(-1, 1)
z = z + math.random(-1, 1)
y = y + math.random(2, 3)
local cf = torso.CFrame
local lx = 0
local ly = y
local lz = 0
teleportfrom.Enabled.Value=0
torso.CFrame = CFrame.new(Vector3.new(x,y,z), Vector3.new(lx,ly,lz))
wait(3)
teleportfrom.Enabled.Value=1
teleportto.Enabled.Value=1
print("Teleport operation finished")
else
warn("Could not find teleporter!")
end
end
end)
From the video you can see that when I touch the 2 parts at the same time it teleports my character back to the first teleporter position which makes no sense, because there is no code that do that. I raised this issue because my main case was that when I touch button for buying gear giver and accidently touch the gear giver at the same time this happens again. So I made that experiment with touching 2 parts at the same time, after I touched the teleporter part before that and this triggered Touched event for teleporter part which should not happen
Thanks for sharing the video and code. After reviewing them, it’s still difficult to distinguish between your game’s custom logic and the actual engine behavior you’re reporting.
To help us investigate, could you please provide a minimal reproduction file (.rbxl)? It should contain only the bare minimum (e.g., just two parts and simple touched event scripts) needed to trigger the bug, without any of your other game code. This will allow us to isolate the issue much faster.
While trying to make repro game I couldn’t reproduce it only with 3 parts. Then I added the teleporters and the issue was reproduced even easier. My character teleports even when parts 1 2 or 3 are not touched by him, but maybe by some other parts. The question here is how teleporter script is able to get my character HumanoidRootPart, while no part of my character touched the teleports i.e they should detect HumanoidRootPart as nil. But here is the place please check it out and comment your observations. BUgRepro.rbxl (58.9 KB)
Thanks for the reproduction file. I’ve tested the place, but I couldn’t see the bug you’re describing. The Touched events appear to fire correctly for the parts the player interacts with. Teleportation only occurs when touching teleporter1f or teleporter1g, which is expected since those are the only parts containing the teleport logic.
try it several times, I just tried again and looks like it is not always reproducible. But I managed to reproduce it again now. Dont know why it is sometimes repoducible. In my game its a constant. In this test place it is not constant now. Strange engine behavior…
Hi! Turns out this is caused by an edge-case with the Humanoid physics logic. When you touch the unanchored part, the Humanoid is simulated by both the server and the client, since the unanchored part is owned by the server. When the server first starts simulating the Humanoid, its cached sensor data is in an invalid state and triggers a touch event on the green teleporter, which was the last cached touch event the server saw.
The fix is pretty simple, should have it enabled in a few weeks. Thanks!