Tags
Creators
Details
Licensed ARR
Published 7 months ago
Updated 3 months ago
All versions
2.0.4
Release
Randomized Block & Mob Drops 2.0.47 months ago 896
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Server-side
Singleplayer
Changes
[2.0.4] โ 2026-03-22 โ Auto-Rebuild & Blacklist Fixes
๐ New Features
- Auto-rebuild on mod or config change. Each world's datapack folder now stores an
rbmd_config.txtfile containing a hash of the active config and loaded mod list. On every world load, if the hash has changed (blacklist edited, toggle flipped, mod added/removed), the datapack is automatically rebuilt with the same seed. Drops stay the same for unchanged items โ the cycle just updates to include or exclude new items. - Mod list change detection. Adding or removing a mod automatically triggers a rebuild on next world load. No need to manually run
/rbmdreshuffle.
๐ Bug Fixes
- Fixed: mod blacklist not applying to existing worlds. The mod blacklist correctly excluded items from the in-memory permutation pool, but existing worlds reused the old datapack files on disk without regenerating โ so blacklisted mod loot tables were still active. The new config hash system detects this and forces a rebuild.
โ๏ธ Technical / Internal
buildConfigHash()hashes all config values plus the full mod list (mod ID + version) using aTreeSetfor consistent ordering.- Config hash stored in
datapacks/rbmd_randomizer/rbmd_config.txtalongside the existingrbmd_seed.txt. - Log line on rebuild:
Config or mod list changed since last generation โ rebuilding datapack.
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:gTOR8pvl:YHubRtTQ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:gTOR8pvl:YHubRtTQ"
}

