Tags
Creators
Details
7.0.12
Compatibility
Changes
Fixed an API issue that popped up in the update after an internal library was updated (which is used for managing the configuration files). This is largely a hotfix and has been confirmed to work on 1.15-1.20, a more permanent solution is being sought after. Please let me know if there are any behavioural issues with config files.
(Also added new mob heads :D)
In light of concerns about Fractureiser, I have made scans on my PC to ensure and avoid infection from the malware, which is not present on my machine. The SHA256 hash of the compiled build is D220CA3B19276A251FBFCA04459238000D214ED689A1B72064D088B232CAEB23. If the plugin starts behaving strangely, please confirm the hashes match up, and if you have any concerns about this, DM me on Spigot or open a ticket on Discord.
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:5BNpeqz1:pgw3SYdJ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:5BNpeqz1:pgw3SYdJ"
}
