Tags
Creators
Details
1.3.0
Compatibility
Changes
=== v1.3.0 ===
+ Added support for 1.21.5 and the new entity properties
+ Added a random-enchantments-amount condition to be able to apply multiple entries from random-enchantments
+ Added an inventory-contains condition and <customitemplugin>-inventory-contains conditions
+ Added a placeholder-chance condition
+ Added support for colored bundles
+ Added support for all item components for 1.21.4 on Paper, these will be documented at a later date, 1.21.5 coming soon
+ Added a /loot convert command to let RoseLoot attempt to convert a vanilla loot table to its own format
* Items in bunldes are now merged into stacks when possible
* Changed the EntityDeathEvent priority to LOW from NORMAL
* The plugin now uses NMS for enchant-randomly and the feature condition for better compatibility, these features now only work on the latest version for each major release, minus the latest
* VAULT loot tables can now use the vanilla-loot-table condition for checking a vault block's loot table (not trial spawners yet)
* Blocks that break by having their support removed will now be attributed as being broken by a player
* Fixed the permission condition not checking the right entity permissions for loot triggered by a player's projectiles
* Fixed the loot table recursion checker not working
* Fixed recursive loot table calls ignoring top level conditions
* Fixed an error on lower server versions on Spigot servers when using smelt-if-burning: true
* Fixed items dropping from the corner of the block instead of the center
* Fixed errors when running vanilla loot tables missing context properties
* Fixed wind charges having weird behavior with overwrite-existing: items
* Fixed support for ExecutableBlocks
* Fixed RoseStacker stacked entity drops not working properly with the RoseStacker setting drop-accurate-items: false
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:7bPBaMrm:tVAufrW2"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:7bPBaMrm:tVAufrW2"
}

