1.2.1
Compatibility
Changes
-
Config Changes
- The Config File has been renamed to "mob_repellent-server" to match the neoforge version
- The Config File has been moved from <instance>/<world>/serverconfig to <instance>/config to match the neoforge version
- The Config is now loaded from the file under <instance>/config if no config file is present in <instance>/<world>/serverconfig to override it
- Copying the config file into <instance>/<world>/serverconfig will override the config in <instance>/config for the world it is present in
-
Updated Internal Library NightConfig to 3.9.0
-
Added Update Checker
-
Brazier igniters are now data driven with the brazier_igniters tag
-
Brazier extinguishers are now data driven with the brazier_extinguishers tag
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:XV1TMTqe:fR3v2HKN"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:XV1TMTqe:fR3v2HKN"
}

