Is :WaitForChild() tied to legacy like wait()?

[GreekForge]

I’ve noticed a whole lot of talk on “wait()” being legacy, stuck behind a 30 hz loop, and unstable. But what about WaitForChild(). If it is and should be avoided then what alternatives can we use?

[ReturnedTrue (Raiden)]

This tutorial talks about bad practices of WaitForChild:

FindFirstChild and WaitForChild: Addressing common bad practices and habits of each

Please do keep the following in mind before reading or linking! Some parts of this thread provide slightly inaccurate, unnecessary or outdated information. You are strongly encouraged to read the replies for further discussion about FindFirstChild and WaitForChild and their use in code, as well as some pointers on replication. I have not yet found a time to correct potential misconceptions in this thread. It does not provide authoritative advice and you should always double check information …

In my own opinion, I wouldn’t class this as legacy afterall making your own adaptation would possibly be less effecient than WaitForChild itself.

[sleitnick]

I don’t believe it is. My assumption is that it’s more-so tied to the event :Wait() method, since it’s probably using that sort of direction to await children being added.