Tags
Creators
Details
0.1.0+1.21.4-alpha
Compatibility
Changes
The first version of the Loot Bundles datapack. Please give it a try and let me know if you encounter any issues so I can move to Beta! MAKE SURE YOU INSTALL THE RESOURCE PACK AT THE BOTTOM OF THE PAGE!
[0.1.0-alpha] - 2024-12-30
Added
Items
5 new items have been added to Minecraft in this Alpha version:
- Added Common Loot Bundle
- Added Uncommon Loot Bundle
- Added Rare Loot Bundle
- Technically, Epic Loot Bundles ARE in this version, but they cannot be obtained without rerolling for them and they have no functionality
- Added Vault Loot Bundle
- Added Ominous Vault Loot Bundle
Advancements
5 new advancements have been added to Minecraft in Alpha version:
- "Bundles of Joy" for obtaining any Loot Bundle
- "Reroll!" for rerolling a Loot Bundle into one of a higher tier
- "Trial By Bundle" for opening a Vault Loot Bundle with a Trial Key
- "Rebundling" for opening an Ominous Vault Loot Bundle with an Ominous Trial Key
- "A Dangerous Gamble" for obtaining an Epic Loot Bundle
Misc
- Created the functionality that Loot Bundles is built upon. For more information, take a look inside the datapack's files and see if you can intuit how it works (there are many comments in the function files!)
Config
- Added
give_itemfunction files for each Loot Bundle- NOTE: Epic Loot Bundles currently lack functionality, as this is just an alpha test. The only way to obtain one is through rerolling from a Rare Loot Bundle. If you obtaining a Epic Bundle, just hold onto it!
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| Reg's Loot Bundles Resource Pack v0.1.0+1.21.4-alpha.zip | Required resource pack | 17.24 KiB |
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:FKfknEgo:yPW0JfEZ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:FKfknEgo:yPW0JfEZ"
}

