"Triggered" function is repeating several times

Help and Feedback Scripting Support
#1

Every time I trigger a Proximity Prompt, the function is repeating several times. Does anyone know, how I can do, if a player triggered a Proximity Prompt, the function will only work one time?

#2

add a debounce some like
local a = false

if not a then
a = true

a = false
end

#3

Do you know, how I can do, that every single player has her/his own debounce?

#4

I’m guessing you may need to disconnect a function

#5

grafik
grafik799Ă—253 29.7 KB

Do you mean smth like this?

#6

are you handling it on the server ?

#7

You have to disconnect the function outside the function

#8

mmh still doesnt work:

grafik
grafik729Ă—252 28.9 KB

#9

As in it’s executing multiple times or not executing?

Edit: I misread the code mb. Disconnect the function after everything that should be triggered has been triggered.

#11

srry, I do not really understand what do you mean

I got this now?
grafik

#12

grafik
grafik765Ă—256 30.4 KB

btw this code doesnt work, srry for telling so late, I tried it with print

#13

The issue is that the connection is supposed to end when all of the necessary code has been executed. When you assign a function, the block of code will be ignored and disconnected before it can be triggered in this case

#14

Check if the function has been fully executed and disconnect once it’s done.

local finished = false
if condition then
    finished = true
end
while finished == false do --don't execute the following code until finished
    wait(0.1)
end
triggered:Disconnect()

This should work but it’s not ideal. Create your own verification to check if the code has been fully executed

#15

make a table, as triggered returns the player set the players debounce in the table

example:

local global_debounces = {}
prompt.Triggered:Connect(function(p)
   if global_debounces[p] then return end
   global_debounces[p] = true
   task.wait(--[[change how you like]])
   global_debounces[p] = nil --I am setting it to nil as I dont want to store a useless "false" value
end)
1 Like
#16

Won’t this cause a memory leak

#17

how? please explain. This would not cause a memory leak as the entry of the table called “p” is removed with nil when the debounce ends, when there is no debounces the global_debounces will be same as a empty table.

there is a reason why I said “useless false value”

#18

I’m assuming OP has put this function within another function, hence the multiple executions

#20

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.