Ugdhar

The EAQ is the stickied topic at the top of the support forum:

Wrong forum, I don't think is really related to forge gradle, but also, 1.7.10 is no longer supported here, and your thread will likely be closed once a moderator sees it. I would advise updating to 1.10+ to get support, and although there are some mods that were left in the dust of 1.7.10, many have been updated, and there are many new ones as well.

You fixed the path shown in the screenshot so you're referencing the project folder containing build.gradle, and not the eclipse folder within that folder as suggested right? And if it's that Test project, it looks like it's already present in the workspace on the left. If it's not that project, make sure you're not trying to import another project named Test (I haven't tried to see if you can have multiple projects with the same name). Otherwise, I guess I'm not sure what's goin on.

You're right, sorry about that. When importing the project, if you're using a workspace the level above the folder your mod project is in, I think you just uncheck where it says to copy project files into workspace (since it's already there), and it should work.

With no intention of offending, you should really learn how to comfortably manage files/folders on your chosen operating system (windows/mac/etc.), and then proceed to make sure you understand basic java syntax. Without these skills, you will have a lot of trouble even trying to accomplish the most basic of things (especially if you're following the tutorials you linked, they're quite out of date, and will not help you unless you know some java already). While people here are great and will offer tons of help and advice, if you repeatedly demonstrate a lack of basic java/programming knowledge, your welcome will wear out quickly. Again, no offense intended, but the above quoted post indicates that you have a bit of homework to do before you're ready to start making mods for minecraft.

First, 1.7.10 is no longer supported here. Second, you got the package name on your proxy in the @SidedProxy wrong, you added "com." at the beginning, but that is not there in the actual package name.

You could always try the curse client, however if you run into issues, you will have to go to the modpack creator for help, for the reason larsgerrits explained above.

Show code, especially where you register all your stuff, it looks like you've got a null value somewhere you shouldn't.

Just remove it to test using a backup of your game. Then, if no crash, you know it's sponge causing it, and if it does crash, you have the crashlog requested to post here

https://www.google.com/search?q=how+to+disable+hiding+known+file+extensions&ie=utf-8&oe=utf-8 Tells you how to disable the hiding of file extensions, you can actually change your file names.

There is also a mod on curse called qubble that adds similar functionality as techne in game as a menu item. I haven't messed with it a ton, but it seems fairly cool.

Forge for 1.7.10 is no longer supported here. Upgrade to a newer version for support.

you're missing the class com.clowcadia.tut.proxy.ClientProxy; you probably named it something different.

If you're getting the same output as the last screenshot you shared, the problem is there is another program on your computer binding to the minecraft default port. Stop that program, or change the port your minecraft server is listening on (server.properties I believe)

You won't find much help for Minecraft 1.6.4 here. I don't think earlier than 1.8.9 (and even that is probably frowned upon) is supported. Here's a link to the EAQ for reference:

Just something I noticed checking out your tutorials, I believe you should not be using getItemModelMesher to register your models anymore, I think it should be using ModelLoader.setCustomModelResourceLocation. Just figured I'd mention it so you can show people the correct way of doing it.

Per the EAQ ( ) Forge 1.7.10 is no longer supported here, update to receive help.

Forge 1.7.10 is no longer supported here. Upgrade to receive support. (the EAQ states this as well as "read this first")

A per the EAQ (that said read before posting): http://www.minecraftforge.net/forum/index.php?topic=20.0 Forge 1.7.10 is no longer supported here. You must upgrade to a newer version to get help.

The EAQ (http://www.minecraftforge.net/forum/index.php?board=119.0) states forge for 1.7.10 is no longer supported, and you need to update for support here.

Not sure to be honest, might be time to start looking at newer/updated mods and bite the bullet and update, there are lots of great mods for 1.10.2+.

Forge 1.7.10 is no longer supported here, if you upgrade and still have issues come back for help then. (EAQ says read before posting: http://www.minecraftforge.net/forum/index.php?board=119.0)

I'd give disabling the loading screen a shot, as described in the EAQ.

The issues here is if you don't know what language you need to set for syntax highlighting, you really don't have any business trying to code a mod, and also, pasting your code so that it is all left-aligned, without any indentation, makes it such a pain to read, no one is going to attempt to make heads or tails of it as to where it's going wrong. Those are your 2 big mistakes, aside from whatever is actually broken in your code.

Sorry, I looked at that image too lol. Perhaps it's using another IC2.ini file from somewhere? Sounds silly but really only other thing that makes sense *Edit: the highlighted line in the image is line 54, not line 63 per the error. This gives a little more credibility to the theory that it's using a different config file from somewhere doesn't it?