LexManos

http://www.youtube.com/results?search_query=how+to+run+a+jar+file&oq=how+to+run+a+jar+file Running a jar is really, really simple.

Ya, use our installer. Our installer will add the libraries to the correct path.

Not exactly sure how 'put this file into the mods folder' is complicated..... But ya, MagicLauncher typically is more hype/broken then the benefit it provides. It needs a lot of work, and it's sad to see it not getting the work, considering it's needed it for so long.

... that makes no fucking sense what so ever.... If anyone else is getitng this issue, zip up your entire .miencraft folder and send it to me, I wanna see if I can reproduce. Because this should not be possible in Forge, and that solution should not be any effect at all...

This is intentional, it's designed to break mod packs which should be shipping these libraries. Considering it was killing our server it's a necessary evil. So your choice are 1) Stop using 1.5.2 seriously dude, theres no reason to not update and if you say 'oh my mods arnt updated' go bitch at the mod authors to stop being lazy 2) Manually install the libraries from the link provided in the EAQ. or 3) If using a mod pack, go complain to the mod pack authors to do there job correctly.

They have the means, in the respiration enchantment. What they are wanting to do is set a number outside the range that rendering allows and thus cause GL error spam. I've yet to see how that's a good idea.

Something in your setup is setting your players skin to null. This can never happen in basic forge. So what I would say is backup, then wipe out your .minecraft folder and start from scratch. You installed *something* that is screwing up your entitie's skin.

Not sure why people have so much issue with running a jar file it's pretty basic. Basically you need to run java -jar {forge installer jar}

Nothing on our end, seems like a issue with your mod pack. Go talk to the pack provider.

No. You don't. Mod installation is simply 'put in mods folder' If you can't figure that out you shouldn't be playing.

Don't use magic launcher.

Logs, always need logs. We dont do anything to the login, typically this issue is a screwup on the mod packer's end, screwing up the json.

Use the installer.

Reinstall java.

Im going to assume that you mean the PATH for java, it's not REQUIRED. You only need to do it if you screwed up your path somehow. When you install java, it configures your path correctly for you automatically.

There is always an issue to move from modded to vanilla, Depending on what you have, or what you've used it could screw things up. Your best bet if you're moving from modded to vanilla is to go through and manually delete all moded items from the map. Sadly you can't do it cleanly in vanilla because vanilla has almost no NPE protection which is what happens when there are 'missing' items.

Not quite sure what order I should view those in, nore what the scale is. However, you'd have to look into the memory snapshot and see whats eating things.

Seems there is a lot of that spam. But sadly, it's not really simple to debug memory leaks, or 'lag'. However, it also does seem like there's a lot of glacticcraft dimensions. If you know how, run jprofiler and get some memory snapshots to see whats eating up what. You have a crapton of mods {looks like 112 jesus} so anything in there could cause lag/issues.

Zip your enitre .minecraft folder and e-mail it to [email protected] I want to take a look, because the error you're getting should not be possible on Forge.

I'd start by removing any coremods you have in your mods folder. And things like optifine, or the like.

Interesting, can you give us the md5 of this file: /Users/edulzo/Library/Application Support/minecraft/libraries/net/minecraftforge/minecraftforge/9.11.0.883/minecraftforge-9.11.0.883.jar It should contain all of the classes, and it *looks* like it's in your classpath. When you run it normally using the mojang launcher, what happens?

1) don't bump 2 month old threads 2) Forge fixes the glint feature, so that it only applies to the 2nd render pass, but, it still works fine:

Seems like an issue with pixelmon calling a method that doesn't exist. Namely it doesnt return Item. Which typically means pixelmon isn't updated to the current MC version.

You have something else in your jar. if (block != null) { block.onBlockHarvested(this.theWorld, par1, par2, par3, l, this.thisPlayerMP); } That is line 270 - 273, as you can see there is literally nothing that can be null there as the only thing that can cause a NPE is block and that has a null check. So whatever else you have in your jar, or that overwrites that class. Remove it.

Mod pack is missing required libraries, they need to fix that.