Knit.Start isn't working

Help and Feedback Scripting Support
#1
  1. What is the issue? Include screenshots / videos if possible!
    knit:KnitInit does work but Knit.Start isn’t working and it doesn’t run
  2. What solutions have you tried so far? Did you look for solutions on the Developer Hub?
    I have tried making a simple knit and still theres a problem and tried moving it into a new baseplate it worked the first time then it stopped working after
5 Likes
#2

You need to provide the code that isn’t working as what you said made no sense. If you mean the function inside services/controllers then the function name is KnitStart and not Start.

#3

this is the code:
image

and heres the output:
image

1 Like
#4

That is really weird, can you show me the client runtime? Also is there anything yielding before the KnitStart? It could be what stops it. Keep in mind I’m talking about things outside of KnitStart since KnitStart itself runs in a separate thread so yielding in it won’t affect other controllers.

1 Like
#5

image

2 Likes
#6

Does “ClientRunTime started” get printed?

1 Like
#7

thats weird it doesn’t print out “ClientRunTime started”

1 Like
#8

So it’s a yielding problem as I said, go through all your controllers and see if one of them has an intensive task that takes so long, an infinite while loop, a long task.wait(), etc. If you found any then that’s the problem, U can just move it to the KnitStart of the same controller to fix it.

1 Like
#9

is runservice.Stepped considered one of them?

1 Like
#10

No, It doesn’t yield.,

1 Like
#11

theres one but its a function that needs to be called
image

1 Like
#12

Move the call to the KnitStart of this function and done, if other code needs it and must wait for it then you just gotta wait for it to load.

#13

ok, so it worked but it caused errors cause they need the function to get the players data

#14

Then you have 2 choices

  • Leave the yielding in since there is no other option.
  • Decrease the task.wait(.5) to just task.wait(), that will make it find the data right when it gets loaded.

I think the first option is better though. Some yielding is better than getting unhandled results.

#15

could I get a knit service in a regular script?

#16

You would need to start Knit there again I think so not the best option, why do you want that?

#17

cause I thought of removing the controller and making it a regular module script which I think would not affect the knit module

#18

If it’s a regular module script then you can indeed use a service from it, you would need to require it from the same run time file or from a file required by it, I don’t see how that will fix the problem though.

#19

I just figured out some off them work and some dont like this one here
image

#20

alright, I fixed the issue thanks to your help I really appreciate it. If anyone wants me to tell them how I fixed just replay and I would hopefully replay as fast as I can