Tags
Creators
Details
All versions
6.4.0
Release
ExcellentCrates 6.4.0last year 616
Compatibility
Minecraft: Java Edition
1.21.8–1.21.10
Platforms
Paper
Purpur
Spigot
Required content
Any compatible version
Changes
- Now supports 1.21.8 and above only.
- New Opening Cost System:
- Crates now can require certain number of a key to open it.
- Crates now can contain multiple different cost options.
- Crates cost options now can contain multiple entries, aka Keys + Money, Key A + Key B, etc.
- Added new placeholder
openings_availablethat вisplays the maximum number of times the crate can be opened, taking into account all available cost options. - The
keysplaceholder now acts the same way as theopenings_availableone for compatibility reasons. It will be removed in the future.
- Editor GUI Overhaul:
- Replaced all chat inputs with dialogs.
- Added more robust options.
- Reward Limits:
- Finally fixed and reworked reward limits.
- Cooldown is works properly now.
- Cooldown get 2 types tp chose from: Daily and Custom.
- Cooldown step was removed.
- Amount of reward rolls is not reset with the cooldown anymore.
- Added config option to toggle the Mass Opening feature.
- Fixed a bug, where players with open cost bypass permissions get refunded when cancelling crate opening.
- Fixed
latest_openerandlatest_rolled_rewardplaceholders not working without player context. - Merged multiple messages for rewards obtained from a single opening into one message.
- Added more detailed problem reporter.
- Added async task for crate and key changes writing.
- Removed reward limit bypass permission.
- Slightly improved performance for crate items.
- Crate's name and lore are properly translated into text components now.
- Performance improvements.
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:TdefKtjL:Fk2WzYAv"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:TdefKtjL:Fk2WzYAv"
}

