Why does the touched function activate more than once? even outside the function

[Rewlaxe (Lazar)]

today I work a lot on my combat system that I manage to do better and better, but I meet a big problem why its print “a” several times

function playerHit()
	local partCollider = colliderArray[newIndex]
	local basePart = character:FindFirstChild(partCollider.Hit) :: BasePart
	local animation = Instance.new("Animation")
	animation.AnimationId = partCollider.AnimationId

	if countDownDebounce then
		local animationTrack = humanoid:LoadAnimation(animation)

		animationTrack:Play()
		countDownDebounce = false
		
		if basePart then
			basePart.Touched:Connect(function(hit)
				if hit.Name == "HumanoidRootPart" and hit ~= humanoidRootPart then
					print("a")
				end
			end)
		end

		animationTrack.Ended:Connect(function()
			countDownDebounce = true
			SetNewIndex()
		end)
	else
		return
	end
end

mouse.Button1Down:Connect(function()
	playerHit()
end)

[windowsvxstauser (ToIMLiker851)]

Touched events are really buggy and don’t have a cooldown or debounce

use a variable to fix this, set it to true or false depending on what you wanna do

local deb = false
if basePart then
			basePart.Touched:Connect(function(hit)
                if deb then return end
                deb = true
				if hit.Name == "HumanoidRootPart" and hit ~= humanoidRootPart then
					print("a")
				end
			end)
		end

[Tomi1231 (Chilly28)]

Touched can fire twice because of this reason

Touch Events and Network Delay

This article outlines some internal functionality of Touched and TouchEnded event replication in the distributed physics engine, with the goal of helping you understand how to approach touch event scenarios in your Roblox experiences. To get the most out of this material, you should be an advanced developer who’s familiar with network replication delay. Example Scenarios Server/Client Async Scenario In one example scenario, a server script has Touched and TouchEnded event listeners for a Pa…

.Touched isn’t only fired by the instance that owns the part, in this case, PartA is owned by client1, but it will still make a .Touched event for PartB, even though it doesn’t own it, and another client is replicating the .Touched event

It works in a weird way… Imo, only the instance owning the part should be able to do a .Touched event for that part