player.Chatted firing twice

Help and Feedback Scripting Support
#4 
local debounce = false

Player.Chatted:connect(function(Message)
	if debounce then
		return
	end
	debounce = true
	print("CHATTED!")
	--ignore rest of code....
	task.wait(1)
	debounce = false
end)

What about this?

#5

It still fires twice:

#6

That’s weird, are you sure you don’t have the same script copied in 2 different locations?

Press CTRL + SHIFT + F and use the global script search to search for “chatted”.

#7

I already made sure of that:

#8

I tried looking around the forum for others who’ve encountered similar issues but this is a first it seems.

#9

I managed to find this one: Script Firing Twice When It's Only Supposed to Fire Once

#10

Thanks for linking, I’ll take a quick look.

#11

So the lines that I originally mentioned were in a bigger script with a bunch of other functions. So I just tried to put the lines I mentioned above into a new local script with no other lines of code and the output was normal.

#12

I’m guessing not but do you have any custom chat systems in place?

#13

No, only a small system for roblox buble chat, I destroyed that tho and used roblox’s normal system and the same thing happend.

#14

If you had the “Chatted” event in a loop before (which ran twice) then the connected function would execute twice as well. In other words you’d be connecting 2 separate closures (functions) to the “Chatted” event, which when fired would result in both functions being executed.

#15 
for i = 1, 2 do
	player.Chatted:Connect(function(msg)
		print(msg)
	end)
end

This is what I’m trying to refer to. Obviously it won’t be that obvious in your script (but I can only assume this is likely what is occurring).

#16

798×504 85.9 KB

1 Like
#17

Can I see the definition for “Message”?

#18

I think its built into the function, right?

#19

Oh, you’ve collapse the function, can you expand it by clicking the arrow?

Also “:connect()” is deprecated (not necessarily the issue) but “:Connect()” should be used.

#20

968×691 140 KB

#21

Where do you define Player? The only possible problem is that you have wrote multiple connections to an individual Player’s Chatted event, or that you have wrote multiple connections to PlayerAdded.

#22

These are the only 2 times “player” was referenced before the chatted code.

#23

I assume player will just be a simple “game.Players.LocalPlayer” at the top of the script.