Hello, so I recently found out abt knit. Whats the use of it? I heard that its for removing remote events and stuff. But what are the pros and cons of it? Does it prevent exploiter intervening or what?
1 Like
Well, I think I might be a little biased to talk about it, but here’s my thoughts.
Knit is designed to give a service/controller architecture, which lets you create high-level systems in your game a bit easier. With this, it also provides a simple way to create remote communication without having to actually create and mess with remote objects (Knit does this for you in the background). Services/controllers are kind of similar to Roblox services: they are singleton objects that can have methods, properties, and events attached to them, and other code can tie into them.
It does not prevent exploitation. That’s not Knit’s goal.
I also will say that Knit is not for everyone. If you’re just getting started with game development, I would avoid it for now. Usually, it will be appealing to developers who have gotten frustrated with trying to organize the top-level setup of their game structure, which is where Knit shines brightest IMO.
18 Likes
Yes! I’ve always wondered what the purpose was for Knit Framework.
I’m not that talented at scripting yet, so I never really understood it.
Thanks for clarifying sir! The best answer is always from the creator himself 
1 Like
nice, didn’t expect the person who created it to respond. I’ll try it out. Thank you for this information