Item‐Requirements

💰 Item Requirements & Restrictions

LemonGui allows you to easily restrict who can click an item and how often they can do it. You can lock items behind economy costs, experience levels, cooldowns, and permissions—all configured directly from the In-Game Visual Editor.

💳 Economy Costs (Vault & EXP)

You can charge players a specific amount of in-game money or experience levels to execute an item's actions.

1. Open the Visual Editor for your GUI (/gui edit <name>).
2. Click the item you want to edit.
3. Click the Requirements (Gold Ingot) icon.
4. Edit Price: Click the Gold Nugget to type a number in the chat (e.g., 500).
5. Toggle Currency: Click the Emerald to switch the currency type between VAULT (In-game money) and EXP (Experience Levels).

Note: If a player does not have enough Money or EXP, the click actions will be canceled, and they will receive an error message. Vault economy requires the Vault plugin and an economy provider (like EssentialsX).

---

⏳ Click Cooldowns

Want to prevent players from spam-clicking a reward or a command? You can set a cooldown in seconds for any item.

1. In the Item Editor, click the Edit Cooldown (Redstone Dust) icon.
2. Type the amount of time in seconds in the chat (e.g., 86400 for a daily cooldown, or 60 for a minute).
3. Type 0 to disable the cooldown.

When a cooldown is active, the player will receive a message telling them exactly how many seconds they need to wait before clicking the item again. Cooldowns are tracked per player and per item slot.

---

🔒 Item Permissions

You can hide the functionality of an item behind a specific permission node. This is perfect for VIP-only menus or staff tools.

1. In the Item Editor, click the Permission (Nether Wart) icon.
2. Type the custom permission node you want in the chat (e.g., myserver.vip.fly or lemongui.menu.staff).
3. To remove the permission requirement, simply type none.

If a player clicks the item without having the assigned permission, the actions will not execute, and they will see the default no_permission message configured in your en_US.yml file.