LexManos

Simple, you ran out of memory, either give your game more, use smaller texture, or less mods.

Thats a incomplete log, you can tell by the fact that it stops in the middle of a timestamp. We need the full log.

Update to 1.7.10, if you refuse then you're on your own. Also READ THE DAMN EAQS.

Problem is, modders control There custom implementations of GuiScreen.handkeKeyInput not us.

Having no intention to ever touch ISBRHs again, because I suck at rendering, and personally not considering this a major issue your only be is to make a PR once 1.8 is done and convince me its a bug worth pulling. If you do need these to be rendered, you can do it yourself as the default rendering is just a sample for use.

Delete the player profile cache json. somehow you got corrupt. I'll make a note to kill the file if it errors.

It's a optifine issue, Vanilla leaks GL states, we fix that leak, Optifine breaks things beyond that. We do not support jar mods like optifine, Not our issue.

Always try the latest build. If you're not on the latest build, your report is invalid.

update and try again, if you still have issues post the world and log like i requested.

If they are hacking support for multiple versions of the minecraft client into there servers then yes, I am calling them stupid. This is something I will never support if they feel like doing it then it is on there end to support it. If you claim people "can't" run 1.8 then give me a valid reason they can't. Nothing in 1.8 save for EXTREMELY old graphics cards, i'm talking 15-20 year old cards, would cause them to not be able to use it. Our 1.8 protocol is rather simple to do this error that you're encountering is simple to address on there end as well. There is nothing I can do on my end that doesn't end with me getting bitched at by Spigot/BungeeCord people to change things so its done. Either way this is not my problem, so locking the thread.

Ah THe BONUS chest thats an important information. This is not enabled by default you have to actually enable it in your world settings. Enabeling it works just fine:

Well, sucks to be you. If you're joining a 1.7 server, then you can use 1.7 Forge which works just fine. If a server admin is trying to get both 1.7 and 1.,8 clients then they are being rather stupid as the protocol changed and with the introduction of new items it's bound to crash people. And thus we wont support it. It was requested of us by the BungeeCord people that we make FML easier to deal with. We have, its now up to them to update.

We need the actual log file, not the console log. Also what program are you using to start the game?

Its fixed, had to special case Banners in the ID registry, because Mojang was stupid and made them take up 3 ids when they could of taken up 1one. But whatever, fixed now.

Seeds for your world and location of where the chest should be.

LexManos, Give me the location in world of the chest and when I get a chance I'll hop on a take a look.

Tho I perfer people manually using the installer {well, manually downloading it} https://github.com/MinecraftForge/Installer It's open source, you can see what all it is doing.

Please be more descriptive in your bug reports, I can activate sticky and normal pistons just fine.

Metadata is still only 4 bits. States can hold more information then that, but metadata can only be 16. If you want to store more use a tile entity. It's one of those cases where Mojang.

Thread locked, we do not support 1.6.4.

I use the same project for everything Forge related.

Fixed in 1248

You log says you are playing on a integrated single player server. You're getting this on realms? What its telling me is the server is telling you to render a item that does not exist... If this IS on a Realms server I may need to hop on there and see if I can debug it. Or if you're able to download the world and send that over that'd be useful. I'm also seeing that you're using zyinhud, you should try without it and see if that helps.

That stack trace should not be possible unless you are running something else besides Forge. There are also some things in the log that concern me such as: That Avaliable chain should not happen as out state events dont fire beyond the first. Not to mention the '--CENSORED--' entries. How are you running the game, I need a clean log. And if it's a world issue, I need the world.

Fixed in 1247