1.0.4
Compatibility
Changes
Changelog
All notable changes to Recipe Shuffler are documented here. [1.0.4] — Current 🎉 New: Commands & Config System
Ported over the full command and config system from Randomized Block & Mob Drops.
New commands:
/rshhelp — list all commands
/rshreshuffle — reshuffle with a new random seed
/rshreshuffle <seed> — reshuffle with a specific seed
/rshfind <item> — find what now crafts a given item
/rshrecipe <recipe> — look up what a recipe now produces
/rshdebug — print debug info
/rshcheck — verify the generated datapack is active
/rshdump — dump the full shuffled recipe list
/dkrsreload — kept as a legacy alias
New config file: config/recipe_shuffler-common.toml
randomize_recipes — master on/off toggle
chaos_mode — more extreme, less predictable shuffle
item_blacklist — items excluded from shuffling
recipe_blacklist — recipes excluded from shuffling
mod_blacklist — entire mods excluded from shuffling
show_welcome_message — toggle the chat welcome message
Other improvements:
World seed is now remembered and reused automatically
Shuffle auto-regenerates when config or installed mods change
Generated datapack is force-added and reloaded automatically, no manual /reload needed
🐛 Fixed
Modded recipes not shuffling in modpacks. Generated recipes were always written to data/minecraft/recipes, so anything from another mod never actually got overridden. Recipes are now written to each mod's own namespace, so overrides apply correctly across the whole pack.
🔤 Renamed
Display name: Receipe Shuffle → Recipe Randomizer → Recipe Shuffler
Mod ID: dkrecipeshuffle / dkrshuffle (mismatched) → unified as recipe_shuffler
Generated datapack folder: dkrecipeshuffle → recipe_shuffler_generated (old folder is cleaned up automatically on regeneration)
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:7xYyyU8T:eRwlLkU1"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:7xYyyU8T:eRwlLkU1"
}

