Tags
Creators
Details
1.1.0-1.20.4
Compatibility
Required content
Changes
-
Add wildcard support for including / excluding loot-tables
- You can now use "*" to match loot-tables.
*- Matches everythingfolder/*- Matches all paths under a specific directoryprefix*- Matches all paths starting with a prefix*suffix- Matches all paths ending with a suffix*middle*- Matches paths containing a string
- You can now use "*" to match loot-tables.
-
Add default support for Entitles (Mobs) #34
-
Updated Config to include different rates for Chests, Entities & Others (Others being added by the include config that aren't within in the Chests or Entities Folder. Ie: Blocks, Spawners, etc)
-
Added handling for server-side recipe error (it'll still be invalid but shouldn't spam the error anymore)
-
Remove server-side resource pack
-
Fix crash on servers #35
Optional dependencies
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:76bG0cN9:bAEpZsBG"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:76bG0cN9:bAEpZsBG"
}

