Scripting Helpers is winding down operations and is now read-only. More info→
Log in to vote
0
How many coroutines would you think is too much?
I'm making a game, and the way things are projected to go, and the way things are set up for now, there will be around...400 coroutines in the game. Half will be infinite loops, the other half are coroutines are also loops but they act only when a value is true.
Is this too much? Like for performance-wise. I don't mean in general, because, well, 750 is a LOT. But performance is my main issue. I would like answers, and if this doesn't belong on here, I'm sorry, but I am not allowed to have a DevForum account for the time-being.
0
69 greatneil80 2647 — 3y
0
The coroutines' performance really depend on how heavy/optimized and how active the function(s) you want to coroutine.new() would be. I don't really think that would be a bad thing to have many coroutines, especially for something simple as your use case, although I would instead use one function and connect to multiple Value.Changed events instead, if that's what you are trying to do.. Y_VRN 246 — 3y