All versions
1.2.0
Release
Bliss Maces 1.2.02 weeks ago 480
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
BlissMaces 1.2.0 — Paper 1.21 rebuild
Fixed
- Mega Mace crafting now works as intended: place Mace #1, #2 and #3 side by side in one row of a crafting table (any order).
- Mace cooldown now applies reliably. It is tracked per mace number on the server, so swapping or copying items can't bypass it.
- Individual mace numbering is validated at craft time, so two players can't forge the same mace number.
- Shift-click crafting of maces, the Mega Mace and Energy Crystals is blocked to keep the caps accurate.
Changed
- Rebuilt for Paper 1.21+ (Java 21).
- Individual and Mega mace recipes are validated server-side, so only real Energy Crystals and individual maces #1–#3 are accepted.
- Dropped mace items no longer despawn and are protected from fire and explosions.
- The Mega Mace splits back into maces #1–#3 on death, including with keepInventory.
Added
/mace resetcooldownclears all mace cooldowns.cooldown-seconds: 0inconfig.ymldisables the cooldown.
Unchanged
- 3 individual maces and 24 Energy Crystals server-wide (
max-individual-maces,max-tokens). - Damage enchantments (Sharpness, Smite, Bane of Arthropods, Fire Aspect, Density, Breach) blocked on individual maces.
- Maces can't be stored in containers.
- Existing maces, tokens and
state.ymlcarry over from 1.1.0.
Upgrade notes
- Stop the server, remove
blissmaces-1.1.0.jar, addblissmaces-1.2.0.jar. - Check
/mace state. If it reports maces as used up but none exist, run/mace set maces 0.
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:SvsFJw9y:zORLEZ7U"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:SvsFJw9y:zORLEZ7U"
}

