LexManos

java.lang.OutOfMemoryError: Java heap space

Try disabling the loading screen, besides that Make sure you're on the latest 1.9.4. And post logs.

Try disabling the loading screen, besides that Make sure you're on the latest 1.9.4. And post logs.

Once the transfer is fully done and everything is stable. The plan is to re-evaluate all of the systems we use and look into better solutions. But the important part is to make sure everything is stable/cleaned up so we can get a full lay of the land.

Once the transfer is fully done and everything is stable. The plan is to re-evaluate all of the systems we use and look into better solutions. But the important part is to make sure everything is stable/cleaned up so we can get a full lay of the land.

Its typically the modder's responsibility to report bugs to us because they are the ones who know the most about it and can provide the actual code context. But whatever. https://github.com/MinecraftForge/MinecraftForge/commit/6b8466778e23226e686bcd0c83769804541eac49

Its typically the modder's responsibility to report bugs to us because they are the ones who know the most about it and can provide the actual code context. But whatever. https://github.com/MinecraftForge/MinecraftForge/commit/6b8466778e23226e686bcd0c83769804541eac49

1) As Erino said, moving from a singelon based system to a per-instance data holder would screach minecraft to a hault. Eat all the resources your system has and make the game unplayable. 2) Again as Erino said we have the ability for you to do that in forge using Capabilities that are only serialized when they are needed to be. However I'm still not sure what the hell you're talking about beyond that as you're just throwing around buzzwords. Items in vanilla will eventually be getting properties much like blocks did, we know this because Mojang said so. How they will implement it nobody knows. But as we sit we don't need to do anything about it.

The loading screen has profiling information in the logs. You can use that to determine what mods you should remove to speed things up. However, we don't support 1.7.10 anymore. Update, or you're on your own.

1) No, not going to happen 2) Items will eventually get a properties system, Mojang has stated this, when that'll happen, we don't know. Beyond that not sure what you're meaning...

1.9.4 is in beta release see the files site.

Stop using codechicken, and update to 1.8.9+ if you want support.

@ScottehBoeh I know you're trying to help, but seriously do a little bit of research before adding your advice in. If I ever ask what launcher someone is using it's because I KNOW they are using a cracked/bad one and want them to admit it before I ban them.

This has nothing to do with the files server. Wherever/however he downloaded the installer broke the bundeled json. Clear you cache and try again. And ONLY download the installer from our official site.

What launcher are you using?

1) we dont support KCauldron 2) Coremods are bad, remove them 3) Update to 1.8.9+ 1.7.10 is EOLed

Stop, just stop. This isn't hard. Your result is a itemstack with a NBT string set to the entity name So make that item stack. Then make your recipe using that stack as the result. Learn how objects work and how variables work before copy/pasting code.

Clear your cache, the json is right.

Use string names for the spawners. Also get rid of the 'new Object[]{}' stuff. And no, you should never use IDs.

Fixed. Redownload.

1.9.4 builds were temporarily broken, re-download should be fine now. Make sure you've cleared you cache before redownloading.

1.9.4 is still in beta, we're working on ironing out the kinks.

Judging by the bounding box, a half slab. This is not a bug, we cull the hidden faces of half slabs and stairs. Just like with every other block.

Update to 1.8+ This is an obvious error, on a EOLed version of so either fix it yourself of update to a version we support.

I've got forge updated, i've just ran into some unexpected issues with reguards to getting the MDK to play nice with enhanced J8 and annotation support. And I have to do J8 now because everyone has been bitching about it {it's a breaking change to the old MDK} and annotations are needed because well MC comes with annotations now. Shit happens. I'm getting close. We'll see tho.