Tags
Creators
Details
Licensed ARR
Published 7 months ago
Updated 3 months ago
All versions
2.0.2
Release
RBMD 2.0.27 months ago 31
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Server-side
Singleplayer
Changes
[2.0.2] โ 2026-03-19 โ Features & Bug Fixes
๐ New Features
/rbmditemdrops <item>โ reverse lookup showing what blocks and mobs drop a specific item, split into separate categories./rbmdmobdrops <mob>โ shows what a specific mob drops now after randomization.- First join welcome message โ shown once per player per world on first login. Tells players drops are randomized and to run
/rbmdhelp. - Config file (
config/rbmd-common.toml) with the following options:randomize_blocksโ toggle block drop randomizationrandomize_mobsโ toggle mob drop randomizationrandomize_silk_touchโ toggle Silk Touch drop randomization (default: true)item_blacklistโ items that never appear as randomized drops (defaults to unobtainable blocks like bedrock, barrier, command blocks, etc.)mob_blacklistโ mobs whose drops are never randomizedmod_blacklistโ exclude all items and mob drops from an entire mod by its mod IDreset_welcome_messageโ force the welcome message to show again on next join
- Spawn eggs excluded as loot table sources โ items won't drop from spawn eggs since they can't be broken.
- Config values logged on startup โ active config is printed to
latest.logon every world load for easy debugging.
๐ Bug Fixes
- Fixed:
randomize_mobs=falsestill randomizing mob drops. The config toggle only skipped theLivingDropsEventhandler but the datapack was still writing randomized entity loot tables. Entity loot tables are now skipped during datapack generation whenrandomize_mobs=false. Same fix applied torandomize_blocks=falseand block loot tables. - Fixed:
randomize_blocks=falsenot applying to existing worlds. The existing-world code path hit areturnbefore checking the config, so the toggle was silently ignored on any world that had already been loaded. Config is now checked before scheduling the reload on existing worlds too. - Fixed:
COVERED_TABLESalways empty, causing some mobs to drop nothing.COVERED_TABLES.clear()was called at the end ofmakeDatapackinstead of the beginning, wiping the set immediately after building it. TheonLivingDropshandler always saw an empty set and remapped every mob through the event โ mobs whose loot table used complex entry types (tags, groups) got nothing remapped and dropped nothing. - Fixed: double-randomization on mobs with loot tables. Broadened the loot table ID match in
onLivingDropsto handle mods that register table IDs without theloot_table/path prefix. - Fixed: all warnings โ removed unused imports, simplified always-true/false null checks, replaced deprecated
defineListAllowEmptywithdefineListusing suppliers.
โ๏ธ Technical / Internal
/rbmddropsrenamed to/rbmditemdrops.- Section comments trimmed to single lines throughout the file.
- Unobtainable items (bedrock, barrier, etc.) moved from hardcoded
EXCLUDEDset into the configurableitem_blacklistdefault โ onlyAIRremains hardcoded. makeDatapacknow readsrandomize_blocksandrandomize_mobsconfig values to skip irrelevant loot table categories at generation time, not just at event time.
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:TbN7Tzkf"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:gTOR8pvl:TbN7Tzkf"
}

