All versions
1.2
Release
1.210 months ago 16
Compatibility
Minecraft: Java Edition
1.21.3
Platforms
Fabric
Forge
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Changes
Keystone Expansion β Pufferfish Skills
Changelog β v1.0.1 (MC 1.21.3+)
β Compatibility
- Added full compatibility with Minecraft 1.21.3+ (changes introduced since 1.21.2 regarding attribute IDs).
- Loaders supported (unchanged): Fabric / Forge / NeoForge.
π§ Fixes
- Fixed datapack loading failure:
skill_tree_for_pufferfishs_skillsno longer crashes with:Unknown attribute minecraft:generic.*Unknown attribute puffish_skills:player.*
𧬠Attribute Registry Migration (1.21.3+)
Vanilla (Minecraft) attributes
- Migrated all legacy
minecraft:generic.*identifiers to the new registry format:minecraft:generic.attack_speedβminecraft:attack_speedminecraft:generic.armorβminecraft:armorminecraft:generic.armor_toughnessβminecraft:armor_toughnessminecraft:generic.max_healthβminecraft:max_healthminecraft:generic.knockback_resistanceβminecraft:knockback_resistanceminecraft:generic.luckβminecraft:luck
- Updated
minecraft:player.block_interaction_rangeβminecraft:block_interaction_range
Pufferfish attributes
- Migrated legacy Pufferfish Skills attribute namespace to the correct mod registry:
puffish_skills:player.*βpuffish_attributes:*puffish_attributes:player.*βpuffish_attributes:*
π¦ Notes
- This release targets MC 1.21.3+ only.
If you still need MC 1.21.1, keep using v1.0.0 (separate jar recommended). - Make sure Pufferfishβs Attributes is installed, as skill rewards now reference
puffish_attributes:*.
Release: v1.0.1 β MC 1.21.3+
Type: Compatibility + Data Pack Fix
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:etNXlw3S:FBdBGyd2"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:etNXlw3S:FBdBGyd2"
}

