• v1.3.1 39b421531c

    RemapIDs 1.3.1
    All checks were successful
    Publish / Build Fabric 1.20.1 (push) Successful in 4m3s
    Publish / Build Fabric 1.21.1 (push) Successful in 2m32s
    Publish / Build Forge 1.20.1 (push) Successful in 3m52s
    Publish / Build NeoForge 1.21.1 (push) Successful in 4m25s
    Publish / Publish Fabric 1.20.1 (push) Successful in 7s
    Publish / Publish Fabric 1.21.1 (push) Successful in 6s
    Publish / Publish Forge 1.20.1 (push) Successful in 6s
    Publish / Publish NeoForge 1.21.1 (push) Successful in 5s
    Publish / Create Forgejo release (push) Successful in 4s
    Publish / Announce release in Discord (push) Successful in 3s
    Stable

    TysonTheEmber released this 2026-06-12 13:33:58 -06:00 | 2 commits to master since this release

    Downloads

    Pick the jar that matches your loader and Minecraft version. The same files are also on:

    Changelog

    Fixed

    • Modded registry IDs not remapped on NeoForge (#5, #6) — On NeoForge 1.21.1, mods are constructed before vanilla bootstrap, and bootstrap freezes the builtin registries before any RegisterEvent fires. The MappedRegistry.freeze() hook therefore ran against vanilla-only registries: wildcard patterns matched nothing, modded targets (including KubeJS-created IDs) were "not found", and aliases injected for modded source IDs were clobbered when the real entry registered later. Finalization and alias injection are now triggered from FMLLoadCompleteEvent (mirroring the Forge 1.20.1 fix from 1.3.0), which fires after GameData.freezeData() when all mod content is registered. This also fixes wildcard remaps for modded item/block IDs.
    • Recipe re-keying could overwrite existing recipes (#5) — Re-keying a recipe ID to a target that already exists (e.g. an entry without a types filter remapping aether:skyroot_stick → minecraft:stick while a minecraft:stick recipe exists) silently replaced the existing recipe. Colliding re-keys are now skipped with a warning, on all loaders.

    Changed

    • Entries without a types filter no longer attempt registry aliases for registries that don't contain the target — a typeless item remap previously produced "target not found in block/fluid/entity_type registry" warnings and pointless alias attempts. A typeless entry whose target exists in no registry at all now logs a single warning instead.
    Downloads