All versions
0.1.3
Release
Bridle 0.1.32 weeks ago 18
Compatibility
Minecraft: Java Edition
26.1.x
Platform
Fabric
Supported environments
Client and server
Changes
๐ก๏ธ v0.1.3 - Multiplayer Security Patch
"A behind-the-scenes update that keeps every mount safe on multiplayer servers. Your saddles, bridles and blankets stay exactly where you put them."
๐ Three Minecraft Versions
- 26.1, 26.2 & 26.3: This release is available for Minecraft 26.1, 26.2 and 26.3. Download the file that matches your game version; all three have the same features.
๐ Security & Stability
๐ด Server-Side Mount Validation
- Interaction Range Check: The server now verifies that you are actually next to a mount (vanilla interaction range) before equipping, unequipping, or opening its inventory. Modified clients can no longer manage mounts from across the world.
- Shears Requirement Enforced: Removing equipment from a mount now strictly requires holding Shears, validated on the server, preventing other players from stripping your gear.
- Valid Mounts Only: Equipment requests are only accepted for living, rideable creatures supported by Bridle, ignoring invalid or spectator interactions.
๐ Bug Fixes
๐ Nautilus Taming Progress
- Progress Is Now Saved: Fixed a bug where the taming progress (temper) of a Nautilus was lost every time you left the world or the chunk unloaded. Your patience while riding an untamed Nautilus now carries over between sessions.
๐ Recipe Book
- Recipes Now Unlock: The Bridle and Goggles recipes now appear in your recipe book as soon as you pick up leather or iron, like vanilla recipes do. They were never being unlocked because their data lived in a folder the game no longer reads.
๐ ๏ธ Stability
- Trimmed Armor No Longer Crashes the Game: With Bridle installed, drawing armor with a trim (in the Smithing Table preview, for example) could crash the game. Fixed.
- Stricter Internal Checks: Bridle now verifies all of its game hooks when loading, so a future incompatibility shows a clear error instead of silently disabling a feature.
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:etK4rflo:xgxhj7qU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:etK4rflo:xgxhj7qU"
}

