LexManos

Simple, you don't have the same mods on the client as you do on your server.

GIVE ME YOUR LOGS There is ALWAYS logs! You may not understand what the logs say but we do. If you post again without logs, you're gunna be banned.

No, for deprecated names, they have been deprecated for over a minecraft version, modders have had adiquate time to adjust to Forge's changes. Beyond that it's Vanilla code that has changed. It may be a little bit of work but it's not hard.

I was hoping to have a build out today that was testable. But last night Adubbz found a pretty severe bug in the new ID management code in FML. being as it is christmas, cpw has been with his family. He'll get it fixed when he has a chance. I've told him that he is free to re-enable the jenkins build when he sees fit. As of right now, I will be gone at a convention until the 2nd. So don't expect any actual code from me. The other announcement is about the Fluid api. King_Lemming wanted to do a major re-work of it, but sadly due to real life issues {and well the hollidays, which admit it, are the same thing } he has not had the time to work on it. He has said that after the 1st he will have more free time and dedicate it to that. Basically, a Beta is just around the corner. I'll be gone for a week, but it's all good.

That pretty clearly states that you put the mods in the mods folder on the client only and used the installer on the server only. That would be consistent with the issues you were getting. How about you follow the damn rules and post your server logs, you know, like you're supposed to.

You do not get write access to the Minecraft Code anymore, This is to discourage people from editing base classes. The source code is linked in as a read only library. You can access it by opening the minecraft jar in the referenced libraries part of the project explorer. If you know what you are doing you can setup a writable work space, but its not being setup for you by default because that extra effort you go through is designed to discourage users from doing it. And put it behind a {al be it small} wall of competence.

The server needs the mods as well. It doesnt know the items exist unless you tell it they exist by having the mods on the server. This is basic modding here...

Make sure you're checking the right things. Witht he gradle the only choice is to Obfusicate to SRG names. It LOOKS like it's not reobfed, because it's in the middle stage. All function references should be func_####_ {Unless it's a method we add in that code it doesnt change}

https://bitbucket.org/luacs1998/forgelibrarydownloads/downloads/fmllibs16.zip Is the correct link, He didnt change the right one, I've fixed the eaq.

There is not much we can do to track down odd bugs like this. Your best option is to track it down yourself. Try taking out mods from your mod pack until it stops happening then re adding one by one until you can track down which mod is doing it. And then report it to that mod author.

Noything to do with us, you're using the wrong IC2 version for the version of MC you have installed.

Use the gradle.

Try giving the installer more ram when you run it, while luacus figures out his hosting issue.

Short answer, Never gunna happen. Long answer: 1) It is by far harder to update Forge then it is most mods {I say most as there are some exceptions}. So If I can update Forge {Including all the back end stuff you guys dont see} Then a modder can update to a new MC version. Most things when it comes to updates for the end modder, is the same thing repeated a million times. Int he case of 1.7 it's removing all referneces to Block.blockID/Item.itemID. When a modder understands what they need to do, it becomes more tedious then hard. 2) Minecraft Updates as of late are large yes, but they are no insane, there update cycle of 4-6 months is NOT crazy. I'ts prety good actually. 1.2: March 1st 2012 1.3: Auguest 1st 2012 (5 Months) 1.4: October 25th (4 Months) 1.5: March 13th 2013 (5 Months) 1.6: July 1st 2013 (4 Months) 1.7: October 25th 2013 (3 Months, This was bumped up due to Minecon) The last few updates have actually been done {partially} because of our interactions with the Minecraft team, We are slowly moving forward into a world where Minecraft modding WILL be stable, there is no reason for us to stagnate and hinder that progression. 3) I WILL NOT back port any Minecraft features to older versions. And If I stop updating to newer versions the entire fucking community will hound me to back port things. Ya.. this isn't gunna happen.

This children is why you don't use 3rd party launcher, We do not support them here.

Something is derping up your internet, provide it the assets. Also you should switch to the gradle system

User was banned for being a cunt, I gave you the solution to your problem, doesn't entitle you to go on a slurfilled rant.

Tip #1) Sob stories are bad #2) Make sure you don't have a ! in your folder path, that's typically the cause of "invalid or corrupt jarfile" as java uses ! to denote archive paths. #3) ALWAYS post detailed information of what you're doing, screen shots, log files, whatever you can get. The more information that is given the more likely someone can help.

You're missing mods, read the log to find out which.

You're using a language whos name is to long. It needs to be <= 7 characters.

https://github.com/MinecraftForge/Installer There is no 'hacking' going on, We just run Forge, using Minecraft as a Library.

Naw, team speak is annoying as crap. IRC is good enough to talk to most modders and if you want to work with certain groups of modders you just talk to them and ask them whats the best way to contact them. Setting up a teamspeak server isn't just about hosting, it's about time to dedicate to the administration of that server... not gunna happen.

Simple enough, use a non-broken launcher.

Give the installer more ram.