Make Vanilla Variant <-> Variant Lib Variant Mappings Data Driven #6

New issue

Open

opened 2025-08-04 01:20:03 +00:00 by MerchantCalico · 0 comments

MerchantCalico commented

2025-08-04 01:20:03 +00:00

(Migrated from github.com)

This would be better if you could instead just have a JSON file which defines the mappings, like say...

{
    // "vanilla": "variantlib:id"
    "gold": "minecraft:gold"
}

This way, modpackers can create compat themselves if an author chooses to not do so or doesn't know about Variant Lib.

Currently, the vanilla Mooshroom and Rabbit variant enums are mapped to Variant Lib Variants through Java code, and may only be added through Java code, meaning that mods with variants which decide to extend an enum or use a registry can't be supported via Variant Lib unless a mod also has a Variant Lib initializer implementation for said variant. This would be better if you could instead just have a JSON file which defines the mappings, like say... ```jsonc { // "vanilla": "variantlib:id" "gold": "minecraft:gold" } ``` This way, modpackers can create compat themselves if an author chooses to not do so or doesn't know about Variant Lib.