Ugdhar

You will likely get more help if you post your code on github instead of in a zip file. Not to mention version control is cool

Items (like Blocks) are singletons, so there is only 1 instance of your Item class being used for every item of that kind in the game. That's likely why all your batteries are sharing their charge. If you wish to have an independent value for your item, it either needs to be stored in Metadata (limited amount of storage, I forget how much), or you will need to use capabilities. Just search this forum for "item metadata" or "item capabilities" and you should find something to get you started. There is info on both of these in the forge docs as well. *edit: Here's a link to a capabilities tutorial that I believe is helpful: https://www.planetminecraft.com/blog/forge-tutorial-capability-system/

https://vazkii.us/p/a-semi-technical-explanation-of-why-you-shouldnt-allocate-too-much-ram-to-minecraft/ I would try less than 10G and see if that helps.

1.7.10 is no longer supported, you should update.

You're better off continuing to post here, I'm not always available to help, and there are plenty of others here just as knowledgeable as I am, and even more experienced with forge than me.

Ok, 1.8 is getting old, so you should really think about updating. I doubt it will continue to be supported for very long, considering we're at 1.12. Continue registering things in init/preinit where applicabile, since the registry events are 1.11+ (although I thought I saw someone say later 1.10.2 had them). In your main class Init you call GameRegistry.register(enugget, "EmeraldNugget");, I believe that should be lowercase, and the same as your asset names.

You should use the registry events to register your items. Here is a good link for reference: http://www.minecraftforge.net/forum/topic/49497-1112-is-using-registryevent-this-way-ok/#comment-249433 Don't use Minecraft.getMinecraft().getRenderItem().getItemModelMesher() , use ModelLoader.setCustomResourceLocation. IDs (mod, item, block, etc) should all be lowercase, both in code and assets (class/field names are fine to be mixed case, but registry names modid etc should all be lowercase) Which version of MC/Forge? Also, you should put your code on a github repo, it makes it much easier to look at plus version control is cool

Then you're going to have to check with the author to see if they have a jar for the dedicated server

It should be in the logs folder, which should be in the same folder the mods folder is in

Post the fml-client-latest.log You could also try removing mods 1 by 1 (or start with 0 mods, and add them in 1 by 1) to determine which is causing the crash.

Try removing toomuchtnt It looks like it's calling a client function, which will crash a dedicated server (but works in single player, since the server/client both exist)

As a side note, you should probably go for 1.11.2 at the earliest, and preferably 1.12.x. I don't think 1.10.2 will be supported here for much longer.

Yeah, plus you're running 1.7.10, which is old and unsupported as well. I'd update both.

My guess would be that there are mod dependencies missing. Are you sure you installed all required mods on your server? Also there should be a fml-server-latest.log file, if you could post that somewhere I think it would help

Check this link out, it's a great display of using the new registry events. http://www.minecraftforge.net/forum/topic/49497-1112-is-using-registryevent-this-way-ok/#comment-249433

1.7.10 is no longer supported here, update if you'd like to get help.

I haven't done a lot of messing with recipes, but I doubt it.

Out of curiosity, what was the issue?

Also instead of setUnlocalizedName("light_blue_stairs"); setRegistryName(Reference.MOD_ID + ":" + "light_blue_stairs"); you should do something more like setRegistryName("light_blue_stairs"); setUnlocalizedName(getRegistryName.toString());

It looks like your pattern has 4 spaces across in each row, maybe removing the extra spaces will help?

What minecraft folder are you talking about? And bumping after an hour, come on guy.

I think this probably means you're going to need a RAM upgrade if you want to decompile MC. You could try setupDevWorkspace instead of the Decomp, so you can still develop, you just won't be able to view the MC sources.

http://www.minecraftforge.net/forum/topic/49497-1112-is-using-registryevent-this-way-ok/#comment-249433 This is a decent example of how to use the registry events to register items/blocks

SkyFactory 3 is for Minecraft 1.10.2. I don't imagine it's been setup to work with 1.12. *edit: was trying to include a screenshot, but evidently it doesn't like pasted images.

This post is over a year old, you should probably start your own post. Start a new post, and post the contents of your fml client latest log