I haven’t had a problem with not using it in this scenario. Generally, WaitForChild is used in cases where you’re not sure that the instance won’t immediately be there. For example, if you encounter an error such as 'x' is not a valid member of 'y', you should consider using WaitForChild. However, if you’re 100% sure that it will not error, using x:WaitForChild(y) is actually slower than x.y. Also, if you find yourself repeating WaitForChild calls (eg. a:WaitForChild(b):WaitForChild(c):WaitForChild(d)), I highly recommend this module: WaitForPath: A Solution To Endless WaitForChild Calls.
2 Likes