Links
Tags
Creators
Details
All versions
1.2.2
Release
A Best Crates 1.2.2 (1.21/1.21.11)4 months ago 1,095
Compatibility
Minecraft: Java Edition
1.21.x
Platform
Paper
Changes
ABestCrates 1.2.2
Version 1.2.2 adds admin maintenance tools, crate templates, config versioning, statistics GUI improvements, and release polish for the Paper 1.20.x branch.
Added
- Admin commands and GUI tools for resetting player cooldowns, player open stats, player reward limit counters, and global reward limit counters.
- Admin Tools statistics GUI for viewing a player's crate history, players who opened a selected crate, player totals, and the most-opened crates.
- Crate duplication with
/abc duplicate <crate> <newName>. - Crate template export/import with
/abc export <crate> [file]and/abc import <file> [newName]. - Template files stored under
plugins/ABestCrates/templates. config-version: 2markers for generated configuration files.- bStats integration wiring, controlled by
metrics.enabledandmetrics.plugin-idinconfig.yml. - Insert Nickname lookup for player statistics and Give Keys GUI workflows.
- Additional unit coverage for crate IDs, safe value clamping, reward settings, and zero-chance reward rolls.
Changed
- Chat prompts, command help, protected-crate, admin, and template messages now live in
messages.yml. - Player open data now stores last-known player names for easier offline stat lookup.
Fixed
- Modern Paper serialized
ItemStackfields in crate files are normalized before loading to avoidMaterial cannot be nullstartup errors. - Existing bundled config files are no longer recopied on startup, removing noisy already-exists warnings.
Requirements
- Paper 1.20.1-1.20.6.
- Java 17 for Paper 1.20.1-1.20.4.
- Java 21 for Paper 1.20.5-1.20.6 and 1.21.x.
- Vault and PlaceholderAPI remain optional.
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:HuFreMHp:jujtJm4K"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:HuFreMHp:jujtJm4K"
}

