Closed mc-kaishixiaxue closed 4 years ago
Minecraft Version:
Forge Version:
Mod Version:
Single Player or Server:
Describe problem (what you were doing; what happened; what should have happened):
tile.crystal.name=Celestial Crystal
tile.crystal.name=Crystallized Obsidian
tile.crystal.name
Unlike registry names, translation keys are not namespaced. It is therefore highly recommended to prefix your modid somewhere to the translation key (e.g. examplemod.example_item) to avoid naming conflicts. Otherwise, in the event of a conflict, the localization of one object will override the other.
Video/images/gifs (direct upload or link):
non-critical issues like this wont be addressed in 1.12 at this point in the lifecycle. Working on brand new mods and 1.14+ ports
Also forge fixes it by default in 1.14
Minecraft Version:
Forge Version:
Mod Version:
Single Player or Server:
Describe problem (what you were doing; what happened; what should have happened):
tile.crystal.name=Celestial Crystal
For Cyclic: https://github.com/Lothrazar/Cyclic/blob/develop/src/main/resources/assets/cyclicmagic/lang/en_US.lang#L159tile.crystal.name=Crystallized Obsidian
The two files both havetile.crystal.name
, because Cyclic doesn't have namespace on language file. https://mcforge.readthedocs.io/en/latest/concepts/internationalization/#usage-with-blocks-and-items said:Unlike registry names, translation keys are not namespaced. It is therefore highly recommended to prefix your modid somewhere to the translation key (e.g. examplemod.example_item) to avoid naming conflicts. Otherwise, in the event of a conflict, the localization of one object will override the other.
Video/images/gifs (direct upload or link):