I’m working on Knit Framework (0.0.18-alpha) and I found a problem:
It says that game.ReplicatedStorage.Knit:WaitForChild(“Services”) is an infinite yield, but I never touched the module at all, did I make a mistake?
There’s not enough information here. Did you just add Knit to ReplicatedStorage and then require it? What is the code that’s requiring this script? Please add more information, just seeing the hierarchy of Knit isn’t enough to help you.
1 Like
I apologize, I forgot to mark this as solved.
I had completely forgot about initializing Knit on Server.
You know you can’t just do that right. First you need to load all of your services and then it isn’t even guaranteed its finished loading yet. That’s why in knit lets you have KnitStart and KnitInit in modules script. In KnitStart all other services are guaranteed to be loaded.
1 Like
Yes, I know, I resolved the problem
This is incorrect - the actual problem is that OP forgot to initialize Knit on server which didn’t create the services folder. Loading services in the case of Knit doesn’t mean waiting for the actual instance (the module script) to exist.
1 Like