Tags
Creators
Details
Licensed GPL-3.0-only
Published 2 years ago
Updated 2 days ago
All versions
2.1.0+1.21.10
Release
Bronze 2.1.0+1.21.1011 months ago 113
Compatibility
Minecraft: Java Edition
1.21.10
Platform
Fabric
Supported environments
Client and server
Changes
π New
- Minecraft's Copper update has elevated tin to a material used in armour, weapons and tools (it finally gets its own nugget!)
- Tin and bronze items have been added to various different loot tables across the game, closely matching vanilla's conventions
- Sickle can now pluck flowers in an area with Right Click
- The sickle's effective area can be tweaked from 1 to 10 blocks in the config file
βοΈ Changes
- The mod's approach to balance has shifted with the copper update. Instead of bronze being an upgrade over iron, it's now more of a sidegrade. It still has better durability and enchantability, but has been nerfed overall. (Tin is a sidegrade to copper, but has more extreme differences than bronze does to iron)
- Tin is now more plentiful and appears in slightly larger veins. This balances it better as a material you can use for gear in the early game
- Existing tin textures have been updated to match the colour scheme of tin weapons/tools/armour
- Sickle
- changed enchanting to be anvil only, and can only be enchanted with the same enchantments as shears can
- changed classification, no longer a tool for mining blocks faster (was overlapping hoe). It's now in the same class as shears, rather than a tiered tool.
- renamed sickle_aoe to sickle_mow (update datapacks that include this file to the new name!)
- added sickle_pluck, which includes blocktags for flowers, which are now harvestable with right click.
π οΈ Fixes
- Aligned bronze (and tin) axes with vanilla's convention. This is technically a damage buff for the items, but should always have been this way.
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:6pVlXMty:A9cgM2JJ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:6pVlXMty:A9cgM2JJ"
}

