I have created a new plugin that allows you to have as many plugins installed as you want (without them being bunched up like they are currently when you have more than 12 installed!) The way I have set up the scrolling frame that houses all of the buttons gives you roughly 156,800 pixels (vertically) to play around with, considering the fact that the buttons themselves are only 200 x 200 The horizontal resolution is dependent upon your screen resolution, minus 30 pixels.
Tutorial for setting up your plugin with PluginVentory - if you want the proper name and icon for said plugin
Make sure your ScreenGui for your plugin matches the name in the ModuleScript
Some helpful tips
The Shortcut to bring up the interface can be assigned in Studioâs Shortcut manager. Look for the Shortcut titled âShow / Hide PluginVentoryâ
All plugins, except for the Physics Analyzer, RobloxGui, and any other core Roblox Guis, support PluginVentory. PluginWidgets will be supported very soon.
It is also very, VERY important that your plugin has an exit button. Itâs also extremely important that your interface is pre-created so you can easily place the modulescript into your StarterGui instance.
PluginVentory allows all plugins 5 seconds to load their ScreenGuis. If a Gui fails to create itâs ScreenGui within 5 seconds, PluginVentory ignores it and moves to the next available plugin.
Known Bugs
Updating the plugin while a place is opened can result in duplicate buttons being created.
If you need help setting up your plugin to support some of PluginVentoryâs display features, Iâm more than happy to help
Screenshots
BytesGuard, an anti virus plugin I created, works nicely with PluginVentory. PluginVentory also has a scrollbar that extends 512 * 200. Giving you a total playroom of around 102,400 pixels for all of your plugins that support PluginVentory.
A brand new plugin that allows the installtion of wellâŚa lot of plugins.
I am getting the âcould not load plugin dataâ warning for everything. I think you should let us hide that warning.
It also might be more practical to use the new plugin GUI system
I think the problem this plugin attempts to solve is a huge issue and rightly deserves to be corrected. Understanding the limitations involved there probably is no possible other way to go about this without requiring plugin creators to add your module script; I think itâs way too much to ask for everyone to add this to their plugin to enable itâs use.
The only way for us to get this working with 99% of plugins is to stream in the pluginâs source code, and either reupload or save said plugin locally. Now the pluginâs working all fine and dandy with your plugin docker but weâre no longer receiving updates to whatever that plugin may be. Our best bet would be to keep the plugin installed and periodically check the plugin manager page to sync with updates, which makes use of PluginVentory somewhat pointless as the plugins must remain installed.
I installed the update for PluginVentory but itâs still not appearing in my plugin toolbox. Iâve checked a few times to see if Iâm missing it due to the very problem it sets out to solve, but am fairly confident no toolbar button exists to allow access to any setting that could disable this.
Due to the fact that PluginVentory spits out a warn() for every single plugin that doesnât have the required module script in them (all of them), and that I canât stand the output being flooded with 50 warn messages every time studioâs started or is refreshed, Iâve sadly just uninstalled PluginVentory.
The issues relating to cluttered plugin toolbars definitely warrant Robloxâs intervention but a solution doesnât appear to be coming any time soon. I really wish PluginVentory had been the fix Iâve been searching for, but until a workaround is put in place that doesnât require plugin creators to include your module script, I donât think PluginVentory is valid as a useable solution.
At the very least the issue with the warn() spams at studio load needs to be addressed, but unfortunately that wouldnât be enough to bring me back.
I really hope these problems can be overcome as I would absolutely love what PluginVentory attempts to provide, and wish you the best of luck at trying to get it to that point.Hopefully my 2 cents help you get there.
Iâll take your advice and make the plugin more usable - instead of being limited to being required to have a module script for the plugins to function - that will be made optional for the icon and name - and thatâs really the only reason I had it, so you wouldnât have plugins named âScreenGuiâ or anything else in the inventory, as Iâm sure thereâs no API to directly get the name of a plugin. Anyways,
To solve your other issue, PluginVentory is activated by a keyboard shortcut, and the âdisable warn messagesâ toggle button is indicated by either a crossout or a check mark - though I should probably change this to something more obvious.
I appreciate the feedback and I shall be improving it for general users!
The plugin has been opened up to all plugins. Of course, the module script can be added by Plugin Creators who want the proper name and icon to be shown. Hopefully, this update will bring you back to using PluginVentory, because I feel it is a much needed plugin in the hands of every developer!
Tell me if there should be anything else that needs changing.
