DeluxeMenus

DeluxeMenus builds menus that look like a chest with items. The player clicks an item and what should happen happens — another menu opens for them, they receive an item, they are teleported to a location, a command runs, or information is shown to them.

It is the best answer to a situation where commands are too complicated for players. Instead of typing /warp mining or /kit vip into chat, you give the player a single menu (for example /menu), where they choose by clicking.

Menus are described in files: menu name, size, items, and what happens after left- or right-clicking. Texts, prices, and icons can be taken from other plugins via PlaceholderAPI (money, level, player count).

Each item can have its own rules: who can even see it, what they must meet (money, permissions, level), and what happens when they don't have it. This makes it possible to create a VIP menu that a regular player can see but does not get — and instead is shown what they need to do.

Menus can be nested: a main menu, with submenus in it for warps, shops, perks. That way the player never gets lost in commands and has everything within two clicks.

For a Czech server, an advantage is that texts are written in Czech directly in the configuration — no translating a plugin that wouldn't support Czech.

1. Download DeluxeMenus from modrinth.com/plugin/deluxemenus (or from the author's official page) for your server version.
2. Upload the .jar to the plugins folder and restart the server.
3. In plugins/DeluxeMenus/gui_menus/ create the first file with a menu — the file name is also the menu name.
4. Set the basics in it: window title, size (9, 18, 27, 36, 45, or 54), and the first items.
5. For each item, set what happens when clicked — opening another menu, a command, a message, or teleport.
6. Test the menu in-game: /dm open (without a player it opens for you) and /dm list pro vlist of all menus.
7. Set who will see the menu: in the main menu, show admins different items than regular players (via permissions or via conditions).
8. Check the Czech language and diacritics — names and texts in the menu are entered directly in the file, so verify it in-game.
9. Verify that texts with values (money, level) update correctly when you open the menu later.
10. Add the menu to an available place: a command (/menu), an item in another menu, or a link on the website and at spawn.
11. When the menu has more than one page (more than 54 items), set up pagination and try clicking through.

A menu is only as good as it is simple. If a player has twenty options in the main menu, they will pick the wrong one. Split them into submenus (warps, shops, perks).
A size of 54 means 54 slots, but not 54 options. Leave the edges empty — the menu then looks clear and the player easily finds what they are looking for.
Write texts in Czech directly into the configuration and check the diacritics in-game. In a menu, it is most noticeable when someone wrote the text without it.
Conditions (I see it when I have money or permission) are better than hiding. A player who sees an item and doesn't get it will learn what they are missing.
Item names and headers change between Minecraft versions. After updating the server, go through the menu and verify that the icons still exist.
If the menu won't open after editing the file, use /dm reload a pod and watch the console — the error in the file is usually printed exactly, including the line.
Back up plugins/DeluxeMenus. A menu is a piece of work and isn't in the server database.