The_Paragon

That is a good idea. I'd just like to make one more note, however. I'm not going to tell you how to operate, but I strongly believe that situations such as this have a great potential to bite Forge in the ass later on. If there are any hitches at all, regardless of whether Forge is at fault, people are going to make noise (as I did) or worse, turn to services such as MCPatcher or the growing number of ahem "Modpacks with installers", which will only create headaches down the road when (not if, when) these services fail. Letting the noobs know that there's a low-hanging branch for them to smack their head on will at the very least transfer the responsibility unto them when they run right into it despite your warnings. Let me say this in conclusion: I love Forge. Forge is the best Minecraft API bar none, and the strides it has taken (most notably the recent appropriation of ModLoader and AudioMod functionality) only serve to increase my respect for it. I know Forge is doing its best to improve the user-end experience - and those examples I just gave prove it! But please, remember those who don't have a complete understanding of what's going on under the hood.

Ahhh! Success! I knew I was probably doing something wrong! Thank you for your help. It might behoove you to throw up a warning on the installation documentation for Mac users. They are not offered a "MERGE" option when it comes to moving files around, it's either REPLACE or DONT REPLACE. I am forced to manually navigate to each individual folder and add the files. This was also the "issue" with a past version of Forge, to my knowledge, wherein the Applet was not included in the release, and every Applehead was accidentally destroying their Applet causing Minecraft to hang on the "Updating" screen forever. Not Forge's fault by far, but at least warning people about these potential problems would probably improve the signal-noise ratio on these forums significantly. Thanks for your time, Lex

Hello, Lex! Posting here because I have an identical issue. Running OSX, latest version of Mac Java. This occurs on a clean installation of Forge with NO mods installed. Forge version is the recommended build here, version 3.3.8.152: (http://minecraftforge.net/forum/index.php/topic,5.0.html) I am installing Forge, and only Forge into a clean, freshly downloaded vanilla minecraft.jar, deleting META-INF. The client seems to launch fine and mods seem to play, but the ingame "Options" menu reports the sound to be "OFF" and any attempt to change the slider results in the aforementioned crash. Forgemodloader-0.log: Stack trace, reported by Console: If you require any further information I am more than willing to assist. My suspicion, however, is that the version of the LWJGL that Minecraft ships with is out-of-date.