Lack of resources around plugin development

it seems outside the basics you’re just expected to learn by yourself

there is like no resources on organizing or planning a good plugin
nor on anything i should avoid
this is concerning especially since plugins have been on roblox for a long time

like where do i put my libraries, do i just make a new copy of fusion in every plugin
i make
compare this to making a game, which have multiple videos dedicated on organization and good practices

1 Like

I find this resource to be pretty good.

For most more advanced plugin things you will have to just go off of the (not great) roblox documentation.

1 Like

this really only covers the fundementals about how to make plugin elements and how to publish

what im currently looking for is structuring plugins and good practices (especially for more complex structures you’d see for managing UI)

the roblox documentation only really covers the API features

thanks for the resource though

You can try looking at the source code of popular plugins and analyze their structure as a reference, I do this a lot whenever I find some interesting plugin (though you need to own the plugin first).
You can use AssetService/InsertService (don’t remember which) to insert plugin into roblox studio workspace or use BtrRblx browser that allows you to look into the source code of models.

Pretty much, at least I don’t think there’s any other alternative to this.
You have to treat plugin as a typical library but with user interface or something like that. Each library puts its own dependencies into itself, meaning if you put 2 libraries with same dependencies into your game, you will have a duplicate of libraries they depend on. Same with plugins.

I’m not exactly an expert in plugins development (hence why my tutorial covers only the basics), but you have to keep in mind to not leave any leftovers after its work. (e. g. plugin creates some asset for something to work in it, like a folder in workspace with parts that are there just for visualization, but it doesn’t get deleted after the plugin’s work is finished, creating an unwanted asset in User’s place), you could use Archivable property for this. As well as implement a Undo/Redo function if it changes something in the place.

I hope this helps!

1 Like

i guess so

might study plugins and do more plugin development
so then i can go make the resources i was looking for

anyways thanks

1 Like

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.