All versions
2.0.0
Release
zyramenu 2.0.02 weeks ago 22
Uploaded by
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
1.21.x
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
ZMenu 2.0.0, first release
Custom chest menus, created and edited entirely in game. Spigot / Paper 1.21 โ 1.21.x, Java 21.
Features
- Create a menu with
/zm create <name>: drop items into a chest, close it, it's saved. - In-game editor with
/zm edit <name>: name, lore, item, amount, glow, hidden info, tooltip, model, permission, close on click, move, duplicate, delete. - Real chest editing with
/zm chest <name>: a chest appears under your feet with the menu inside./zm savesaves it and removes the chest. Unchanged items keep their lore and commands. - Menu settings with
/zm settings <name>: title, rows, permission, custom open command (/shop), open sound, background item. - Actions on buttons:
[player],[console],[message],[broadcast],[open],[close],[sound],[title],[actionbar]. - Images to items with
/zm transcript <image>: up to 9ร6 tiles, no grid lines, resource pack generated and sent automatically. - Placeholders:
%player%,%uuid%,%world%and PlaceholderAPI.
Resource pack
- On Paper, the pack is served through the Minecraft port: nothing to open, works on Pterodactyl.
- The player's connection address is detected automatically.
- On Spigot: port
8165orexternal-url.
Valocraft compatibility
- Both packs are sent side by side on the same port, without conflicts.
- Menus and editing are blocked during a match.
- Valocraft placeholders:
%valocraft_rank%,%valocraft_radianite%,%valocraft_level%,%valocraft_kd%... - Requires Valocraft 2.3.2+ for correct resource pack messages.
Installation
Drop ZMenu.jar into plugins/ and restart. No dependencies required.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:y8TYDCnK:dp9zhH3s"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:y8TYDCnK:dp9zhH3s"
}

