Skip to main content

RemapIDs

RemapIDs is a data-driven registry remap and alias system for modpack developers. Define JSON mappings that redirect item, block, entity, fluid, tag, recipe, and loot table IDs to alternative IDs at runtime — enabling seamless world migration when mods are removed, replaced, or reorganized.

Key Features

FeatureDescription
Vanilla & Modded RemappingRemap vanilla IDs to modded IDs (and vice versa) — including live block replacement with block state remapping
Wildcard ExpansionUse * patterns to remap entire families of IDs in a single entry
Type FilteringOptionally limit which remap types (block, item, recipe, etc.) a mapping applies to
Chain FlatteningAutomatically resolves multi-step chains (A→B, B→C becomes A→C)
Circular DetectionRejects circular mappings with clear error logging
Tag RemappingRedirect tag references with the # prefix, including tag-to-item conversion
Numerical ID SupportUse pre-1.13 numerical block/item IDs as sources for legacy world migration
Identify CommandLook up registry IDs of blocks and items in-game with /remapids id
Multi-File ConfigsOrganize remaps across multiple JSON files, processed alphabetically

Supported Platforms

LoaderMinecraft VersionStatus
Forge1.20.1Supported
Fabric1.20.1Supported
Fabric1.21.1Supported
NeoForge1.21.1Supported

How It Works

RemapIDs operates through two categories of remaps:

  1. Registry remaps (block, item, fluid, entity_type) are injected into the game registries after all mods have registered their content. These require a full game restart to apply. For block remaps, block state IDs are also remapped so network serialization stays consistent.
  2. Reloadable remaps (tag, recipe, loot_table) are applied when datapacks load and can be refreshed with /reload.

RemapIDs is configured through JSON files placed in config/remapids/remaps/. The /remapids id command is available in-game to help identify block and item registry IDs — see the Commands Guide.