LexManos

Post your install log and your vanilla launcher logs then.

Your code is to complex maybe you may find the issue if you write it simpler, this is your code: world.setBlockState(pos.down(), world.getBlockState(pos.down()).withProperty(BlockDoor.OPEN, world.getBlockState(pos.down()).getValue(BlockDoor.OPEN))); Simplified: BlockPos down = pos.down(); IBlockState state = world.getBlockState(down); boolean open = state.getValue(BlockDoor.OPEN); state = state.withProperty(BlockDoor.OPEN, open); world.setBlockState(down, state); Now read that carefully, and No I did not make any typos when translating your code.

We no longer put a jar in the versions folder as it is unnessary. Use the vanilla launcher and it will work.

Use the official minecraft launcher.

There is no need for Better Fonts anymore with proper configuration files you can do everything that that achieved in MC 1.8 nativly. On top of that Diesieben is correct, you should not be editing vanilla classes if you have no idea what you are doing.

That is not spawn, the place where you are with the tree is actually like 250 chunks away from spawn, hence why it doesn't get loaded. Spawn is at -1784, 373, so fly over there real quick, or die without a bed so the chunks reload. I JUST tested this exact map with Forge, it works fine you just need to make sure the chunks load.

1) 1.6.4 is years old, stop using it we do not support it 2) Follow the rules when asking for support and post logs we're not telepathic.

Stack from those looks look like you're having issues with immibis multiblock and chickenbones mods potentially with your graphics drivers. Remove those and see what happens.

Protip: That mod is bad and there is no reason it should be doing ASM hacks.

It does not, tested the map it works fine. You may need to load the spawn chunks and get the redstone going, but this is a issue in MC itself not Forge.

Mixing and matching like that isnt advised because other languages have different syntaxes so its not always {Material} {Form}

The in-game config system never worked, I fixed it to do a few months back in 1.8+ Some coremods have gone through and futtzed with that screen but nothing in Forge. And we do not backport changes. So, right now you can't edit things in-game. Use the main menu option or you know, UPDATE FORGE.

We will not throw errors because everyone and their dog has their own idea of what the standards should be and trying to impose anything on modders is like herding 3 year olds. As it sits FG and Forge SUGGEST that modder follow a standard and FG prods it in that direction using some of the mechanics it has in place. But there isn't anything we can do to Force it.

The alias system is the method for 'taking over' someone elses registry entry. Hacky solutions are not advised and are most likely the reason you're getting things that are broken. According to cpw as long as you register everything correctly and register your alias any @ObjectHolders, ItemStacks, etc.. will be updated to use your object over the one you're overriding.

Mulitcraft should really make things easier on their users. Anyways download our installer. Install the server to some random new folder. Upload EVERYTHING in that folder most notably the forge jar, minecraft jar, and libraries folder EXACTLY HOW THEY ARE MADE. Do not rename anything, do not change capitalization, nothing. Then execute the forge jar in the folder you uploaded it to. Making sure the working directory is set to that folder.

Yes will take a while its zipping up the world folder. You can do it yourself by zipping the folder and deleting level.dat.bak

The "Bug" is not in Forge, it is in Mac graphics drivers. They are the ones who are not following GL standards and misusing texture objects/memory. Nothing we can do about this but disable our feature that get effected by this. So once again, Macs are crap.

Macs are crap, stop using them. Until you do that disable the loading screen as described in the EAQs.

Remove NEI

You would have to talk to chickenbones, on his main thread on the minecraft forums. We don't write NEI/CCC here. And it is a error in that code.

Run a gradlew cleanCache and try again, wrong forum.

This is not a Forge issue. One or more of your mods is having bad interactions with how you're using them/setup. Ironchests being one you mentioned I get 620FPS using Forge and IronChests on 1.8. We cant debug your setup, start dismantling your machines and move on.

Be a bit more descriptive. We use the normal GUI that java allows us perhaps a video or gif showing what you're trying and what issue you're having would help. We need more information.

Lower your render distance.

You login using the mojang launcher with Forge installed using our normal installer. Realms works fine. If you dont see realms then your session is invalid, or you're using a incorrect launcher which is not respecting the work that mojang and us put in to allow us to decouple ourselves from the realms library so that mojang can update it independently. So ya... LOGS!