LexManos

Simple, the session whoever is trying to connect with is invalid, they need to dump out of MC completely and re-run the launcher/login. Or, the host can not connect to the mojang auth servers. In which case an error would show up in the logs.

You dont have internet, or your firewall/something is preventing java from being able to download gradle, kill your antivirus and see if that helps.

Do as it tells you...

You installed a bad version of chicken chunks.

http://bfy.tw/s3g Also don't bump your threads, the edit button exists for a reason.

To expand on that, you should not be editing the jar, Ever. If you want to use optifine with forge, just stick it in the mods folder. That is it NO EDIT JAR FILE EVER! If Optifine is compatible with the version of Forge installed then it will simply load and you're done.

Yup, i will say this over and over again {its my personal opinion as a developer, consumer, and IT professional} Macs. Are. Crap. If you're doing anything fancy, anything beyond what Apple has put forth then you're screwed. They are the consoles of the PC world. But anyways, again personal opinion not a debate starter. Your issue is resolved, there isn't anything we can do about giving you the loading screen on your mac. Their drivers are simply not compatible. If you have any other issues, feel free to post. But please search before hand next time.

Re-run the forge installer. You seem to of deleted the forge jar, this is kinda important.

None of that needs to be a fucking coremod. Use the values that you can set in the blocks... Seriously CORE MODDING IS A LAST RESORT DO NOT DO IT FOR SHIT YOU CAN DO IN VANILLA.

Try clearing your internet cache. Also go to files.minecraftforge.net/mirror-brand.list and tell me what that shows you. Should work fine. We removed one of the mirriors because they were 404ing.

Thats the point, you're disabling the new fancy loading screen because your computer is crap.

You have access to every version of minecraft through the vanilla launcher, so there is no worries about being 'to updated' they all live together fine is you do it right. When you install forge it specifically targets a single version and does all that for you. Forge is currently on 1.8.0, Minecraft is on 1.8.7, the installer/launcher know to use the correct information. {Before anyone asks, yes i'll be updating, when i get free time, monday is the plan}

adventurebackpack-1.7.10-0.8b Mods do not work across MC versions. So that one will obviously not work. Morph-Beta-0.9.1 Gives no MC version info so you'd have to consult the mod's official thread/page. There is also a logs file in the logs folder that tells you more information.

User was banned for using a cracked launcher and being retarded enough to ask for support on it.

Use the forge installer.

If you dont care then use the pre or post events. The specific ones are if you wanna modify cancel or do additinal stuff with the rendering of specific things.

As far as I know, we do not touch anything that would cause this. We dont touch how minecraft creates the intial display or what monitor it locks to. You may need to see your graphics settings to see if you can specify an affinity for the fullscreen to use. But i'll poke fry about this, he's our rendering guy. Sadly tho, hes out of country {as am I} so don't know how fast he'll be able to get back to you.

Why? What?

Yes i can tell what function is recurring. Cuz you know, stack trace. However, it shouldn't be that big of a deal. How does it expand to 1728 function calls, that seems ridiculous. Will need to look into it when I get back home. But yes patch files are far better then hunks of code with comments. Much easier to actually see the difference.

Wall of code really doesn't help cases like this, patch files are much more useful. Quick glance at it shows that it should be sane enough for any normal usage. How exactly are you getting a stack overflow? I'll be able to take a more detailed look at it when im back in town, but it shouldn't recurse that much unless you're feeding it extreamly bad information.

Ah, even I missed that it was old cuz the same guy bumped it twice. Anyways, this is unneeded.

Why does everyone this this is an error? You could tell it isn't a error if you TRIED RUNNING the damn thing..

Post you full logs there is debug text that I want to see. There shouldn't be any reason this is giving you an issue.

Both should sufficiently be covered by the block events, and beyond that, there really isn't a good place to hook into this and pushing things like this out into the main event bus would just be horribly inefficient. I don't see a real reason for you to need this exact event...