Don't bump, also go debug your mod, you're expecting us to do it for you?
Go find where its printing that error and see if you can make it print a stack trace.
There should be nothing in Forge/FML that would cause your GL drivers to error like they are, we do not touch anything related to the initalization of the gl drivers.
Also I am unable to find anyone that can reproduce this error.
The 1st pastebin link is invalid, however, if you are using 1.2.5, we're not officially supporting it anymore.
However, there isnt any know major issues so check the compatibility between whatever else you have installed and forge.
Something that you are doing is making it so that the uo class, ColorizerGrass isnt being found. This is a installation issue, not a forge issue. So start from scratch and figure it out.
Go look at the plethora of other launchers that do exactly what you want.
And do not post mojang code here.
You have to set the MC directory in Minecraft, not just the launcher.
The mere fact that it says:
2012-08-25 08:13:41 [FINEST] [ForgeModLoader] Library file guava-12.0.1.jar was downloaded and verified successfully
should mean you should not be getting that error.
Either way http://files.minecraftforge.net/fmllibs/fml_libs.zip
Download and extract that to the libs folder in your MC directory.
Ah yes, another mac user having the same problem of not being able to copy files correctly.
Google is your friend find a better archive tool. One that MERGES folder not REPLACES them.
One again you're not setting the minecraft directory properly.
Ive tested many times that setting the minecraft directory works with the new releauncher, so, go try again.
Next post that you have without showing your code and showing that you have tested thoroughly will result in your ban.
Just saying it doesnt work and not showing why you think it should it not valid.
Eah last time I used it it has a folder in the root of the MC dir.
And you could just setup those folders for yourself when the mod loads for the first time.
Anything more complicated then 'Put this zip in /mods/' is a bad idea
Instead of relying on on classpaths, you could write a little bit to load things from that folder first if they exist.
I dont get how people keep getting this error so far after this version has come out, leads me to suspect that they are doing something really stupid in the install process.
However, its 1.2.5, 1.2.5 isnt out anymore, so we don't support it/