LexManos

[17:52:32] [server thread/ERROR] [FML/]: There was a critical exception handling a packet on channel FML java.lang.NullPointerException at net.minecraft.server.management.ServerConfigurationManager.a(ServerConfigurationManager.java:109) ~[ld.class:?] Someone will have to look at what could be nulling on that line. Also why the function is named a.... Anyways.. you'll have to wait till im back from con, unless some brave soul out there wants to help while im occupied.

Use build 1056 -.-

.... interesting it should show more detailed information in the log file, any chance you can post that.

Wow... thats fucked up. Haven't seen that before, I'd say try updating your vid drivers. It's potentially possible that ichuns' changes in 1057 caused this {cuz rendering is weird} try 1056.

1056

Use 1056

use 1056

echo %JAVA_HOME% What does that say? Something is setting your JDK to not java 7. Could alweays just update to latest forge {well 1056 as 1057 is bugged for some people}

2014-04-09 21:25:51 [iNFO] [sTDOUT] Memory: 451712 bytes (0 MB) / 259522560 bytes (247 MB) up to 259522560 bytes (247 MB) You ran out of memory, 247MB wont cut it for modded minecraft. Try a gig.

We need actual screenshots/logs. Describing it doesnt seem to be working.

Seems to be an issue with ThutConcrete registering its items incorrectly, it should not be registering the same name multiple times.

Try using 1056 and see if that works.

Use 1056 for the first one. And for the second, ignore it if you have nothing in net.minecraft.

Seems unfriendly, but to each there own, then what does it matter what your repo is setup like if you don't care/expect others to see it?

You openly admit to trying to run a 1.6.4 mod on 1.7.2... What makes you think this is a good idea or that it'd work?

... http://wiki.vg/Protocol

I'd say move the licenses and stuff into /src/main/resouces so that it is picked up by the builder, or potentially link it in using the build.gradle. And I would also say keep the gradlew file for those who use your repo who arnt using your OS.

We need to have your full log that is in your log folder.

One or more of your mods is a client side only mods. None popout at me so you're gunna have to track it down yourself.

There was a security issue disclosed today that affects Mojang and Amazon. They *should* update and resolve ti soon. So try relaunching your launcher and it may grab a new version or wait for Mojang's response. As such this isn't a Forge issue.

We do not support the old python scripts.

Well no shit you cant run mc with mssing dependancies. Moajng's/Amazon's servers are having a bad day today. Try re-running your setup with --refresh-dependancies untill it works.

This is not something to do with Forge. The launcher and amazon are the only parties here. This may be caused by today's Heartbleed vulnerability that was found and Amazon's response to it. I would advise moving to talking to Mojang about this.

why are you running the universal? Use the installer...

The original fix is gunna need to be reverted as it's killing some peoples games on certian hardware. Will need to look more into this.