LexManos

Something in your environment is registering a keybinding that's null. Check the load order of your calls.

I'm not a fan of utility functions that save the modder ~10 lines of code by sacrificing understanding of what they are doing. However, there are some vanilla utility functions that exist for these types of things, so either use those or make your own, it's not hard.

Should a modder be using @SideOnly ever? NO Why is your code running twice: It's either two instances, or the client and server are ticking it. Depends on what 'code' you're talking about.

Run a clean and try again, but it seems it cant find pixelmoncore. import assets.pixelmoncore.models.ModelPot; As a note.. why is your folder called assets.pixelmoncore? You put assets in assets not code.

Protip: read the log it tells you how to get more information. But looks like something in your install got corrupt running a cleanCache to rebuild everything would probably solve it.

It should give blocks the same IDs as vanilla, unless you're loading a broken world, then it tries to fix it. Zip your MC folder and send it to me, I want to see what you've done to break it so hard.

The network code is open source in FML feel free to take a look and see what you need to emulate it.

give us the full log and we may be able to tell you.

Your HatStand config is corrupt, delete it and let it regen.

Those are the two proper solutions, when done correctly either would work fine. {Sahding is prefered tho} If that doesn't satisfy you then you can make another system like you have, but the instant you post it for public consumption, it opens you up to us telling you its stupid, because it is.

Thread locked for being to stupid to search.

https://github.com/MinecraftForge/FML/blob/master/patches/minecraft/net/minecraft/server/management/ServerConfigurationManager.java.patch#L17 Would possibly explain why it is named a As for the error it's caused by the player trying to login to a dimension that the server doesn't know about you will have to edit the player's .dat and set there dimension to 0 {overworld}

Get us a log from 1.7.2 and just Forge then. As a log from a old mc version, and MCPC is useless for debugging.

I dont see that NPE in your logs anywhere, and the IOE is rather vague. Can you point out the NPE itself. The IO seems like it's just a connection timeout.

Or, you know, you could use the dependancy management system and fatjar system included with gradle which is 1/2 the point of moving to gradle. Why make ti more complicated and non-standard then you have to?

We would need the full logs {if cpw bothered to put that debug info in} However, if a client side only mod, does not tell us that it is a client side only mod, how do you expect FML to know it is a client side only mod? It's all down to making sure that the mods give FML the full correct information for it to be able to do its job correctly.

Either some entity you are rendering is killing your graphics card. or more likely your graphics card drivers have a issue, you may want to make sure you're on the latest version. Or, if you've recently updated, try downgrading as the drivers may have a issue.

No, there is no config option for this. It has the potential to derp up a lot of Mod's items. You can however fix this in your texture pack, by adding the extra parts you want to have the effect on to the second pass texture.

As you have failed to provide any log files as stated in the eaqs, on the top of every page, and at squituri's request. This thread is now being locked for failure to follow the rules. If we dont get a log, we CAN NOT help you.

I do, and that's because we actually fix a bug in vanilla that causes it to overlap onto the layers it shouldn't. This has nothing to do with 1024 or anything as we've done this since potions were added.

Try temporarily disabling any firewalls/anti-viruses you have, Avast likes to cause this.

See your github issue. https://github.com/MinecraftForge/MinecraftForge/issues/1079

We no longer support 1.5.2.

No thats vanilla, Forge is on the right, hence why I showed the debug info stating as such -.-

There was a bug in our networking system that didnt properly register version checks. This has been corrected, sadly this means that a few mods need to double check there configurations to make sure they are in line with the spec. {Note, this is the same spec that as in place in 1.6, just was bugged int he re-write}