Links
Tags
Creators
Details
1.9.1
Compatibility
Changes
Forge 1.19 - 1.9.0
- Fixed compatibility with new forge version 41.0.99. Closes #57
Forge 1.19 - 1.9.0
-
Ability to change the default range for all spawners through config. Look for the fields: default_spawner_range and default_spawner_range_enabled
-
You can now change the hardness of the spawner through config. Default is 5 (obsidian is 50 for comparison). Field is: spawner_hardness
-
Fixed server config sync
-
Fixed version numbering
Forge 1.19 - 1.8.16
-
Update to 1.19!
-
Fixed limited spawns, they now work. Look in config to enable it!
-
Fixed redstone consistency issue: #55
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:ZF0coYok:P6WuqFmJ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ZF0coYok:P6WuqFmJ"
}

