Flynet is an Plugin Framework for developers, and easy Plugin managment for users. With our Framework, you can make your Plugin be a part of Flynet’s ecosystem and create or use sleek Plugins.
Why Flynet?
Easy to use Framework API
With our easy to use Framework, you can create simply but yet sleek plugins. With our documentation, you will be never lost in developing a Plugin!
Easier access for users
Installing plugins and being lost in Plugins tab won’t be your nightmare anymore. You always can use our Search feature in Flynet’s main tab.
How do I use it?
Documentation for developers
Proper documentation will come tommorow (April 8th)
Installation for users & developers
In our case, we’re installing from GitHub. You can use Creator Store too.
The code is in .rbxm file, instead of inserting into Plugins folder, insert it into workspace. The usage is to have all Plugins in one place, aka Flynet and to make “ecosystem”
How is the plugin downloading process going to work? if I port a plugin to Flynet do users install it through the plugin marketplace and Flynet manages it, or is it through another method?
Good question! Right now I’m making a built-in plugin in v1.0 for importing plugins easily. Here’s the concept: You just provide a Script via .rbxm and users will download it, they are going to insert it into a folder that my built-in plugin will make. I also plan on making online Flynet Plugin marketplace. Stay tuned!
(tip: use this if your plugin is going to be a flynet thing!
You can check the .rbxm file, however, I may use sandboxing scripts feature to restrict some dangerous things. And of course user will be able to change these restrictions
We created brand new feature: Flynet Marketplace! Do not worry: You won’t get any malicious plugins. However, you can always import plugins LOCALLY!
FlyProtect will cover your back!
Installed a shady plugin? Will it insert a backdoor? No worries! You always have FlyProtect! However, if your plugin flags false positive, you can always disable it. But, never, I say, NEVER disable it if someone asks you to!
New API improvements and additions!
We’ve added two new types of UI objects: Checkbox and Input!
Checkbox accepts only one custom property: DefaultState. It only accepts “On” or “Off”, however, you can also use true or false as we convert it! You can toggle it by pressing, and its state is being saved to attribute named “State”.
Okay, so I’m planning to make Flynet v2.0, full rewrite of Flynet and remove Flynet Marketplace to release Flynet Online, the better implementation of Flynet Plugin store.
Why so?
So I just figured it out that my Flynet Marketplace does not work for some users because of the Roblox asset privacy.
What is planned for v2.0?
Complete User Interface Redesign
Better Design. Easier Communication.
FlyProtect v1.1
Protection leads to better results. Why not to protect your game?
More Built-in Plugins
Need to take a note? Need a timer? Need easier conversation between developers without using Alt + Tab each Discord notification and then raging that the notification was from a random abandoned server that you are going to hate for eternity?
To make a successful product, the user has to not get lost in the user interface and be satisfied with it.
Flynet should be simple and understandable to use. We have came up with this design, however, it’s not finished and we have no guarantee it will be used:
Easy to use Framework API
Easier access for users
Known Bugs
Sneak Peek for v1.0
More UI Objects for Plugins (Input, Checkbox)
Looking for developers to fill up the Flynet Marketplace!
Early Access to new versions
Uploading Plugins to Marketplace
FlyProtect will cover your back!
Happy developing and using!
Complete User Interface Redesign