LexManos

Not knowing any of the internals of the code for the mods related to your issue, All i can say is it's crashing in thermal expansions conduet code, your best bet is to ask them as they should know there code base better then us.

I'll see if I can make this into a common questions post: Will Forge still be free? Yes, it will always be free Will Forge still be open source? Yes, Open source all the way. Will Curse Launcher be REQUIRED to use Forge? No, you will still be able to download and install Forge exactly how you can now. The major end user visible change. Is that this forum, will be moved to a Curse controlled forum. And our download list (this) will move to CurseForge somewhere. The same exact files/setup. Just a different, more robust host.

Post logs, try running from command line: link in my signature. Make sure there are no ! in your path.

We do not support development for old miencraft versions. Your official answer will be to use 1.6/1.7 development. However, unofficially, you can manually fix the issues, we don't support it though.

Yes, but thats crappy and hard to push pull requests for. Having a repo setup with all the build system needed to start working on it would be the best use of your time for now. Then porting over to Forge.

Im bad at the whole talking to public thing, you all know that. But it needs to be addressed here, so that everyone knows. http://forum.feed-the-beast.com/threads/ftb-and-forge-curse-partnership.38512/ I hope that you guys are intelligent enough to understand that we are working twards the best community we can. I can't give out specific implementation details as we still have to figure them out. But, we want to keep you in the light. Update: 03/09/2014 So, Slow and I went out to Curse's office to discuss the deal this last week, Basically the Forge side of things are not going to happen for the near future. Until they get there functionality in place. All of the bits and pieces are there and it's REALLY promising, we just need to make it all functional before we can continue discussions on it. Not gunna go into to many details, going to have Slow do my PR So ya, none of the Forge stuff will change, so, ya.

Without a clean access to your source/setup all I can do is a preliminary. Quick glance at your base edits tells us that a large bulk of your changes can be done in Forge in one way or another. Also, FML has the CoreMod system which allows you to do edits to the Minecraft classes without actually editing the jar. My suggestion to you, would be to open up your project on Github, and switch to Forge. It will take some time to work through 'Forgifying' your mod, but it'll be worth it. You have to do major re-writes in 1.7 anyways, bite the bullet and joint he club.

That means that one or more of the mods you have installed explicitly requires 953.

2014-01-07 17:02:21 [sEVERE] [ForgeModLoader] The mod BuildCraft|Core (BuildCraft) requires mod versions [Forge@[9.11.1.953,)] to be available 2014-01-07 17:02:18 [sTDOUT] MinecraftForge v9.11.0.883 Initialized 883 < 953... Install 953 -.-

Reboot your comptuer into safe mode and delete the file there.

Yes, adding support for vanilla clients to connect to modded servers is in the works: But not done yet

Vanilla or Forge client?

2014-01-07 17:02:21 [sEVERE] [ForgeModLoader] The mod BuildCraft|Core (BuildCraft) requires mod versions [Forge@[9.11.1.953,)] to be available

Yes you are, read the log.

I HIGHLY doubt any of those mods are updated yet, make sure you are using mods for the correct version on minecraft you're trying to install.

Your backpacks mod is not a 1.7.2 mod.

Not sure what the heck is causing this, if you can reliably find a way to reproduce it, let me know. But ya, put in some prevention, lets see how that goes.

This is SUUPPER complicated so i'll go slow... Put The Mod In The Mods Folder. Did I go to fast for you?

Run it manually, or use the exe installer. Also make sure you don't have a ! in your folder path. If it still persists, provide more information/logs/screenshots.

So complicated, also a protip you shouldnt tell the server anything, the server is the one controlling things it should tell the CLIENT the extra info.

Why are you cleaning the cache... there is no reason to do this and jsut means shit needs to rebuild all the time. Also whats with the custom build file?

Stop making it complciated:

for (ItemStack stack : OreDictionary.getOres("copper")) if (OreDictionary.itemMatches(stack, other, false)) return true; Seriously, not complicated.

Not sure, because if this error was a real issue, with Forge itself, there would be tons of others coming along with this error. As that field is used in vanilla minecraft, and there for used in Forge. https://github.com/Mojang/LegacyLauncher/blob/master/src/main/java/net/minecraft/launchwrapper/LaunchClassLoader.java#L42 Actually, it is, the only issue left with it is that King has not had time to re-work the fluid system, everything else is ready to go and as soon as he does that we'll release a RB.

Humm, somehow jopt dissapeared from the server jar.. Use 994 it has it fixed, and i've tested fully. Got to love one broken thing hiding another...