Menus are inventory screens with your own artwork: a shop, kits, warps or a server menu. The studio draws the menu, sets every button and exports the files a menu plugin reads.
Start from a template
Open Menus and pick a start: Empty menu, Flat gray panel, Server menu, Confirm purchase, Shop categories, Kit selector, Warps, Player settings or Item list with pages. From a file reads a menu you already have as JSON or as a DeluxeMenus .yml.
Set the buttons
Select a button on the menu itself. The panel shows:
Item and Change item: what the slot shows. The list starts with your own items, then every Minecraft item.
Name and Lore: the hover text, up to 16 lore lines.
Item model: a model by ID, written as namespace:path, for example myserver:coin.
On click and Add action: what a click does, such as Open menu, Close, Command as player, Command as console, Message or Sound.
Click through it
Press Play to click through the menu as a player. The Log shows what each click does, and Play as tries permissions, requirements and whether the player can pay. Press Stop to go back to editing. Nothing is sent to your server: Play is a preview in the studio, not a test in the game client.
Export it
Open Files, or Export this menu in the menu's More menu, and choose a format: DeluxeMenus, JExResource, or .
Your plugin
Pack files
When you build the pack, the menu artwork goes into the resource pack and the server files ZIP holds the menu files.
jexpixel/menus/*.json: The JExResource plugin
plugins/DeluxeMenus/gui_menus/*.yml: DeluxeMenus, when Add DeluxeMenus files is on
jexpixel/INTEGRATION.md: Your own plugin
For DeluxeMenus, copy the .yml files into the DeluxeMenus folder of your server and list each file in DeluxeMenus' config.yml. Give INTEGRATION.md to the developer of your own plugin.
JExResource is not released yet
Until it is, clicks in game need DeluxeMenus or your own plugin. The Pack files export is not yet tested in the game client.