Tags
Creators
Details
Licensed MIT
Published 2 years ago
Updated 2 months ago
All versions
2.5.0+26.1.2-fabric
Release
2.5.0 for Fabric 26.1.24 months ago 1,659
Uploaded by
Compatibility
Minecraft: Java Edition
26.1.2
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Changes
Trident improvements
- Impaling now also affects all mobs that are in water or rain instead of only specific aquatic mobs.
- Tridents with Loyalty will always return to the hand they were thrown from instead of the first free inventory slot.
- Tridents with Loyalty will return to the player when they enter the Void instead of being destroyed.
Item charge progress bar
- Bows, crossbows, axes and tridents now visually show how much they need to be charged in order to be used inside a progress bar that shows up in the hotbar when charging up the item.
- The bow bar shows how much the bow needs to be charged for the shot to be a Perfect Shot.
All the new features above are configurable, as usual.
Changes
- Reduced default Perfect Shot timeframe from 4 to 3 ticks (it's easier to do now with the new progress bar).
- Changed "Perfect Shot timeframe" option from seconds to ticks. This will cause the option to get reverted to the new default of 3 ticks.
- "Shield delay fix" is now an option under the "Vanilla bug fixes" section. It has always been enabled, but can be toggled now.
Bug fixes
- Increased compatibility of Magic Protection and Elemental Protection enchantments with mods which add magic and environmental damage types.
- Picking up a thrown axe when in creative mode will no longer duplicate the item.
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| rearm-2.5.0+26.1.2-fabric-sources.jar | Unknown | 123.18 KiB |
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:NHzN2FGz:DpMIPf7p"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NHzN2FGz:DpMIPf7p"
}

