Repository navigation
Commands and Permissions
LemonGui is designed to be fully managed in-game. Below is the complete list of available commands and their required permissions.
All administrative commands default to OP and require the lemongui.admin permission node (or specific sub-nodes) to be executed by other ranks.
| Command | Description | Permission Node |
|---|---|---|
/gui create <name> |
Creates a new GUI with the specified name. | lemongui.command.create |
/gui edit <name> |
Opens the Visual Editor for the specified GUI. | lemongui.command.edit |
/gui delete <name> |
Permanently deletes a GUI. | lemongui.command.delete |
/gui list |
Lists all currently saved GUIs in chat. | lemongui.command.list |
/gui reload |
Reloads the configuration and language files. | lemongui.command.reload |
/gui open <name> |
Opens a GUI (useful for testing or linking to NPCs). | lemongui.command.open |
Pro Tip: You can give a user the
lemongui.adminpermission node to automatically grant them access to all the commands listed above.
By default, LemonGui does not restrict players from clicking items inside a menu. However, you can configure Item-Specific Permissions using the In-Game Visual Editor.
If you set a permission (e.g., vip.kit) on an item using the Permission Editor (Dark Red Banner), any player who clicks that item must have that specific permission node. If they don't, the action will be canceled, and they will receive a customizable "No Permission" message.
If you want an admin or a specific rank to bypass item cooldowns and item permissions inside the GUIs, you can grant them:
-
lemongui.bypass(Currently under development for future updates)