Tags
Creators
Details
Licensed GPL-3.0-only
Published 4 months ago
All versions
1.2.1+fabric-1.21.1
Release
RemapIDs 1.2.1 (Fabric 1.21.1)3 months ago 18
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Changes
1.2.1
Fixed
- Tag remapping crash on Forge/Fabric 1.20.1 -
TagLoaderMixinwas injecting intoloadAndBuild(), which returns resolvedHolder.Referenceobjects, causing aClassCastException. Now correctly targetsload(), which returns rawEntryWithSourceentries. Also fixed on Fabric 1.20.1 where the same latent bug existed. - Forge world migration only handled
remapids:namespace -ForgeRegistryEventspassed the mod's own ID togetMappings(), soMissingMappingsEventonly caught missing entries with namespaceremapids:*. Now collects all source namespaces from the remap config and queries each one. This fixes remaps likecreate:brass_block → minecraft:copper_blockbeing silently ignored when Create is removed. - Forge registry lookups could cross-contaminate types -
ForgeRegistryMixinlooped through all registry types (block, item, fluid, entity_type) for everyForgeRegistry.getValue()call, so an item-only remap could incorrectly redirect a block registry lookup. Now determines the specific registry type from theForgeRegistryinstance and only checks that type. - Removed leftover debug logging on Forge - The Forge
RecipeManagerMixinhadLOGGER.info()calls for golden_apple recipe debugging and verbose per-invocation logging left from development. Cleaned up to match the other loaders'LOGGER.debug()level. JsonRemapper.rewriteCountthread safety - Changed from a plaininttoAtomicIntegerto prevent potential race conditions in the rewrite counter.
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:LS9KUmOO:l3swLqPl"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:LS9KUmOO:l3swLqPl"
}

