Tags
Creators
Details
2.1.1
Compatibility
Changes
Changes Since The Latest Bug Report
Fixed
-
Fixed Crayfish stab/right-claw attack sometimes missing at certain distances.
- The stab hitbox was slightly too narrow/short for the distance where the AI could choose the attack.
- The Crayfish now re-aligns toward the target on the actual damage tick.
- The stab hitbox was widened and extended slightly to better match the animation.
-
Fixed Crayfish slam block-wave origin.
- The slam damage was already offset forward, but the visual block wave and knock-up were still centered under the mob.
- The block wave now starts from the same forward slam offset as the damage hitbox, under the claw impact.
-
Fixed invalid uppercase resource path warning.
- Renamed
Crab.animation.jsontocrab.animation.json. - This removes the Minecraft resource warning about invalid pack paths.
- Renamed
Changed
-
Added the same visual block-wave effect from the River-Prawn Greatclaw slam to the Crayfish slam attack.
- Uses fixed radius and fixed power.
- Does not scale with fall speed like the weapon slam.
-
Crayfish slam now also knocks up nearby targets through the block-wave system.
- The knock-up uses the slam wave origin under the claw impact.
-
Swamp Buster / River-Prawn Greatclaw can now safely receive both upgrade stones.
- Smithing Stone durability bonus is explicitly allowed.
- Somber Stone damage bonus is explicitly allowed.
notsoshrimple:swampbusterwas added to the smithing whitelist.
-
Blue Crayfish meme sound now plays when cycling variants with a stick in Creative mode.
- The sound only plays when the new selected variant is the blue variant.
- The existing config option still controls whether the sound is enabled.
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:4XgIMgL4:jGRDAPlu"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4XgIMgL4:jGRDAPlu"
}

