Tags
Creators
Details
Licensed GPL-3.0-only
Published 2 years ago
Updated 2 weeks ago
All versions
1.1.1.2
Release
zMenu 1.1.1.27 months ago 1,867
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.x
1.20.x
1.19.x
Platforms
Folia
Paper
Purpur
Spigot
Changes
Bug Fixes
- Fixed
openWithOldInventoriesmethod crash on 1.20 by usingCompatibilityUtil.getTopInventory()for safe inventory access. - Fixed trim pattern and material validation: now uses Bukkit
Registryinstead of the hardcodedTrimHelper, with proper error messages listing all available patterns/materials when a key is not found. - Fixed null
ItemFlagentries causing errors when applying flags to item meta. - Fixed
EnchantmentGlintOverrideComponentnot handlingfalsevalues correctly — previously onlytruewas applied, now bothtrueandfalseare respected. - Fixed click requirements defaulting to an empty click list when none are specified — now defaults to all click types.
- Fixed
AttributeWrapperto support an optionalNamespacedKeyinstead of always generating a random UUID, preventing attribute duplication on item rebuild. - Fixed database connection logger initialization order in
ZStorageManager. - Fixed item loading from map (
loadItemStack) to useMenuItemStackLoaderinstead of the removedMenuItemStackFormMapclass.
Improvements
- Command Permissions: Added dedicated permissions for
CommandMenuEditor(ZMENU_EDITOR),CommandMenuVersion(ZMENU_VERSION), andCommandMenuGiveOpenItem(ZMENU_GIVE_OPEN_ITEM). - API: Added
getClickRequirementKeys()method toMenuPlugininterface, allowing addons to retrieve the supported click requirement configuration keys. - Default Configs: Updated default configuration files (
pro_inventory.yml,playtime_reward.yml) to use kebab-case (view-requirement,click-requirement,open-requirement) matching current conventions. - Dependencies: Added
adventure-text-minimessageas a library dependency inplugin.yml.
Internal Changes
- Removed unused
PlayerSkinclass. - Removed unused
MenuItemStackFormMapclass and associatedfromMapstatic method. - Cleaned up imports and formatting across multiple files.
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:XPQ42u1g:AAyV01cR"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:XPQ42u1g:AAyV01cR"
}

