LexManos

Seems to me like an issue with waila's HUD screwing up the GL context causing transparency to not work correctly. Nothing forge related. Speak to Waila's author.

Remove mods, provide logs, provide video to demonstrate 'flickering'

Try out this code: public static class Main { private static class Foo { public String bar = "bar"; } public static void main(String... args) { Foo foo = new Foo(); System.out.println("Foo: " + foo.bar); buzz(foo); System.out.println("Foo? " + foo.bar); } public static void buzz(Foo foo){ foo.bar = "wat?"; } } Note: your change doesnt take into account machines/that double call thing.

Except that completely screws up the logic in ContainerFurnace.transferStackInSlot. You should look into it more.

at mrtjp.core.world.BlockUpdateHandler$.onTick(blocktickhook.scala:46) Remove mrtjp mod, or ask it's author, seems a recent version of that is broken, we've gotten a few reports.

Sadly I'm not able to reproduce this in any way even included using the exact JRE you're log states. There isn't much I can do with no log, no reproduction or anything... If any developer out there is experiencing this issue and can look into it. Else you could try loading up JProfiler and attaching it to Minecraft and seeing where its stalling.

Yes, its one of the reasons why Forge has not touched this area much. We can not break protocol.

http://wiki.vg/Protocol#Entity_Effect http://wiki.vg/Protocol#Data_types

at mrtjp.core.world.BlockUpdateHandler$.onTick(blocktickhook.scala:46) Whatever mrtjp.core is is probably the one at fault or could tell you more, go talk to it's author.

I wonder what could possibly of gone wrong and what you should do....

How exactly do you expect something like that to be implemented? Lighting is 4 bits, thats all, in order to expand that to allow for native numbers we would have to break the chunk format. Not to mention propagation is a bit.. iffly. Trying to figure out where light should be 'negative' and where its just dark... This is not something that will go into Forge. It's a major breaking change in the engine.

If you did as I said, you wouldn't be 'the same as this case' So post a new log. Also, update Forge. And @Acid: Do not hijack others threads saying "I'm getting this too" because you have no idea what you're getting and have no idea what hes getting without logs. As for your 'Only installs the .json file' THAT IS INTENTIONAL,100% FULLY WORKING INSTALL. How many times to I have to repeat this?

Humm i could of sworn they printed the uuid when connecting. You need to find a way to print that out for the users. or simple test, delete the stats folder, run the game and do the process to repeat. If you have two files in the stats folder now that is the issue. Also show us how you are launching the client.

There isn't much we can tell you, this is why we tell you to give us logs, anything without them is speculative. If world/stats/{uuid}.json exists, the stats reader will read it. If your UUID changes, then there is something wrong.

What EXACT VERSION of FOrge. Post Logs. You can try disabeling the splash screen if your gfx card is deping the crap out of it like this. Tho this is the first ive heard of the splash screen causing this.

The loading screen shouldn't affect this, you just don't have room for a big enough texture on your card.

Also update forge.

The FML logs. Thats from the launcher its just saying that the game crashed. Not clue why. Im not sure how much we can help with this as there isn't much in these logs. Its just exiting.

This isn't anything FORGE can do. YOu can't really cache recipes, they have to be generated into a in-engine object {the actual recipe class and everything else} There is nothing to cache here, and even if there was, what you're saying is that Forge should replace a 'if isLoaded(mod) addRecipe' in the mod, with a complex caching system that would be 10-100x slower then that one if statement... Not gunna happen.

Buy minecraft. Advocating using cracked launchers will get you banned. just buy the damn game.

logs

read the releases post -.-

Let me guess you're running on a mac. Disable the splash screen in the properties like the release post says.

Thats the crash report not the logs. The logs are in the logs folder named fmllog.

Why not just use a NBTList with type String? As for the issue when 'sending less data' should not be an issue, things are compressed when needed.