Tags
Creators
Details
Licensed ARR
Published 9 months ago
Updated 3 months ago
All versions
3.0
Release
Supply Crates 3.09 months ago 57
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
SupplyCrates Changelog
[3.0] - 2026-02-03
Added
- Modrinth Update Checker:
- Checks for the latest version on Modrinth.
- Notifies admins on join if a new version is available or if they are running a beta version.
- Configurable Drop Duration:
- Added
crate-drop-durationtoconfig.yml(default: 8.0 seconds). - Added
/supplycrates setdroptime <seconds>command to adjust the speed of the falling crate animation. - The drop animation speed now scales dynamically based on this setting.
- Added
- FillLoot Integration:
- Direct integration with FillLoot tables located in
plugins/FillLoot/tables/. - Supports loading custom component metadata from FillLoot tables (Name, Lore, Attributes, Custom Model Data, Unbreakable, Custom Data).
- Direct integration with FillLoot tables located in
Fixed
- Item Duplication:
- Fixed an issue where receiving signal items with a full inventory would duplicate the item or delete it. Now drops excess items at player's feet.
- Fixed
InventoryClickEventhandling to only cancel events within SupplyCrates GUIs, resolving item duplication issues in normal inventories.
- Metadata Parsing:
- Fixed "Unknown item 'minecraft:'" errors when generating loot from FillLoot tables.
- Implemented a robust manual JSON parser for item components, properly handling SNBT formats that caused NMS crashes.
- Global Progress:
- Improved global progress tracking logic.
Changed
- Loot Generation:
- Switched from reflection-based FillLoot API calls to direct YAML parsing for better reliability.
- Removed debug logs related to loot generation.
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:WafBlWY2:rWeSIash"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:WafBlWY2:rWeSIash"
}

