Links
Tags
Creators
Details
Licensed BSD-3-Clause
Published 2 years ago
Updated 22 hours ago
All versions
8.0
Release
Timo 8.022 hours ago 12
Uploaded by
Compatibility
Minecraft: Java Edition
26.4-snapshot-6
26.3
26.2
26.1.x
1.21.x
1.20.x
Platform
Data Pack
Changes
Changes
- shelf woodcutting
- woodcutting recipes for the poplar wood set
- uncrafting recipes for spears
- files requiring newer versions are available from the snapshot which added the necessary feature
- added creaking, happy ghast, nautilus, zombie nautilus, sulfur cube, frostbite spawn egg recipe
- shulker dungeons always generate on blocks
- wither skeleton dungeons are always buried
- fix village and pillage ship
- combined redstone chamber and redstone chamber 2 into one structure set
- combined village and pillage ships into one structure set
- more random salts in structure sets
- clean surface rule of rich noise settings
- fixed many bugs in versions before and after 1.21
- redstone chamber chests can contain any type of button
- fishing loot table is affected by luck of the sea (fish becomes rarer; junk stays the same; treasure becomes more common)
- mineshaft chests can contain furnace minecarts
- many loot tables which could not contain treasure enchantments can contain treasure enchantments
- in the bonus chest logs now have a minimum count of 4
- stronghold library chests can contain up to 4 enchanted books
- shepherd chests can contain pink wool
- added the function timo:place_mob_heads which places all custom mob heads for testing
- added advancements for unlocking recipes for all recipes
- advancements in the recipes tab now trigger when the recipe is used, previously it triggered when the recipe was unlocked
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:Th80Dayj:m8DEZVG2"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Th80Dayj:m8DEZVG2"
}
