PluginAction.AssignedShortcut and 4th CreatePluginAction() parameter

As a Roblox developer, it is currently impossible to know what shortcut is assigned to a PluginAction.

To remedy this, I would suggest adding a new string property to the PluginAction object called AssignedShortcut. The inclusion of this property would allow flexible tooltips that notify the player of the command to use.


As a Roblox developer, it is currently impossible to provide a default shortcut for a PluginAction.

Adding a fourth parameter to the CreatePluginAction() function, suggestedShortcut, would allow the developer to pre-select the desired shortcut. If the shortcut isn’t already taken, it gets set as the action’s shortcut. This would allow much-increased ease of use for the user.



This concludes my spree of PluginAction threads.
15 Likes

Without these two features there isn’t much reason to ever use CreatePluginAction() as a Plugin developer. I have no way to assign a shortcut to an action, and even if I can convince my user to go into an obscure settings menu to set it themselves, I have no way of knowing what they set it to.

I believe this feature is absolutely essential for nurturing a professional Plugin development ecosystem.

3 Likes

Been a couple years, hasn’t it? It’s still impossible to know if a shortcut has been set (or what it’s been set to). I’ve run into this issue again with a low-profile plugin that I want to drop a message in the output reminding the user to set a shortcut if they haven’t already, but I’m not able to.

I make a lot of low-profile plugins, but a decent chunk of users have a hard time getting them set up because there’s no way to a) have them get set up automatically or b) dynamically remind the user when and how they need to set it up. These two features would enable that ability and vastly improve plugin actions.

3 Likes