2.0
Compatibility
Changes
Version 2.0 - Rework
This version is a fully rewritten plugin. It removes the hardcoded single mace limit, introducing configurable limits, in-game GUI management, live tracking, and custom recipes.
Configurable Crafting Limit
The server is no longer restricted to one Mace! You can now configure the number of Maces that can be crafted server wide (up to a maximum of 7). Once the limit is reached, recipes are automatically disabled.
Full In-Game GUI
All plugin settings can now be managed directly in-game.
Access: /om settings (or /onemace settings)
- Change the server Mace crafting limit
- Edit individual Mace recipes
- Toggle plugin features
- Manage container restrictions
Custom Crafting & Attributes
Each Mace can now be customized individually.
- Custom Recipes: Modify the crafting recipe for each Mace through the GUI.
- Attributes: Toggle traits such as Fire Immunity and Enchantability per Mace.
- Cosmetics: Choose whether the crafter’s name appears in announcements and whether attributes appear in the item lore.
Tracking & Container Restrictions
- Live Tracking: Use
/om locateto find the location of any crafted Mace, including player inventories and containers. - Container Restrictions: Prevent Maces from being stored in specific containers (Ender Chests, Shulker Boxes, Chests, Furnaces, etc.).
New Admin Commands & Configs
New tools and files have been added for server admins to manage the plugin easily.
- Added
/om locateto track active Maces. - Added
/om reset [confirm]to safely wipe Mace data and restart the limit. - Added
/om reloadto reload configuration files. - New Files: Data and settings have been split into
config.yml,data.yml,maces.yml, andmessages.yml. All plugin messages are now 100% customizable!
Disclaimer
The plugin description has been updated to reflect version 2.0. Features described may not apply to older versions.
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:UEMgHuAO:Smio02DZ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:UEMgHuAO:Smio02DZ"
}

