Jump to content

Recommended Posts

Posted

when i try and launch my custom modpack, it finishes initializing and moves on to postinitializing. however, as soon as it reaches this point, it just stops with a java.lang.outofmemoryerror. no crash, just Mojang screen forever.

here's the pastebin of the console: http://pastebin.com/Xk4nE6Q7

i only posted about half the launch process and the error, i don't think the rest matters. The error is at the bottom.

Thanks in advance!

Posted

i have java 64-bit online. i had java trouble a while ago, but when i installed that, everything worked again. I hate to remove advanced genetics, are you sure there's no other option?

  • Discord Moderator
Posted
  • Forge for MC >= 1.6 does not use a /coremods/ folder in any way. All mods belong in or below the /mods/ folder.
  • Your pack archive has a /test/ folder with 200M of unneeded files. Remove this folder.
  • IDFixMinus should not be included in your modpack. It is intended to be used to assist in resolving ID conflicts, then removed.
  • You need to be including Lexmanos' Legacy Java Fixer: http://www.technicpack.net/article/attention-modpack-authors.105

I am able to launch your pack with 2G allocated and using Java 8.

  • Discord Moderator
Posted

are idfix and the coremods folder actually a problem?

 

I'm not claiming to know all the right ways (far from it), but in this case it is improper to include anything in the /coremods/ folder as it does absolutely nothing and just bloats the pack size needlessly. If you place mods in there which are required for other mods to function, the pack won't work. As for IDFixMinus, it is intended to help you resolve conflicts, then to be removed. It should not be in a published pack, and should never ever be used in a pack which is destined to be used on an SMP server.

  • Discord Moderator
Posted

IDFixMinus is a tool. It is intended to help you resolve ID conflicts. If you remove it (after it does its magic) and still have conflicts, you'll need to fix them the old fashioned way:

Posted

ok, so i resolved the id conflicts, but when i luanch it, i get the same MaxPermGen message, with other errors besides. I've included the legacy fixer, removed the coremods and the test folder, and fixed the ids: i would be interested to know how you managed to get it to launch. it always just freezes on the mojang screen. with the console telling me that it is unloading everything because of this: http://pastebin.com/dh2WMD1Q

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...