Open citric-sulfur opened 6 months ago
I'm not sure how Jade handles the display of these items. Logically speaking it should be using the lang file, so it should change similarly to the tooltip display. I'll check at some point in the near future and get back to you.
Issue description
I'm currently working on modpacks that are available in various languages. I succeeded in applying the translated names of the items and blocks added to emendatus enigmatica, but I couldn't find a way to change the name of the ore that Jade mod displays. Is it possible to change the localizedName displayed in Jade mod to a lang file? If possible, I would appreciate it if you could also tell me how.
(I used Untranslated Items mod)
(I would like to change this part through the lang file.)
material\lifestone.json
{ "id": "lifestone", "source": "mod", "localizedName": "Lifestone", "disableDefaultOre": true, "processedTypes": [ "gem", "ore", "storage_block" ], "properties": { "materialType": "gem", "harvestLevel": 0, "isEmissive": true }, "oreDrop": { "drop": "kubejs:rough_lifestone", "min": 1, "max": 1 }, "colors": { "materialColor": "F0BEAE" } }
material\copper.json
{ "id": "copper", "source": "vanilla", "localizedName": "Copper", "disableDefaultOre": true, "processedTypes": [ "ore", "plate" ], "properties": { "materialType": "metal", "harvestLevel": 1, "isEmissive": true }, "oreDrop": { "drop": "minecraft:raw_copper", "min": 1, "max": 1 } }
lang\ko_kr.json
{ "item.emendatusenigmatica.lifestone_gem": "생명석", "block.emendatusenigmatica.lifestone_ore": "생명석 광석", "emendatusenigmatica.lifestone": "생명석", "localizedname.emendatusenigmatica.lifestone": "생명석", "gui.emendatusenigmatica.lifestone": "생명석", "jade.emendatusenigmatica.lifestone": "생명석", "item.emendatusenigmatica.copper_plate": "구리 판", "block.emendatusenigmatica.copper_ore": "구리 광석", "emendatusenigmatica.copper": "구리" }
Steps to reproduce
No response
Minecraft version
1.19.2 (Latest)
Forge version
43.3.9
Emendatus Enigmatica version
2.1.x (Latest)
Other relevant versions
No response
If a (crash)log is relevant for this issue, link it here: (It's almost always relevant)
No response