LexManos

Quit getting your panties in a bunch. 'MinecraftByExample' should definitely know better than that. And then only reason anyone actually does use explicitly wrapped Object[]s in there is because they are copy/pasting from decompiled code 69 times removed. And no you shouldn't be yelled at for your coding style if you choose it. However people who are claiming to be teachers SHOULD be yelled at for copy/pasta. Anyways, stop teaching bad habits and copy/pasta code. Thread over.

define corrupt, its fully functional.

TSteelworks{1.6.4-0.0.4.2-fix2} [Tinkers' Steelworks] (TSteelworks-mc1.6.4_0.0.4.2-fix2.jar) Unloaded->Errored i wonder what it could be.....

lower your view distance

lower your view distance

new Object[] { No, Bad modder stop it!

Log

immibis just needs to not be stupid and compile his mods to target the same version of java that Minecraft targets.

If it was a simple thing to detect we'd have it done. But the consensus is that due to the 1% of broken computers we're gunna have to do a 'Lets test this on first run' type thing. Trust me I know how frequent it gets reported. From the looks of it, it's a common driver doing GL in a way that is contrary to the GL spec, but hey we have to support it.

config/splash.properties set enabled to false, your mac video drivers are crap and don't support the new load screen.

Update Forge

Take a look at where IStateMapper is used. It is designed so that you can tell the game what states in your block are useful for the model. Sugarcane for example tells it to ignore 'age' which is why the state json doesn't have anything related to age.

Seems that the installer cant find the JRE. It searches in the common install folders {profile files} as well as the JAVA_HOME environment variable. It cant find it in either of those so it errors. What you could do is run the installer with java manually by doing: c:\program files\{wherever you installed java to}\bin\java.exe -jar {forge installer}.exe

Remove any mod with Chicken in the name or 'CCL' 'CCC' and try again.

Seems like you are having issues outside the scope of Forge/Installer. https://github.com/MinecraftForge/Installer/commit/8ebfa46e07357163ca9c5b142bf950787a515e2c The log file will be <CurrentJarName>.log. Or if you run the installer from the command line it'll spit everything into the console window as well. You may want to go look into process monitor to see where the installer is trying to write files. Because it's sitting there doing something and thinking it's installing correctly. And without logs, or sitting there trying to walk you though all possible debugging steps {killing antiviruses, running as admin, disabling UAC, and so on} there isn't much we can do. Modern installer will only create the JSON and not the jar because that is no longer needed. Make sure you have write access to everything in the .minecraft folder. From the sounds of it you may have permissions issues.

The logs are created right next to the installer. But ya, if it says it installed, then it installed. Else something is broken on your computer in a fundamental level.

Post logs of the installer. It tells you explicitly where it is installing it to.

1) 1.6.4.. really what makes you think we still support that... update 2) Your launcher/java is broken. Not a Forge issue.

Its not a bug, vanilla doesn't support mods, you destroyed your world. This is why backups are a good thing.

What exactly are you trying to accomplish?

Intersting you have a mod installed that is trying to parse screwed up json. Sadly the stack trace cuts out so I cant tell you which mod, just that one of them is.

Talk to whomever wrong the thing you used to 'export to java'.

Logs, also we dont touch DNS so that would probably be a anti-virus or firewall issue.

IStateMapper

That's a MagicLauncher issue, he needs to support inherited versions, which is a feature of the vanilla launcher. It's REALLY useful for stuff like Forge.