The builder¶
/emenus create <name> [rows] make a new one
/emenus edit <name> open an existing one
/emenus the builder home screen
The canvas¶
The grid you land on is the menu, at its real size, drawn exactly as players will see it. There is no separate preview to drift out of step with the thing you are editing.
| Left-click a slot | Edit the item there, or add one if it is empty |
| Right-click a slot | Clear the slot |
| ++q++ | Open the tools |
Holding an item when you click an empty slot uses that item straight away, including its name. Laying out a menu is: hold, click, hold, click.
Why is there no toolbar on the canvas?
Because a menu can be 54 slots, and a toolbar would mean you could never build a full one. The drop key costs nothing and is always available, on every screen.
The tools¶
++q++ from anywhere.
| Title | What players read at the top |
| Size | 1 to 6 rows. Items that no longer fit are removed, and you are told how many |
| Open command | The command that opens this menu |
| Open permission | Who may open it at all |
| Live refresh | Redraw every few seconds so placeholders stay current |
| Borders and background | The colour palette |
| Start from a template | Replace this layout with a ready-made one |
| Test it | Save, reload, and open it the way a player would |
| Save | Write the file, keep editing |
| Save and exit | Write it and close |
| Discard changes | Put the file back as it was when you opened the editor |
Editing one slot¶
| Item | Any material, or a reference like hdb:1234 or head:%player_name%. Right-click uses what you are holding |
| Display name | Colour codes and placeholders both work |
| Description | The grey lines underneath, one at a time |
| Stack size | The number in the corner |
| Glow | The enchanted shimmer, without a real enchantment |
| Custom model data | For servers running a resource pack |
| Who can see it | A permission node. Without it, the player sees an empty slot |
| What clicking does | The action list |
| Priority | Which item wins when two share a slot |
| Duplicate | Copy this item into the next empty slot |
There is a Save button on this screen too, and a How this works guide in the top-left corner.
Borders and backgrounds¶
++q++ then Borders and background.
| Click a colour | Paint the outer edge |
| Right-click | Fill every empty slot behind your buttons |
| Shift-click | A glowing border |
A border is written as one item claiming every edge slot, not twenty-odd copies. Changing the colour later is one edit, and the saved file stays readable.
Background fill only ever touches slots that are still empty, so it cannot cover a button you have already placed.
Saving¶
Three things write the file:
- the Save button, on the slot editor and in the tools
- Save and exit
- closing the editor, including with Escape
That last one is deliberate. An editor that quietly throws away twenty minutes of work because somebody hit the wrong key is not one you would trust twice. Discard changes is the deliberate way to undo, and it restores the file exactly as it was when the session opened, including anything you saved during it.
Two people, one menu
A menu can only be edited by one person at a time. If somebody else has it open you are told who, rather than both of you saving over each other.
Testing it¶
Test it in the tools saves, reloads, closes the editor and opens the menu as
a player would see it, permissions and all. Get back with
/emenus edit <name>.