#custom events only fire once

1 messages · Page 1 of 1 (latest)

velvet ermine
#

I've made a devforum post, but replies here help too
read the post: https://devforum.roblox.com/t/custom-events-only-fire-once/2648088

Developer Forum | Roblox
Custom events only fire once

Now, I have created a custom event for my module. However, it only fires once. Sure, I could use connections. But that would mean the person using the module would also have to implement a system to manage these connections on their end. How can I make it so that the events fire multiple times until disconnected? Example of what I mean: local ...

exotic pulsar
velvet ermine
exotic pulsar
# velvet ermine ???

https://devforum.roblox.com/t/custom-events-only-fire-once/2648088/2

Developer Forum | Roblox
Custom events only fire once

Look, the problem is not with your event, it’s with your chat command. Players’ chat is firing multiple times but the code that fires your event is inside the if statement which is checking if the message is equal to “test”. So, It will fire the event once if you type “test” once, it will fire twice if you type “test” twice and so on. Here is y...

#

looks like the guy has fixed it and got no issue

#

this ```lua
local t = {}

local function createEvent(eventName)
local event = Instance.new("BindableEvent")
event.Name = eventName
return event
end

local myEvent = createEvent("Example")
t.CustomEvent = myEvent.Event

local function playerAdded(player)
player.Chatted:Connect(function(message)
if message:lower() == "test" then
myEvent:Fire(player.Name.." said test!")
end
end)
end

game.Players.PlayerAdded:Connect(playerAdded)

return t

velvet ermine
#

Did you even read the whole post?

#

I said that that was an example.

exotic pulsar
#

According to the example provided, which should be the “custom” events at play.

#

And so with this current information there is absolutely no issue with the example.

velvet ermine
#

Post 4 has my issue.

exotic pulsar
#

Most won’t read that long script, including me

vernal smelt
#

I haven't looked into the script, but maybe your firing the ".Event" thing instead of the actual bindable event?

#

Sorry if this didn't help.