For the "Recipe By:" Feature, Look Up a Data Pack's Name.
VT-14 opened this issue ยท 3 comments
This is a feature request. Currently JEI seems to display Data Pack recipe changes by grabbing the Namespace ID of the recipe, matching it to a ModID, and displaying that. If it can't find a Mod ID, it will use the Namespace ID and seems to capitalize the first letter.
My example Data Pack is this one: https://github.com/VT-14/VTs_Minecraft_Datapacks/tree/master/FileStructureExample(datapacks_folder)
The Data Pack's name is "Data Pack Name", and that is the name I would like to see the "Recipe By:" note list.
Instead, it shows this:
The "Recipe By:" shows "Namespace." For entirely additive changes, that works fine (make the namespace whatever you want to show up).
The issue is that this can cause the "Recipe By:" feature to point at the wrong thing. The 'normal' way for a Data Pack to tweak a recipe is to replace it under the original namespace.
So if I did a change to a Minecraft item under the Minecraft ID, it would show up like this:
There is no "Recipe By:" note, implying the recipe is from vanilla Minecraft. This could cause confusion to players, who previously play on a server or modpack with such tweaked recipes that say they are from the base mod, and then play on a different one and the recipe isn't there.
Alternatively, I could blame an entirely different mod by using their namespace id, such as this:
An obvious workaround would be to 'disable' (error out by making invalid) the original recipe and re-add it under a custom namespace, but that's more work and files, and not everyone will know to do that. If it is reasonably possible, I believe that getting the Data Pack's name rather than just the namespace ID would head off a lot of potential confusion.
This would be especially useful for packs with spaces or other symbols that are not allowed in namespaces, or where the data pack creator prefers a particular capitalization.
Question: Could a Data Pack add in an extra value be added to the JSON files that vanilla would ignore, but JEI could pull to get custom information (like a display name)?
