ZephireNZ

Minecraft now redownloads the jar if any of the default types are changed. If you're editing "1.6.1.jar", Minecraft will overwrite the jar because of the new mechanics. You need to copy the jar file and create a new version, such as "Modded1.6.1.jar". How to do that is shown in this video: The gist of that video is: - Copy the version you want to a new folder - Name the folder - Name the jar with the same name - Edit the name of the .json and the name inside the json with the same name You can then create a new 'profile' in the launcher that will use your custom jar file.

Did some further tests. It seems when copying over a minecraft.jar file from pre-1.6 will do this, creating everything in .minecraft. That's likely just because the entirety of 1.5.2 is ignoring the Launcher's requests. With a 1.5 jar that was downloaded after 1.6, however, it fails to launch at all. It seems that the forge code for 1.5 is breaking the net.minecraft.client.Minecraft class, hence stopping it from loading properly. Stacktrace: I'd say that because of the new launcher, and because of the majority of people (hopefully) wishing to switch to the new laucher, it might be wise to release versions of both Forge 1.5 and 1.6 that are compatible with the new launcher.

Creating a Forge profile on the launcher works fine if you have only 1 forge setup. I personally have multiple, so I relocated them to be in seperate folders (by using the inbuilt game directory feature, of course). However, it seems - for whatever reason - that Forge wants to put all of its own files in .minecraft. This makes it so all of Minecraft's core features are run out of the set game directory, but everything else, like the mods directory, resources/mods and so on, are being placed in .minecraft.