Tags
Creators
Details
1.21.1-4.0.20
Compatibility
Required content
Changes
V-Tweaks Changelog MC 1.21
4.0.20:
Fixed:
- Default Tags not loading because of directory changes
4.0.19:
Added:
- Particle effect while walking on Powder Snow blocks
- Offers a more accessible approach to telling the difference between normal & powder snow
4.0.18
Added:
- New mixin tweak to make Powder Snow blocks solid
- Disabled by default
- Makes exploration in ambient snowy areas less annoying
4.0.17
Added:
- Config to control whether baby
#c:chickenscan have their feathers plucked- Defaults to false; babies cannot have their feathers plucked
Fixed:
- Ungriefing Creepers tweak not working
- Feather Plucking using the wrong Shears tag
- Feather Plucking causing the player's arm to swing even if plucking failed
Changed:
- Updated all references to tags in the
forgenamespace to now use thecnamespace instead- This change is also reflected in Config Comments for maximum clarity
- ChopDown Requires Tool setting uses a less sketchy method for tool detection
4.0.16
Changed:
- The text
Durability:in the Durability Tooltip is now localizable!
Fixed:
- Server Crash
4.0.15
Initial port to 1.21 (and 1.21.1 by proxy) using NeoForge. Tested full suite of features locally in dev server, so hopefully there'll be minimal server-only issues, but we'll see!
Not too much has changed from a functional perspective really:
Changed:
- Challenger Mobs' Gear and Drops now use the Component Feature to define properties like enchantments, potion data, etc.
Removed:
- Food Tooltip: This was trickier to re-implement than I had time for, plus this feature gets turned off by most users anyways because better tools like Quark and AppleSkin exist.
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:Bmda4Rq4:ml45L1Co"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Bmda4Rq4:ml45L1Co"
}

