Very nice framework. But I recommend rewrite it to your needs (Also I recommend remove promise at start and yield thread instead).
Yes, you will need some time to make great structure, but this is indeed worth it.
If you need medium/big project with transferable services, your answer is knit.
If you just make something small I think it’s really overkill (Not apply if you have knit services from past project). Just imagine that you write something like:
I found that for most people it is very overkill to try to start a Knit project because of the practically infinite setup time it takes if you let it. My solution to this is to work on a new template called C.G.T(Chain Game Template) that includes essential services and controllers that all games require and a general structure that allows you to just jump in and get started on a new project. If people are interested in that they should look forward to that, I’m a bit busy so a general release should be expected in a few weeks to a month from now.
Knit genuinely is one of the best modules I’ve ever seen. Like ROACT LEVEL GOOD. Normally i’d have to create a localscript inside a folder. Then add it to me default.project.json. Then create a remote event.
But knit completely eliminates that and I can do server-client communication within 1 script. Amazing module 10/10
Hey, small question but what is the benefit of Roact? I had a look at it myself earlier and didn’t see much benefit but I would love to get some input off someone who uses it.
Hi! Just started using Knit. Is there a ‘best practices’ for what actions to be done in KnitInit() vs KnitStart for controllers / services? In the advanced service example you don’t have any code in KnitStart.
Trust me, you should just watch the videos and get started with planning the project that you want to make with it. There aren’t really any “best practices” just make sure your KnitInit doesn’t yield for an unreasonable amount of time because KnitStart won’t run until all KnitInits have run. Good Luck.
It doesnt change that much, but theres a strong motive why I use knit in any project, and its because VSC you cant create remotes in visual studio code and the roblox IDE is just not that good
I don’t know if this is a known thing or not but if it isn’t here is a little tip, since you have to wait till knit started to get a service or a controller you normally would put a variable out of scope and then set it to that service or controller or some other way but, you can just put it inside the table and use it from there here’s an example:
When first starting out with knit I didn’t see this anywhere, I would normally just create a variable outside of the scope and set it to the service or controller.
