LexManos

The mod 'roflpunk' is broken, contact it's author.

Quit using the older installer, I'be re-uploaded all the installers and they will now verify the libraries when they download. As long as you arnt using a older version then you should be fine. Manual installs work as well, but the installer works fine.

Just run the installer, t'll install another 'version' that you cal select in the profile editor. It will also set the 'Forge' profile to whatever version you just installed. It's rather simple. It just adds shit that you can choose from.

pixelmon needs to update for 1.6.4.

mod_NoteBlockDisplay Is not updated, remove it.

The minecraft vanilla server jar MUST be called 'minecraft_server.1.6.4.jar' and MUST be in the same folder as Forge

Do not REPLACE, you want to MERGE.

You only have to manually install if for some reason your computer can't download them from our servers. We've done everything on our end we can do to set it up for users to download, its down to users having good internet, and the server not crushing under the load. And no there are no OS specific version of these libraries so you don't have to worry about that.

Interesting well take a look at it, however it's crashing outside of our control. We did update the launch wrapper between 1.6.2 and 1.6.4, Optifine may need to update because of that.

Thats because you haven't registered your structures! Seriously, i'm not talking out of my ass, try it.

Your 'monsterhunter' mod adds world gen structures, but does not register them with the new MapGenStructureIO class. Its REQUIRED for anything that makes structures.

Try running it from the command line, it should print out a error. Also the md5 you want for that file is : 0d9fb49dda3c19c960b81f271c80557a

I was actually being genuinely helpful,. but your rant gave me the urge to ban you so, enjoy your ban and enjoy playing minecraft. Try not to be a cunt next time you work with people who are helping you.

If you ahve a packaging issue, ALWAYS ALWAYS ALWAYS post the package. Seriously it 1000x easier to check the issue directly then it is to speculate over the internet.

No, but you do have access to FML's deobfusication data.

Yes it's the mod, here is a helpful tip when reading the log files: java.lang.NoClassDefFoundError: nm at mod_ReiMinimap.getVersion(mod_ReiMinimap.java:15) The first line is the error, you'll learn a lot of the common errors if you just start reading. The line immediatly under it, *typically* tells you what mod is responsible. In this case it's pretty obvious: 'mod_ReiMinimap' There can be things like 'net.minecraftforge' or 'com.forestry' or things like that... If you actually READ your errors, it because rather easy to do basic trouble shooting yourself.

What custom launcher are you using? But ya it looks to me like a launcher issue not forge. As you can see int he log we clearly startup in 15 seconds.

... you expect rei's mods to work for 1.6.4 already?

Your log clearly shows a startup time of 15 seconds, which is normal. If you're referring to the file the mojang launcher takes. That's there end, they single thread the loadup and download of the news. Sometimes causing several minutes of wait time.

Update, 1.5.2 is nolonger supported.

I honestly have no idea what you're saying, nore what magic launcher has to do with anything here... However, if you run using the command line it should print an error. This message pops up when you have a corrupt download of the installer. So... clear your internet cache and try again.

Small derp up in cpw's changing of the required launchwrapper version. It's still looking for 1.3 in the manifest. cpw is fixing it now, so go use build 883

Interesting, do you get a constant SHA1 for the ones the installer spits out? Also it shouldn't be overwriting your manual downloads if the checksums are correct. Can you garentee that those files are the correct checksum BEFORE running the installer process? The only thing that seems to come to mind as a possible cause for the issue, is that you're running Java 8. Java 6 and Java 7 both produce the same output from unpack200ing something, but java8 may of screwed that up. Any chance Ic an get you to test running the installer on a 1.7 JVM? Though this still doesn't explain why the manual downloads are getting overwritten.. unless java 8 screwed up the entire sha1 system..

My bad, those are sha1 checksums {seriously... who does sh1 *shakes fist at cpw*} Anyways just ran through and gathered the checksums myself, here you go see how yours compares: C:\Users\Lex\Downloads\test>md5sum * 44f4d11085423ebffbfb177c1fe4cc69 *scala-compiler-2.10.2.jar e3ab8b490a4a25aa78d6be631159a6b7 *scala-compiler-2.10.2.jar.pack.lzma 000f71f6c70baf780ad6819d8b89c960 *scala-compiler-2.10.2.jar.unpacked 8800aafcc03e346dbbde171bef0b2bfe *scala-library-2.10.2.jar ff917f6e29ae246b1a1d305d26619dc1 *scala-library-2.10.2.jar.pack.lzma 38ceadbc4da687ca5d1146166f679d30 *scala-library-2.10.2.jar.unpacked C:\Users\Lex\Downloads\test>sha1sum * 64c8b1380cc53d6850823d6e4e7ae984aa44ef9c *scala-compiler-2.10.2.jar 79dc9406dd44b136429f8b2f26cc94b47f63bb42 *scala-compiler-2.10.2.jar.pack.lzma 40281b3ffc69fb385953522c843363ccaf71ba89 *scala-compiler-2.10.2.jar.unpacked 6ba65d12cd09d441083262d6f73d2257fec7c663 *scala-library-2.10.2.jar 3b52a48d5497035c14b3bf813ba06bf73200d04d *scala-library-2.10.2.jar.pack.lzma dffc88e804861c9eaba39283757000b6558ea573 *scala-library-2.10.2.jar.unpacked C:\Users\Lex\Downloads\test>ls -l -r total 44956 -rw-rw-rw- 1 Lex 0 6584157 2013-09-17 20:42 scala-library-2.10.2.jar.unpacked -rw-rw-rw- 1 Lex 0 1676323 2013-09-15 18:44 scala-library-2.10.2.jar.pack.lzma -rw-rw-rw- 1 Lex 0 7121818 2013-07-09 14:52 scala-library-2.10.2.jar -rw-rw-rw- 1 Lex 0 13195641 2013-09-17 20:42 scala-compiler-2.10.2.jar.unpacked -rw-rw-rw- 1 Lex 0 3033499 2013-09-15 19:24 scala-compiler-2.10.2.jar.pack.lzma -rw-rw-rw- 1 Lex 0 14411577 2013-09-20 20:26 scala-compiler-2.10.2.jar .pack.lzma being the compressed version the installer downloads {dont really care about that} .unpacked being the unpacked .pack.lzma, which if you use the installer, *should* be what ends up in the libraries folder. the .jar ones are the raw, unpacked, jar that i linked to earlier. It seems that you're failing to download the files all the way, clear your internet cache and see if that helps.

Set the Launcher Visibility, to 'Keep launcher open' and then post a console log, and the log files in your .minecraft folder.