Tags
Creators
Details
3.0.0+1.21.4
Compatibility
Required content
Changes
3.0.0
1.21.2 and 1.21.4 made massive changes to items, including shields. This means that Shield API is nearly obsolete, how exciting!
But we are not there quite yet, as Minecraft still checks specifically for the "minecraft:shield" item in some places.
Custom shields are now created using 100% vanilla tech, see the test mod for an example.
Note: Shields now directly use the 'attribute modifier component'. This means that they can be changed for individual item stacks. Changing the default is more involved, however. There are already other mods out there doing exactly that, which is why I choose to remove the feature from Shield API.
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:y9clIFY4:fllnpOlz"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:y9clIFY4:fllnpOlz"
}

