Tags
Creators
Details
Licensed ARR
Published 4 years ago
Updated 2 weeks ago
All versions
1.0.8-a
Alpha
Full Inv Control & Addon Manager2 weeks ago 254
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
1.21.x
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
What's new
- Choose what happens when your inventory is full. Each drop has a new "Full Inventory" setting in its settings menu. Click it to switch between:
- Drop on the ground: anything that doesn't fit lands at your feet, the same as before.
- Stop drops: only what fits in your inventory drops. This includes normal Minecraft drops.
- Server owners can set the default for all drops in the config.
- Addon Manager. Install and update CustomDrops addons without leaving the game. Open it with /cd addons or the new Addons button in the main menu.
- Xenith adds conditions and actions for drops and loot.
- BlockHardness adds custom mining speeds for blocks. It needs ProtocolLib, and the menu warns you if that's missing.
- Each addon shows whether it's installed and if an update is available. Click to install or update, then restart the server to finish.
- Requires the drops.addons permission.
Improvements
- Smarter inventory checks. A full inventory still picks up an item if you already have a stack of it with room. For example, you can keep collecting wool while your wool stack isn't full.
- Auto-inventory works better when your inventory is nearly full. It fills every stack it can, and only the extra goes to the drop's Full Inventory setting.
- Shared mob kills are fairer. When several players damage a mob, its normal drops are checked against the killer's inventory.
Fixes
- Fixed an error that some unusually named loot entries could cause.
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:7W4ykV3p:24Atsdtm"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:7W4ykV3p:24Atsdtm"
}

