Guide to event-based programming and why it's supreme

Resources Community Tutorials
#2

Cool and all, but why are the codeblocks so badly formatted?

#3

Because Roblox won’t let me indent when making a post

#4 
while true do
    local parts = myPart:GetTouchingParts()

    if #parts > 0 then --//A part was found in the table returned, so we know something is touching our part
        workspace.Baseplate.BrickColor = BrickColor.Black()

        break
    end

    wait()
end

Doesn’t stop you from pressing space or using a tool such as

Just a suggestion because new programmers look at these and they should be written in proper code syntax as to ease readability.

#5

That tool doesn’t work for me, and yeah it’s weird how you can’t use tab on here. I also don’t feel like spamming my space bar 10 times per line.

5 Likes
#6

I’m a little confused by this, could you possibly show a code example of what you mean? Thanks!

1 Like
#7

Is this right? According to the wiki, a BindableEvent can only be subscribed to by one script:

d07fe4863451d4804bfb2e0cdb5c03a1
d07fe4863451d4804bfb2e0cdb5c03a1879×155 11.5 KB

I couldn’t find any clarification of what “Subscription” means in this context, but I took it to mean a connection to the event, so you can only connect one function to a BindableEvent at a time

#8

Ahem ahem. BindableEvents can be connected by unlimited scripts.

BindableFunctions only by one.

1 Like
#9

yeah I tested it out and I could connect as many scripts as I wanted. do you know what it meant by the subscription limitation then?

#10

Perhaps I didn’t do a great job of wording that.

Basically like, I’ve found it being better practice (for me personally) to put something like this within your ModuleScript’s environment:

function myModule:Init()

someBindableEvent.Event:Connect(function()
--//Do stuff within this module
end)
end

Versus explicitly running a bunch of module methods when an event occurs:

--//Regular script

someBindableEvent.Event:Connect(function()
moduleA:Cleanup()
moduleB:Cleanup()
moduleC:Cleanup()
end)

Both work obviously, I just personally prefer the first option because it feels like you have more control.

1 Like
#11

Probably just how many scripts can connect

#13

Great tutorial, but bindableEvente are outdated because they can cause memory leaks if not used correctly.

1 Like
#14

You’re using them wrong then. A event wrapper instance (aka bindableevent) cannot cause a memory leak on it’s own.

1 Like
#15

It can, if you pass in any value that isn’t pure Lua, garbage collector wouldn’t be able to collect it.

#16

At least provide valid stats if you want people to not use bindables all together. I’m not reading a long post that doesn’t mention memory leaks you mentioned.

#17

It does.

RobloxSignal uses BindableEvents to make custom events.

#18

Cool but you still don’t show any stats showing that it does indeed memory leak in that way.

#19
#20

I don’t understand how that is related to bindables memory leaking – it doesnt describe how they leak, nor does it provide stats that I’m literally begging for you to show.

#21

I am new to this so I can be wrong unless you can correct my flaws.

#22

Don’t say anything if you can’t provide anything to prove your point then. Do some research before posting.