LexManos

We do not control any of CB's Mods.

installer ran fine now for the launcher logs

no its not, there are alot more to he logs then that, they are in your logs folder -.-

Post Your Log Files

L To O to the G to the S LOGS!

It does run with a jar file, its just not in that folder. The Forge jar has always been installed into the libraries folder not the versions folder. Don't use Magic Launcher. And follow normal procedures for installing Forge on the normal launcher. Supply logs of exactly what you're trying to do. If you use the mojang launcher, our installer will work just fine.

Disable the loading screen as detailed in the eaq

Your jar is corrupt somehow. I would advise trying with the normal launcher and not the curse one to see if they have derped something.

Your latest log is from 1503 update

Answer the question, and Forge/MC doesnt give a shit about the launcher you're using as long as it does it's job correctly. If in doubt use the latest launcher.

Forge would not effect your chsome so if you cant use it you've got something else fucked up not us. And try 1504+ The FML logs, are in your logs folder, and they have fml in the name -.-

Post a log of a run with zero mods.

Yup that error is listed in the EAQs, you should really read them. Update to at least 1.7.10.

logs -.-

There is nothing I can do on my end to make modders stop being lazy. Its impossible to "Make it stupidly easy to port" because that's not how programming works, you can't just magically make things 'easy'.

Clean your internet cache and re-download 1504+ Also post the FML log not the crash log.,

Try the latest build. 1504

No they can't. The Forge blockstate format is simply a system that builds all the cartesian products for the given entries for you instead of you having to specify them all. The json is not a scripting system, if you need it to be then you're doing something wrong.

A single tick should not take over a minute to do. It should happen 20 times a second. 'Hiding' this error/lag is not a option. But thanks for letting me know that for some reson the watchdog isnt killing your server like it should. I'll look into why that is.

Start removing mods, the log doesnt tell us which one it is, but it looks like you've got a coremod in there derping things up.

Ya, we just switched to a revamped version of our build system, it works locally but it seems to need more testing, Blame AbrarSyed, i'm working on it and should be fixed for new builds today.

Neither of those logs contain a crash. THe FML one just ends which is odd. You can try disabling the loading screen if your gfx card is the issue.

http://mcforge.readthedocs.org/en/latest/blockstates/forgeBlockstates/

Abrar broke shit, its fixed now -.- This should not of effected end modders I will be yelling at him a lot next time hes on.

Abrar broke shit, its fixed now.