Hi,

 

I'm wondering why my language keys for my mod are working fine in my test environment and inside of eclipse, but do not work in the modpack FTB Beyond when I copy my jar from

the test environment into FTB Beyonds mods folder.

 

Quote

tile..justanotherenergy.solar_panel.name
Forge 12.18.3.2297
FTB Beyond

Minecraft 1.10.2

 

 

Quote

tile.justanotherenergy.solar_panel.name
Forge 12.18.3.2297
Test Environment

Minecraft 1.10.2

 

Spoiler

block.setUnlocalizedName(Constants.MOD_ID.toLowerCase() + "." + name);
block.setRegistryName(name);
GameRegistry.register(block);

 

I mean, how is it possible that such a thing happens with exact the same jar.

(Note: the log does not contain any information of this)

 

Bektor

 

EDIT: Just changing the name in the language file doesn't solve the problem. So adding the second dot in the language file does not solve the problem.

Also there does no second dot occur on those Strings, but they are also not translated correctly.

gui.solar_panel.energy_stored.name
  
I18n.format("gui.solar_panel.energy_stored.name");

 

Edited June 3, 20178 yr by Bektor

48 minutes ago, diesieben07 said:

Does it occur in non-dev Minecraft with just your mod?

No. With just my mod (my test environment) everything works just fine.

Thought in the FTB environment to which I copied my mod from the test environment it's also only

my mod having those problems.

31 minutes ago, diesieben07 said:

You will have to go through and add mods from the pack one by one.

Ok, I found the problem.

Edited June 3, 20178 yr by Bektor

1 minute ago, diesieben07 said:

Please describe it here for the future?

Well, I forgot to change the en_us to en_US thing while backporting.

Thought I've got totally no idea why it worked everywhere outside of eclipse and inside of eclipse with Forge 1.10.2 while it doesn't with exact the same version using FTB.

Edited June 3, 20178 yr by Bektor
grammar fix