Started by sTiKyt
on Sat, 11/11/2017 - 01:32
Topic category: Bugs and solutions
Guys, you create error in mcreator.
Dont name files in up registry(en_US.lang) becouse it dont work!
Name it:( en_us.lang ) in down registry, it work!
Topic category: Bugs and solutions
Guys, you create error in mcreator.
Dont name files in up registry(en_US.lang) becouse it dont work!
Name it:( en_us.lang ) in down registry, it work!
We will fix this in next update. Thank you for your report!
EDIT: Which version of MCreator are you using?
Latest, 1.7.5 - Mcreator
1.11.2 - Minecraft
And please, add normal ore dictionary editor xD
Becouse: OreDictionary.CreateOre("oreCopper", OreCopper);
dont work in 1.7.5 version...
Relly dont work, i dont have errors, code working but ore dictionary dont work...
Thank)
MCreator 1.7.5 creates lang files with lowercase names. Did you create a new workspace or you imported one from an older version?
It is nothing weird that OreDictionary#CreateOre() doesn't work, because method with such name doesn't exist and as far as I know, it has never existed. The method is actually OreDictionary#registerOre().
I think that MCreator has generated the lang file uppercase as well, however, there is a quite easy permanent fix. Go to MCreator\forge\src\main\resources , there is a file named pack.mcmeta. Open it and set pack_format to 2. This enables the old legacy format.
Can you tell me where to put this code?
You have to put it into the pre-initialization FML life cycle.
Guys, i did buy new laptop, install Windows 10, install Mcreator latest version, create new workshop(use default).
I dont import workshops , i create little modification, and in test minecraft it named: text.print.text(example)
I export my modification and open it, using 7z.exe, in .jar file i find languages folder and in i see: en_US.lang file.
I rename en_US.lang to en_us.lang, and my text.print.text(example) renamed to: Print (again example xD)...
All understand?)
P.s Sorry for my English, i learn this one month xD
Thank)
MCreator generates lowercase file name starting with 1.7.5 version. But if the user imports old workspace which contains the uppercase version of lang file, Windows doesn't rename it as it considers new file name the same as the old one.
Nope, i use new workspace but it in Upcase xD