Remap IDs

2.0.0

Changed

• Live registry aliasing removed. Remaps no longer mutate lookup maps for registered IDs or redirect ForgeRegistry.getValue() for them. This eliminates the whole class of crashes where another mod looks up its own ID and casts the result (the 1.3.2 Create/Thermal ClassCastException was one instance; block/fluid/entity lookups were still exposed). Lookups of IDs that still exist always return the real registered object.
• World migration is uniform across all loaders. Chunk palette block IDs, item stacks, and entity type IDs in save data are rewritten at deserialization on Forge, Fabric 1.20.1/1.21.1, and NeoForge. Conversion persists when chunks re-save, so a fully converted world no longer depends on RemapIDs staying installed. Forge additionally keeps its native MissingMappingsEvent handling.
• JSON rewriting is context-aware. name fields are only treated as IDs inside typed loot entries (minecraft:item, minecraft:tag, minecraft:loot_table), so display-name fields are no longer corrupted. Loot-table reference entries now honor loot_table remaps and tag entries honor tag remaps.

Added

• Missing ID resolution — registry lookups of a remapped source ID that no longer exists resolve to the target, so custom recipe types, advancements, /give, and other mods' JSON referencing a removed ID keep working. IDs that still exist are never redirected, so this cannot cause the crashes that live aliasing did.
• Entity type remapping in world data — saved entities, passengers, and spawner spawn data are remapped on all loaders.
• 1.21 recipe result support — recipe results using the id key (and 1.20 string-form stonecutting results) are now rewritten.

Removed

• Block state ID patching (Block.BLOCK_STATE_REGISTRY). Block conversion happens in the chunk palette instead, which is lossless for matching properties and no longer risks corrupting network state IDs.