All versions
1.2.0
Release
ShieldHider 1.2.03 days ago 2
Compatibility
Minecraft: Java Edition
1.21.11
Platform
NeoForge
Supported environments
Client-side
Required content
Any compatible version
Changes
ShieldHider 1.2.0
Added
- New builds: Fabric 1.19.2, Forge 1.19.2, Forge 1.21.1 and Forge 1.21.11. They hide the held shield in first person exactly like the other builds.
- Each new build checks the shield tag of its own loader and Minecraft version: c:shields on Fabric 1.19.2, forge:tools/shields on Forge 1.19.2, c:tools/shield on Forge 1.21.1 and 1.21.11.
Changed
- Fabric builds now require Fabric API and Architectury API. NeoForge builds require Architectury API. Forge builds need nothing beyond Forge.
- Fabric 26.1.2 now requires Fabric Loader 0.19.5 or newer: the current Architectury API crashes the game at startup on older loaders.
- Every jar is for exactly one Minecraft version. In 1.1.x the Forge 1.20.1 jar also accepted later 1.20.x releases, and the NeoForge 1.21.1 and 1.21.11 jars accepted any later Minecraft. That is no longer the case.
Fixed
- A malformed escape in config/shieldhider.properties (a \u not followed by four hex digits, for example a stray backslash in front of a u) crashed the game when entering a world. The mod now logs a warning naming the file and ignores the file's lists until it is fixed. The vanilla shield, shield-type items and the conventional shield tags are still hidden.
Unchanged
- The same items are hidden as in 1.1.0.
- config/shieldhider.properties keeps its name, its four keys and their syntax.
- No Minecraft version or loader was removed.
Compatibility
- Client-side only on every loader: a server does not need the mod.
- Architectury API is accepted up to, not including, its next major version. Forge and NeoForge are accepted within their own line.
| Minecraft | Fabric Loader | Fabric API | Architectury API | Forge | NeoForge |
|---|---|---|---|---|---|
| 1.19.2 | 0.14.9+ | 0.66.0+1.19.2 | 6.6.92+ (Fabric) | 43.1.0+ | – |
| 1.20.1 | 0.14.21+ | 0.83.0+1.20.1 | 9.2.14+ (Fabric) | 47.1.0+ | – |
| 1.21.1 | 0.15.11+ | 0.102.0+1.21.1 | 13.0.11+ | 52.1.0+ | 21.1.1+ |
| 1.21.11 | 0.17.3+ | 0.139.4+1.21.11 | 19.0.1+ | 61.1.0+ | 21.11.0-beta+ |
| 26.1.2 | 0.19.5+ | 0.154.0+26.1.2 | 20.1.14+ | – | 26.1.2.99+ |
| 26.2 | 0.19.3+ | 0.154.0+26.2 | 21.0.7+ | – | 26.2.0.40-beta+ |
| 26.3 | 0.19.5+ | 0.160.5+26.3 | 22.0.1+ | – | 26.3.0.0-beta+ |
Architectury API is required on Fabric and NeoForge only, never on Forge.
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:gDlNzeRh:I8JlEh1l"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:gDlNzeRh:I8JlEh1l"
}

