its great to know that disconnecting a listener destoryes the already made threads,
but what if im using the remotes to update information about the clients every once in a while? for example i have a table in module script that has all players information like if they are attacking or blocking an attakc…Etc, so im using a remote event to Update this table every once in a while but i dont want the threads that has been created to stack up? so how should i go about this?
i mean i want to destory the threads after they finish excuting.
what i meant is that i dont want to disconnect the listener since i need it to update information on the server but at the same time when it fires it creates new thread so is there a way to destory the threads without disconnecting the listener?
in other words destroy the thread once it finishes excuting without the need to disconnect the listenrer
Just a quick FYI, roblox doesn’t support anything in parallel (like multithreading), it simply switches from one task to another, but it only switches when the current thread yields. But what you’re referring to is a completely different thing. Starting a new connection don’t create a new thread, because they are two different things
listeners do create new threads, and about if Lua supports anything in parralel or
not then I’m not sure about it, still need to do my research but i guess your right about lua not supporing parallism since i read couple topics a while back talking about it
Luau is actually live in studio, but not live in real games. Luau is still unstable and the goal is to boost performance along with backwards-compatible with current Lua.