LexManos

Use the new installer. Or, manually install the libraries. Or, better yet, stop using 1.5.2. There is no reason to stay on 1.5.2.

http://www.minecraftforge.net/forum/index.php/topic,12728.msg65980.html#msg65980

Running virtual machines typically screws over any 3d program, or anything that does complicated work with the graphics/audio. This error is typically caused by incompatible/out of date audio drives {since it's OpenAL} It's not advised to run minecraft in a VM.

For jar mods {which you should NEVER DO ANYMORE} you need to add a new versions folder. And then select it using the 'Use Version' in the profile. The mods/{mcversion} works, but it doesnt split everything off like you want. That is, quite literally what 'Game Directory' is for -.- Moving shit out of the standard folder. mods/{mcversion} is NOT DESIGNED for incompatible mod sets as it doesnt move the worlds It doesnt change the config folder it doesn't change what jar launches the game it simple is a place where you can put MINECRAFT version specific mods. Anyways, don't use jar mods if the official answer you're gunna get.

1) Don't hijack other's threads 2) The problem is that the class is not found, typically an issue with you not installing things correctly.

I know, use the installer. Or manually install the libraries.

Use it -.-

If you share the same folder between profiles of corse the same data/saves/mods/configs/whatever is gunna show up in both profiles. Thats what the 'game directory' option in the profile config is for. I typically just setup everything to .minecraft/profile/{name} And it's basically a copy of the needed files in there. This is nothing to do with Forge, this is basic minecraft setup.

Use the normal launcher. We can't control other launchers. What are you trying to do?

One of your coremods has not updated to 1.6

One of the mods you have installed does not support dedicated servers. You'll have to figure out which one.

However you're launching minecraft isnt including the libraries.

Interesting, the last line would apear to be galacticcraft, Coremods do have the tendancy to do weird things. What I woudl advise is removing mods one by one untill the issue is resolved, and then re-adding them untill it breaks again, so you can figure out which mod is doing it.

The only official solution you're gunna get from us is to update to 1.6.4. We do not support older builds. And it looks like you're sadly mistaken by a lot of you mods. Also, if your mod hasn't updated since 1.5.2 then you should drop the mod. It doesn't take 5 months to update -.- any mod who has taken that long probably will never update and you should cut your losses right now.

Installing forge adds a 'version' to the new launcher, and then you can just go into the profile and select any version you have installed. Simple as that: No fumbling with jars or folders at all. {Unless one of your mods is incompatible with the version you select, there's nothing we can do about that}

Then you're doing it wrong, And we can't help those who don't post logs. Either way 1.5.2 is out of date and you should update.

We're actually moving away from decompiling minecraft being the standard. 1.7 development will be gradle based and decompiled only if demanded. Your source will be separated from Minecraft's source.

No, no side effects at all. Upgrading to forge cdirectly is where you wanan go. If you do however have a Foretess.dat in /world/data then move it to /world/dim-1/data and you wont even have to run around. The format is the same. The reason it need sto be per world is that the format doesnt contain any world identifying data so there is no way for us to tag what world that data is for.

Yes, because 1.5.2 has been EOLed for that setup. Any mod pack or any other reason why you are still on 1.5.2 should provide there own mirriors for the libraries. We've asked them to do this for months, and since we now have a better solution for our end, meaning I just made installers for all 1.5.2 builds, we are not directly supporting the fmllibs download anymore. Hexxit, and any other mod packs SHOULD of been shipping the libraries from the get got.. How can you call yourself a complete pack if you don't have all the required files? Your choice are 1) Update to the new distribution of libraries 2) Update to something other then 1.5.2 or 3) Ship your own libraries.

Don't use 1.5.2, update.

Do not 'rip a backup out of ftp' The proper solution would be to use the new installer for 1.5.2 instead of the old method. Or, just fucking update. 1.5.2 is officiall EOLed from us and isn't supported. And considering fmllibs/scala-library.jar was eating almost 700GB/day in traffic {1/3rd of our total} I decided to provide a better solution.

That, is actually a bug, I had it working locally, because I had the patch locally but for someone reason it didn't go along with the inital commit.. so, use build 916: https://github.com/MinecraftForge/MinecraftForge/commit/7d5d191fc2f735abcb4648a03800c80580d196f1#diff-1

Interesting, usually when things like this happens it throws something about not being able to open font files or some shit. But this is just nothing. Sadly, without someone who is experiencing the issue giving us direct access to debug on there computer, or us being able to reproduce it our end... there's not much we can do.

You'd have to ask your hosting provider exactly. But the simplest way is to just use the installer locally, select install server. Point it at a empty directory and then once it's all setup upload the entire directory to your host.

Yes, one of your mods is not 1.6.4 compatible.