All versions
1.0.0
Release
TCrates 1.0.03 weeks ago 33
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Paper
Purpur
Changes
๐ TCrates v1.0.0 โ The Initial Production Release
Welcome to the first official release of TCrates! Built from the ground up as a modern, ultra-lightweight, and zero-lag reward engine for modern Paper and Purpur servers.
โจ Core Highlights & Features
- โก Zero-Lag Async Engine: Non-blocking asynchronous database operations powered by HikariCP with SQLite and MySQL support.
- ๐ฏ Fair Pity System: Configurable pity counters that guarantee rare drops after a set number of rolls, eliminating unfair bad-luck streaks.
- ๐ฎ Shards & Alchemy Fusion: Turn unwanted items into progression! Collect shards and transmute 10 lower-tier shards into higher-tier shards via
/tcrates shards. - ๐ฐ Progressive Community Jackpots: Server-wide jackpot pool that grows with every crate opened and triggers celebratory payouts.
- ๐ Interactive Crate Missions: Dynamic daily/weekly opening milestones with progress bars (
/tcrates missions). - ๐ฌ Offline & Overflow Mailbox: Players never lose drops due to full inventories or disconnects (
/tcrates mailbox). - ๐๏ธ Instant Left-Click Preview: Left-click any physical crate block in-game to view item rarities, lore, and transparent drop odds.
- ๐งช Monte Carlo Simulation: Test economic balance in milliseconds with
/tcrates simulate <crate> <runs>. - ๐จ Modern UI Design: Crisp Adventure MiniMessage gradients, zero unwanted vanilla italics, and responsive click handlers.
๐ฆ Platform & Compatibility
- Supported Platforms: Paper, Purpur (1.21.x)
- Java Version: Java 21+
- Dependencies: Completely standalone! (Optional: PlaceholderAPI, Vault)
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:c8WpeeWy:F4lZp5qW"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:c8WpeeWy:F4lZp5qW"
}

