1.0.1
Compatibility
Changes
š§ Bug Fix Update - Mace Restriction Config
Hey everyone! We've fixed a bug with the mace blocking configuration:
What was broken: The block_regular_maces setting in config.yml wasn't working properly when using /mythicsadmin reload - you had to restart the server for changes to take effect.
What's fixed: ā Config now reloads properly with /mythicsadmin reload ā Moved block_regular_maces from bloodbath: section to general: section (makes more sense as a server-wide setting) ā No more server restarts needed to toggle mace blocking!
How to use:
Edit config.yml and change general.block_regular_maces to true or false Run /mythicsadmin reload in-game Changes apply immediately! Note: Set to false if you want players to craft/use regular maces, or true to only allow the Bloodbath mythic mace.
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:vipDSle5:D5LQZxJX"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:vipDSle5:D5LQZxJX"
}

