robobanana99

Yes I do, It all works fine in eclipse but as soon as I build it, It no longer works. I've checked against other mods and cant see anything odd

Whenever I try to build my mod using gradle, the mod builds successfully and the textures work, but the languages don't work in-game. Is this a known bug and how do I fix my localizations?

Thank you so much Probbably not the proper way round it but it works for now!

Oops, my keyboard derped there. /give playerName atomicraft:compoundItem gives me the item but as soon as I even try to right click it, I get an itemstack out of bounds -1. Also, if I create a world, quit the game, relaunch mc and join that world, everything is still there meaning that the things only disappear when leaving and rejoining in the same game session. Ok heres my init code where the items are first referenced http://pastebin.com/hYRmwLfT and then my item init code http://pastebin.com/3dgyQ5bm

I'm confused, as I have now made my unlocalized names the same as the names I used in GameRegistry.registerItem. Another thing, I can spawn the items in using /give playerN

Errm, derp on my behalf at no point was I giving any form of item or block Id. How do I give an id to a block or item?

Yes it does happen on fresh worlds when leaving and rejoining

Also, this only seems to occur on the client, the server seems to be fine

Ok, thanks for the tip. I'm using GameRegistry.registerItem(compoundItem, "compoundItem");

Here's the error: http://pastebin.com/zTFpzXz5, I think it is being caused by my other bug report. Thanks

Hello, I am a modder. I've begun updating my mod to 1.7.2 using forge 10.12.0.1013 when I realised that when I left a world and then rejoined, all the mod blocks / items disappeared and left this error in the console: http://pastebin.com/8e5Nt7w7. As far as I can see, it's detecting the missing blocks / items and saying that they are missing but still connecting to the world with the mods: ([07:26:42] [Netty IO #3/INFO] [FML]: Client attempting to join with 4 mods : [email protected],[email protected],[email protected],AtomicAPI@v1) I was wondering whether it was: A bug in forge An issue that I needed to fix If it was a mistake on my part, how would I go about fixing it and what are the common causes of this error? Thanks