Tags
Creators
Details
1.3.0-1.21-1.21.3
Compatibility
Required content
Changes
🎉 New Features
-
Configurable Loot Table Probabilities: You can now fully customize the ticket spawn probabilities for each structure through the
ToEK.jsonconfiguration file- Individual configuration for each specific loot table
- Configurable generic probability for other chests
- Default values maintained for backward compatibility
-
Nether Fortress Support: Added support for tickets to spawn in Nether Fortress chests with a default probability of 5%
-
Extended Compatibility: The mod is now compatible with Minecraft versions from 1.21 to 1.21.3 with a single JAR
🔧 Improvements
- Dependency Optimization: Removed unnecessary
server-translations-apidependency
📝 Configuration Changes
The ToEK.json file now includes two new fields:
{
"lootTableProbabilities": {
"minecraft:chests/ancient_city": 0.1,
"minecraft:chests/abandoned_mineshaft": 0.03,
"minecraft:chests/stronghold_library": 0.05,
"minecraft:chests/stronghold_corridor": 0.05,
"minecraft:chests/stronghold_crossing": 0.05,
"minecraft:chests/end_city_treasure": 0.05,
"minecraft:chests/bastion_bridge": 0.15,
"minecraft:chests/bastion_hoglin_stable": 0.15,
"minecraft:chests/bastion_other": 0.15,
"minecraft:chests/bastion_treasure": 0.15,
"minecraft:chests/nether_bridge": 0.05
},
"genericChestProbability": 0.005
}
lootTableProbabilities: Map of customizable probabilities per loot table (0.0 to 1.0)genericChestProbability: Probability for generic chests not specified (default 0.5%)
📚 Documentation
- Updated README with complete information about the new configuration options
- Improved documentation on how to customize loot table probabilities
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:rzksOpGQ:abJ34j45"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:rzksOpGQ:abJ34j45"
}

