Ugdhar

I would just use the Forge Energy capability API. Doesn't have any dependencies, and as far as I know is compatible with RF in recent versions. I was tinkering with energy a bit recently, and the generator I made was able to supply power to machines from ThermalExpansion. I know that's not a definitive "it's globally compatible" or anything, but it at least demonstrates it works with stuff other people made.

Please post the entire fml-client-latest.log in spoiler tags *edit: Also, 1.7.10 is no longer supported, so you won't get help for it here.

It's all in the github repo there, just browse around the source files

I've been creating my creative tab right in my mod class near the top: public static final CreativeTabs TEST_TAB = new CreativeTabs("test") { @SideOnly(Side.CLIENT) public ItemStack getTabIconItem() { return new ItemStack(Items.REDSTONE); } }; I haven't messed with it much, but I do recall it wouldn't use my test item for the tab icon because my items hadn't registered yet, and I haven't as of yet bothered to try and fix/change/figure it out. But besides that works fine as far as I can see.

Look for "targetCompatability" in your build.gradle, see if you can change it to 1.8 there.

This link has a great example of using registry events to register stuff.

I also see net.minecraftforge.fml.common.MissingModsException: Mod twilightforest (The Twilight Forest) requires [forge@[14.23.0.2501,)] And you're running forge 14.23.0.2491

Please upload your code to a github (http://www.github.com), we're going to need to see pretty much every class because everything in your code calls/references something else, and we need to see how it fits together to see where your null is.

Post your entire fml-client-latest.log file in spoiler tags please

You made your main mod class abstract, so it can't be instantiated.

1.7.10 is no longer supported here, you will need to update to get help here.

Post the full fml-client-latest.log, the bit you pasted doesn't have any real info or even a crash in it. Use spoiler tags (the eyeball button)

Are you building your jar with gradlew build? Beyond that, you'll probably need to post code, as despite checking it twice, there is still something that must be wrong since it doesn't work, and more eyes could help find it.

1.7.10 is no longer supported here, you will need to update to get support.

Did you build your mod jarfile using gradlew build? How did you install the forge server files?

1.7.10 is no longer supported here, you will need to update for help.

Post your fml-client-latest.log file, it should have information to help figure out what's wrong.

Post a screenshot of your mods folder, as well as fml-client-latest.log so we can see what's goin on

I would (in fact I did) just get a free dynamic DNS setup. http://www.noip.com lets ya get up to 3 for free, all you have to do is confirm you're still using it every 30 days. I've seen hamachi mentioned before, but never used it, so no idea how to fix it.

Any reason you're not using 1.10.2? I believe there were a lot of bug fixes between 1.10 and 1.10.2. Unfortunately, I have no idea looking at that log what is wrong, is there a crash report or anything as well?

Do a bit of reading on variable scope. You can't declare a variable in one method, and have it accessible in another method.

Post your code to github and link to it here for more help, are you setting the registry name in your ItemStraw? edit: also when posting a long error report like that, you should use the spoiler tags.

Where are you registering this event on the event bus? What does it do when you run it? Do you ever make it to that inside condition where you're attempting to add the drops? Does the fml-client-latest.log say anything?

I would also not use a # in my modid (I'm not sure, but I would bet special characters are prohibited), and modids need to be all lowercase.

That's just silly. Your log shows us all the mods you're using anyway lol. Anyway, I would hazard a guess that it has something to do with Extra Utilities, since I see it mentioned in the crashlog. Try removing that and seeing what happens.