Jump to content

plowmanplow

Discord Moderator
  • Posts

    4594
  • Joined

  • Last visited

  • Days Won

    74

Everything posted by plowmanplow

  1. Looks like a crash related to Modular Powersuits. Try removing that and see if it works. If it does, you might need to follow up with the mod's support thread.
  2. You haven't fixed your download URL. You haven't incremented your pack version even though you changed the modpack archive. You are now including too much stuff in your pack archive. It should only contain the folders: bin, config, Flan, mods. The /bin/ folder should only contain the file modpack.jar. You haven't moved the contents of /coremods/ over to /mods. You have a 1.6.4 version of CoFHCore in the /coremods/ folder. CoFHLib is for mod developers only and shouldn't be in a pack. You haven't updated AE2. Your Forestry mod is out of date. You have MFFS but none of the dependency mods which Calclavia requires. You have Numina but not Modular Powersuits, the only mod which uses it. Please address all the points I have made in both posts before continuing.
  3. There's really no practical way to go from a 1.6.4 world to a 1.7.10 world when there are a lot of mods involved.
  4. The only real way is to keep abreast of the change log so you notice when they switch to a new version. That being said, the current version is for 1.7.10. The page I linked is the build server for the developers so always current and up to date.
  5. Copy.com links need to have "?download=1" (without quotes) appended to them in order to function properly. Your pack version is 1.0. Make sure you are incrementing this when you update your modpack archive. Forge for MC 1.7.10 does not use a /coremods/ folder in any way. All mods belong in or below the /mods/ folder. You have only one of the three required mods files for Galacticraft. You need GalacticraftCore, GalacticraftPlanets, and MicdoodleCore You need to get your IC2 build from the developers: http://ic2api.player.to:8080/job/IC2_experimental/ You need to get your ChickenBones mods from the author: http://chickenbones.net/Pages/links.html Your ProjectRed is woefully out of date. REI Minimap crashes with some mods. I recommend a combination of LiteLoader and VoxelMap. You should update to AE2rv2 Fix these issues and come back if you are still having troubles.
  6. Believe it or not, allocating less memory can sometimes help. Try playing with 2G allocated in the Launcher.
  7. Your modpack download URL is broken or malformed. Check your settings.
  8. java.lang.OutOfMemoryError: GC overhead limit exceeded The client is running out of memory. In theory you could suggest that players increase the memory allocation in the Launcher to a higher value. However, your pack is so large that almost no one is going to have sufficient resources to play the pack successfully. It's just too big. I was able to start it with 3G allocated, but the parent process was consuming nearly 3.6G. Anyone with less than 8G of physical RAM won't even be able to start it.
  9. Uhh, the API URL or a link to the pack details page.
  10. That is a relevant observation, but does not alter my assessment in any way. Without the API URL or pack details link for your pack I can't provide further information.
  11. As I mentioned, you ONLY want the folders: bin, config, mods. The other folders (even Hats) will be created on the fly when the pack starts up. Nothing else should be included in your pack. Also, make sure you only include the modpack.jar file from the /bin/ folder (remove everything else from that folder).
  12. Not sure why you would be seeing that. I do not see that in my Solder interface.
  13. That error happens on a server when one of two things happens: A client-only mod has been included in the server /mods/ folder. A mod which should work in SMP is poorly coded and does not properly proxy its client only code. In the case of #1, it is a simple matter of figuring out which mod is client only. For #2, you'll need to track down which mod is not coded properly. This can be tricky.
  14. If you provide a link to your pack details page or the API URL, I can figure out which mod(s) is causing the problem.
  15. That error is happening because you either have a client only mod on your server, or one of the mods which should work in SMP is poorly coded and is not properly proxying its client code. I'm away from my PC at the moment so I can't test them, but I would suspect something like the colored chat mod or a similar mod.
  16. Your modpack archive is in RAR format. All archive files intended for use in the platform must be in ZIP format. The contents of your modpack archive are in a subfolder named "mcinfinitycraftingluc". The required folders (bin, config, mods) must be at the top level of the folder structure inside the modpack archive. You have included WAY too much stuff in your modpack archive. It should only contain /bin/, /config/, and /mods/. The /bin/ folder should only contain modpack.jar. Your archive is over 550 meg in size which is crazy huge. Fix these issues and come back if you still have troubles.
  17. The "correct" way to install LiteLoader in 1.7.10 is to simply place the liteloader-1.7.10.jar into the /mods/1.7.10/ folder (the mod JAR, not the installer). For Solder, you would just create that folder structure just like any other mod.
  18. What I'm trying to say is that once the IDs are "fixed" correctly, there shouldn't be ANY ID fixing mods in the /mods/ folder which makes the idfix.txt file of no concern. You either deconflict the client OR the server, then copy over all the configs to whichever you didn't fix (if you fixed the client, copy the configs to the server, ec.). If you have an ID fixing mod in your client pack, or on your server you are doing it wrong.
  19. No. Once you have resolved all of the ID conflicts (on either the client or the server) there should no longer be any ID "fixing" mods in the /mods/ folder and the idfix.txt file should no longer be needed.
  20. java.lang.NoClassDefFoundError: reifnsk/minimap/ReiMinimap REI Minimap is a client-only mod and should not be on your server.
  21. The correct way to do this is to resolve all conflicts on either the server OR the client, verify that all conflicts are still resolved after removing all IDFix-ing tools, then copy those deconflicted config files over to the other (either server or client, depending on which you resolved). If you resolve the conflicts independently of each other there will be mismatches (as you have seen).
  22. Please pastebin a full crash report.
  23. Your modpack archive is in RAR format. All archive files intended for use in the platform must be in ZIP format only. Many of your mods are out of date with known crash bugs and stability issues.
  24. That is a good place to start. At least I can find the pack that way. However, it is much easier for the support folks if you provide the API URL. This is the URL that can be copied to the clipboard by clicking the "Install This Modpack" button on your pack details page. Pack Details Page: http://www.technicpack.net/modpack/darth-gaming.591943 API URL: http://api.technicpack.net/modpack/darth-gaming
  25. Shall I guess at the name? Shall I divine the search parameters to use to find your pack? Wouldn't it make it a lot easier on the folks from whom you are requesting assistance to provide those things for which they have asked?
×
×
  • Create New...