I have been making plugins for quite a while and i think it would be a nice feature to studio. Being able to run plugins, without publishing them
1 Like
You can manually add plugins through the plugin folder. Just go to the plugins tab, then select plugins folder. Put the plugins in there.
I think he means for testing purposes – not for having them private. Even if you put them there, you have to restart Studio, or open a new place, every time you want to test a plugin update. I think what he’s asking for is when you select Test > Start Plugin, it would open a menu and you would choose which plugin you would want to test, and then it would add it to Studio temporarily. This would get a bit tedious if you wanted to test the same plugin over and over, but had to continually select it, so instead, I would think a “Reload Plugin” option would be better.
Reloading a plugin (Right click on plugin; select “Reload”) would stop the current plugin’s code from running and start it again. That way, you’re not having to open new places nor continually select which plugin you want to test from a file menu when you are just testing one plugin.
I am aware of this, however there sre two types of plugins. Single-file, and dependant.
Single-file plugins are single lua files that contain the plugin code.
Dependant plugins are scripts or models that hold children, and are published to roblox fom the explorer window. These allow you to keep instances inside your plugin for later use (aka intrucate GUIs, modules), some dependant plugins include MultiplayerStudio, and Gui Studio by MrNil,
Test->play plugin would allow you to get pass having to upload to roblox, update your plugin manually, and opening up a new place just to test a single update for a dependant plugin.
Yes please, testing plugins can be quite a hassle, especially when working with the newer plugin format.
1 Like