If math.abs(relativePosition.y) < boxBoundary. See Debounce Patterns for strategies on improved collision handling. This can lead to undesirable behavior in a collision scenario.

For instance, for a rectangular area, you may use: if math.abs(relativePosition.x) < boxBoundary.x then part.Touched:Connect (onTouched) The Touched event can fire multiple times in quick succession based on subtle physical collisions which may not be apparent during testing. If math.abs(relativePosition.x) TanTen * math.abs(relativePosition.x) thenĪs you may notice, that my touch volume is a pie geometry that it has certain radius and certain linear boundaries, but you can easily custimize your boundaries. Local relativePosition = playerPosition - NpcPosition Now for an additional sanity check I have created this helper function, and it was checked everytime a touchEnded event was triggered, where: - This tells if the player still is inside the interactive volume Fire remote events that player is in sightĪctionRemoteEvent:FireClient(player, 'Exit') If not NpcGreetingsTrack.IsPlaying and not NpcWavingTrack.IsPlaying then Assigned the player to the debounce table And here is my solution: In my regular touch end check events there is: - This manages on touch end events local function onTouchEnded (hit) - Get hit player and check its humanoid local player game.Players. Where a player jumps it triggers the TouchEnded events. Local humanoid = hit.Parent:FindFirstChildWhichIsA('Humanoid') Actually it is a very common 'jump' issue happens in the touch zone. Local player = game.Players:GetPlayerFromCharacter(hit.Parent) It’s one of the millions of unique, user-generated 3D experiences created on Roblox. In my regular touch end check events there is: - This manages on touch end events Actually it is a very common 'jump' issue happens in the touch zone.

Roblox touch to bounce