DeadSix27

I have this issue on 1.10, means it can't be fixed that way or at all?

Is this going to get added into the 1.10 branch as well? (I applied the same change myself, but after I built it and tested it the server still had that issue, so I guess it's not that easy)

Oh I see, did the translation code change and the mod authors simply didn't implement the new change yet? And the same happened with the tps command (e.g forge devs forgot about that) Either way, added an issue now: https://github.com/MinecraftForge/MinecraftForge/issues/3722

Well, the issue kinda seems related, considering its a very similar behavior (e.g the stuff gets not translated)

More examples: Server side: tps shows only "commands.forge.tps.summary Client: JEI buttons have no translation (even though they should) However tps works just fine (unlike on the server) The One Prope has the same issue with enderIO translations (but ive seen a missing translation log message for this particular case i think) Both: A lot of items have no name like: tile.WallpaperCraft:tintedglassblue_12.name, tile.chisel.glass.name however a others do.. Should I report this on the issue tracker of Forge?

Forge version: forge-1.10.2-12.18.3.2234 Mod list: https://share.dsix.tech/modlist.txt For some reason a lot of messages are not being replaced with language-file-translations, e.g the placeholder messages will be used rather than the english (or any other lang). For example: The command tps will show: > forge tps [07:01:47] [Server thread/INFO]: commands.forge.tps.summary Instead of replacing it with: "%s : Mean tick time: %d ms. Mean TPS: %d" etc That issue exists in many instances, e.g JEI translations and so on. The server runs on Linux and its locale is set correctly $ locale LANG=en_US.UTF-8 Additionally I tried starting the server with: -Duser.language=en -Duser.country=US that did not solve it. Any idea why this is happening?

Unfortunately the neighboring blocks idea doesn't work in my case, as for example, it can be on any of the 3 sides in a corner of 3 blocks.

What could cause the facing and colour to be wrong upon world load though? I got it working but only until I save and close the world. Then when it loads the world data the states are wrong.

I figured it has something to do with that, the whole bit code there is a little beyond my experience, never worked with bitshifting, I will have to read more into that. EDIT: However I should also look at Tile Entities, I guess, I read about people using the tile data for colour and the state for facing, which would allow for a bigger range of colours too.

So in short the example is wrong? Meaning @Override public int getMetaFromState(IBlockState state) { EnumFacing facing = (EnumFacing)state.getValue(PROPERTYFACING); EnumColour colour = (EnumColour)state.getValue(PROPERTYCOLOUR); int facingbits = facing.getHorizontalIndex(); int colourbits = colour.getMetadata() << 2; return facingbits | colourbits; } would return a number bigger than 15?

So I have experience in other languages and a little in Java. But no experience in Forge / Minecraft modding. And I came to an issue I am unable to solve: I worked mostly of the examples made by https://github.com/TheGreyGhost/MinecraftByExample/ I nailed my issue down to the overridden functions getStateFromMeta and getMetaFromState. So the issue is: My code crashes with the following stacktrace: net.minecraftforge.fml.common.LoaderExceptionModCrash: Caught exception from Test (testmod) Caused by: java.lang.ArrayIndexOutOfBoundsException: 18 at net.minecraftforge.fml.common.registry.GameData$BlockCallbacks.onAdd(GameData.java:303) at net.minecraftforge.fml.common.registry.GameData$BlockCallbacks.onAdd(GameData.java:284) at net.minecraftforge.fml.common.registry.FMLControlledNamespacedRegistry.addObjectRaw(FMLControlledNamespacedRegistry.java:584) at net.minecraftforge.fml.common.registry.FMLControlledNamespacedRegistry.add(FMLControlledNamespacedRegistry.java:482) at net.minecraftforge.fml.common.registry.FMLControlledNamespacedRegistry.register(FMLControlledNamespacedRegistry.java:829) at net.minecraftforge.fml.common.registry.GameData.register_impl(GameData.java:254) at net.minecraftforge.fml.common.registry.GameRegistry.register(GameRegistry.java:153) at my.testmod.StartupCommon.preInitCommon(StartupCommon.java:27) <--- First problem is, the stacktrace is not detailed enough, all it points me to is: GameRegistry.register(testBlockVariant); Is there a way to get more out of the stacktrace in Java/Forge/Minecraft? But I was able to find what is possibly the cause of the crash, its somewhere in the Meta/State functions. Here is the full BlockTestBlockVariants.java https://gist.github.com/DeadSix27/3f508233175d7e5874ce18aa32698053 and StartupCommon.java https://gist.github.com/DeadSix27/2997707637f59db7c81d82ee7c7e5159 If you need any more information or files, tell me.