Tags
Creators
Details
Licensed MIT
Published 8 months ago
Updated 7 months ago
All versions
1.2.0
Release
RESONANCE Update - 1.2.0 (1.21.11)8 months ago 124
Compatibility
Minecraft: Java Edition
1.21.11
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Any compatible version
Changes
Added:
- Full compatibility with Minecraft 1.21.11 (Fabric)
- Placeable Pet Bell block with floor, ceiling, and wall attachment support
- Redstone activation for the Pet Bell block (resonate sound + enchant particles)
- Block-specific config:
block_recall_range,block_recall_cooldown_seconds,block_particle_intensity,block_settings_mode - Reliable advancement unlock on bell ring (item or block) and on placing the block
Changed / Fixed:
- Pet List distance display now uses blocks; out-of-range shows
max+ blocks - Config loading now falls back to defaults safely and normalizes all values
- Tag detection uses dual CCA + command tag check with legacy
pettag auto-migration - Recall scan results are throttled and reused per player for performance
- Tameable checks use cached reflection lookups for modded entities
- Fixed default config migration (
block_settings_mode→"tool", particles →"minecraft:heart") - Fixed placement advancement triggering on non-Pet Bell block placements
- Fixed Pet Bell support model particle texture
- Fixed fox trust detection
1.21.11-specific fixes:
- Fixed world creation freeze (CCA component serialization mismatch)
- Fixed UI crashes (
Can only blur once per frame) - Fixed blank pet list entries
- Fixed pack metadata parsing (
supported_formats,min_format/max_format) - Fixed pet list stability (reverted experimental cache path, stabilized entity previews)
- Fixed unlimited recall scan bounds (now uses full build height)
- Fixed block entity state validation crash on placement
Optional dependencies
Any compatible version
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:bNbJd3RE:tTz1bTyp"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:bNbJd3RE:tTz1bTyp"
}

