Simple Registry Aliases

The modification provides access to Fabric API's alias system through a convenient configuration approach. You can assign alternative identifiers for Minecraft registry elements in any convenient way.

Functionality covers both static registries (items, blocks) and dynamic ones (crafts, biomes).

Configuration Setup

All alias definitions are stored in the ./config/registry_aliases/ directory as JSON objects. For standard registries, files are named by the path <registry_path>.json - for example, item aliases are located in item.json, blocks in block.json, and biomes in worldgen/biome.json (where worldgen is created as a separate folder).

For custom registries (also works for standard ones) the name format includes the namespace: <namespace>/<path>.json. For example, the magic_mod:spells registry requires the file magic_mod/spells.json.

The file structure is extremely simple - a JSON array where keys contain source identifiers and values contain replacements. Consider this example from ./config/registry_aliases/item.json:

{
  "toomanymetals:enderite_pickaxe": "minecraft:netherite_pickaxe",
  "toomanymetals:enderite_axe": "minecraft:netherite_axe"
}

After loading such configuration, all toomanymetals:enderite_pickaxe items are automatically converted to minecraft:netherite_pickaxe when accessing the item registry.

Important limitation: replacement occurs only when the target registry element doesn't exist in the system. If the element is already registered, the module uses the original version regardless of settings.