LexManos

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.

Working with bspkrs right now to get his end done. Forge's end there are ~100 failed hunks. I'll be pushing at least a beta tonight.

Json and lang files are data. Not code. You can not reference code in them. Simple as that. If you MUST have a weird setup like this then write a script to generate the lang and json files.

1.9.4 support will be done Soon I've finished the bulk of the updates for the pre-forge stuff. Just waiting on someone else to finish their work so I can start on Forge.

One of your mods is sending an invalid packet, there is no way to know which so you'll have to start removing them. Also, you REALLY should update to 1.8 if you want support 1.7.10 is old as hell..

Mystcraft issue, also update to 1.8+

CAN you require J8 in your mod? Yes. SHOULD you? No, Minecraft targets J6, so should you. Simple as that.

That is called layers, you can use normal textures layered on top of each other just fine. No need for custom generated code. It would work JUST FINE with resource packs. As for the physics shit, you can do the substitution system we have in the registry to take control. And leave it as is. Generating context, be it blocks, items, textures, whatever is bad because it 1) breaks the data driven design that we at forge, and mojang are trying to do 2) It breaks a lot of functionality when it comes to external modification for resource pack makers, server owners, etc.. 3) It makes life hell when trying to manage data and keep worlds/servers clean and synced up 4) It opens up a PLETHORA of potential security issues depending on the routes which you go. 5) It screws with the caching and performance of the re-written rendering pipeline causing major downgrades to end user's experiences. There are A LOT of issues with doing dynamic content like that. If you run into issues, then you can get them addressed. 1) Fixed with multilayer models 2) Fixed with some re-working of the entities nothing hard just needs to be brought it properly. 3) Should never need to be done.

That is you running the game -.- not the installer -.- Just watch the video in my signature and run the installer jar manually. Use the command: java -XMx2G {InstallerFileName}.jar If that doesnt work give the logs of the screen and if you get a 'file not found' error then you didnt use the correct installer name or are in the wrong directory rewatch the video -.-

That is not your log -.- the log is a file created in the same directly as the installer that will tell us WHY you couldn't install those files -.- 9/10 times its because your computer gave the installer to little ram. Which we have explained how to fix a plethora of times on these forums if you would search or read the eaqs.

Prepackage the data, and in all honesty what you've described doesnt need to do anything special or replace blocks, just listen for block change events and create falling entities. 'Dynamic' mods/block are a BAD IDEA. Do not do them.