I’ve stumbled upon a issue that I’ve somehow looked over from the few times I’ve tested a specific portion of my game. I’ve had issues like this with sounds, which from further inspection cloning sounds into a workspace can cause some frame drops. Though this issue seems particularly more unique; though this is my first game I’ve gotten the furthest with production, so keep the thought of my abilities as inexperienced.
I’ve done some tests in a fresh baseplate game, with an obvious result of not having any issues. The frame drops seem to be most prominent through the fact that server scripts that are running has a lot of traffic. Even when cloning through a separate script, it has the same result. Of course if I were to shut down all the server scripts and clone a UI Element multiple times, there’s no frame drop at hand.
Now the obvious solution I’m looking at for myself is having the UI Elements ready’d up to be altered whenever I’m in need of them. Though I’m curious if this is just what is expected of when building up a game in the later stage, or there could be something better I could be doing. I will say the most faulty way of tackling a ton of loops through one server script does exist. It updates anything within workspace that deals with loops. Though the forever loop runs at the default of task.wait() and whenever said items reach their cooldown, they update then continue the cycle. That’s probably the core behemoth of the frame drop issue, though even without it, the problem still persists.
Maybe I’m just bad at what I’m doing, but I’m not willing to give up easily, even if the solution is scuffed.