Let's say I have 200 doors and I want them tweened, would it be better to create a tween for each door, so having around 400 tweens stored in variables at all times and just being able to play them at any time, or would it be better for performance to have a main script create a new tween for a door when it is needed? Also why?
✓ ANSWER ACCEPTED
Quick questiong about performance regarding tweening?
1 answer
✓ Accepted answer
There is some issues if there are too many playing at the same time. The only way to fix this is putting the players on your game as low as 10 to 15 players.
This discussion is preserved as it was. New answers, comments, and votes are closed.
5 comments
I'd recommend using a ModuleScript to holster one tween for all the doors that do the same thing, as this will decrease memory usage and the script won't run until the function is being called.
If you use one tween, how would you deal with the first parameter, the instance?
You can create a function for the tween, with pre-setup tweens, and the parameter can be the part that you're trying to tween.
So basically a function that passes the instance, then everything except the :Create part is already setup? So I create a new tween each time with :Create but tweeninfo and properties is already setup?
Sort of, the only thing you're changing is the position, like another parameter for the function can be the position you want it to tween.