Just heard about this, is it true? And if so, what is a good alternative?
Depends, but if you are making a system that depends on the character state, its totally not recommended to use CharacterAdded because its called once when a player joins (based on my experience)
It is not bad, you just want to check if the character already exists
Like with everything, it depends on how you are using it.
If It can be replaced by something thats far more efficient, probably not a good use.
If its required for a specific task that requires that specific yield, sure you can use it.
It’s not bad. People just say it’s bad because they don’t see it’s uses. As long as you check the character exists first, it’s better than saying repeat task.wait() until player.Character.
local character = player.Character or player.CharacterAdded:Wait()
It’s depends on your task or function.
I dont think this is bad but i usually do this so it gonna slow my scripts a little bit to wait for everything to load
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.