Ugdhar

1.7.10 is no longer supported here. You will need to update for support.

Post the whole fml-client-latest.log Make sure you're using the right version of abyssalcraft for the version of minecraft you're using.

We need the full fml-client-latest.log in your .minecraft/logs folder

1.7.10 is no longer supported

This post is over 3 years old, and 1.7.10 is no longer supported here.

1.7.10 is old and no longer supported, update.

1.7.10 is really old, and is no longer supported here. You will need to update.

please post the fml-client-latest.log from your .minecraft/logs folder

1.7.10 is no longer supported here, you will need to update to receive help. *edit: Your build.gradle is for 1.7.10, despite the subject line saying 1.12. If people help for 1.12, odds are it will probably not work in 1.7.10 since it is so old.

Read http://mcforge.readthedocs.io/en/latest/gettingstarted/ It explicitly tells you which files to move to your new project folder (steps 2 and 3)

First thing I noticed, is you do not need to use the AttachCapabilitiesEvent for a capability that is part of your own item, the initCapabilities method you overrode takes care of that. You would only use that event for attaching to an item that you didn't code yourself (i.e. a Stick or something) I haven't much time atm, so that's all I got for now, I'll look some more when I have more time.

It would be much easier if you uploaded your entire codebase to github Post all capability related classes otherwise pls (not to mention much harder to read code on here than github as well)

You should make all your registry names lowercase. You should set the unlocalized name using getRegistyName() after setting the registry name. Also, what version of Minecraft is this for?

If you're making a mod, post your code. You should also update from 1.8.9, it's getting old. If you're trying to use mods, one of them is a broken example mod.

I would say you could set those inside your item class if you wanted if they're the same for all batteries and wouldn't change per battery

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.