plowmanplow

You'll have better results using 1.7.10-1.1307.06.218 or 1.7.10-1.1381.06.221

I'm not sure why you would be having issues. I've been running my "B-Team update" A-Team's Revenge for a very long time now with no issues at all. I'm currently at over 11 days of uptime on the server and everything is 20 TPS with no errors. A-Team's Revenge There's a server pack download in there as well. You might get more traction targeting a newer version of Forge as many of the mods have moved on quite far from #1291. I'm running #1381 with no issues (including the mods you are having trouble with and many others).

I'm not familiar with that Cauldron build. Your server's fml-server-latest.log should have a line which looks similar to: [11:08:39] [Server thread/INFO] [Minecraft/]: This server is running Cauldron-MCPC-Plus version git-Cauldron-MCPC-Plus-1.7.10-1.1381.06.221 (MC: 1.7.10) (Implementing API version 1.7.10-R0.1-SNAPSHOT) What does your line look like?

The "latest.log" is not much help. The "fml-client-latest.log" is FAR more useful as it has actual error information with context around it.

The /mods/mekanism.zip file serves no purpose and should be removed. You should ensure your mod file names are what the author is distributing. For instance, your CustomNPCs mod has "copy" at the end of it. Your Mekanism mod is out of date. You are using an old version of Java 8. Update to the latest build. It looks like you are allocating only 1G to the Launcher. Try upping that to 2G. This error: GL info: ~~ERROR~~ RuntimeException: No OpenGL context found in the current thread. indicates that there is something wrong with your PC. The pack works for me no matter how many times I start it.

​Or, you could look in the forge log (fml-server-latest.log to be precise) and it will tell you exactly what's missing and exactly which mod is requesting it.

We would need the crash report and the latest FML log from a client that crashes. Since you stated yourself that it seems "random" (but probably isn't) we can't just guess at the problem. Also, always provide the API URL or a link to your pack details page when requesting custom modpack assistance.

You have an active thread for this issue. Don't start a new thread as that just makes it much harder to provide support. Also, always use a pastebin service to post log/crash data instead of putting it in the thread. Do this in your previous thread and also provide the API URL or a link to your pack details page.

Bar some extraordinary measures or better backups, once it's deleted it is truly gone.

That error indicates that one or more of your mods either: Is a client only mod intended for use only on the client. Is poorly coded and is not properly proxying/protecting the client code in a universal mod.

Always provide the API URL or a link to your pack details page when requesting custom modpack assistance. You have a coremods folder with something inside of it. Forge for 1.7.10 (actually >= 1.6) does not use a coremods folder in any way. All mods belong in or below the mods folder. I'll take another look after you provide the API URL because your pack works fine in my test environment.

Making a server from a pack: http://forums.technicpack.net/topic/61989-server-of-fury-i-would-like-more-help/#comment-519381 During your testing and assembly the config folder in your test environment will be populated with all the config files. These should be included in your modpack archive after you are finished fine tuning things for compatibility and interaction between mods.

Where did you check for those mods? iChun lists version 4.2.2: http://ichun.us/mods/ichunutil/ Mo' Creatures lists the CustomMobSpawner requirement with a download link: http://mocreatures.org/downloads

This is a well known issue with Forge for 1.6.4 and Java 8 which is addressed by adding Lexmanos' legacy java fixer (it's in your client pack) to the server's mods folder.

Always provide the API URL or a link to your pack details page when requesting custom modpack assistance. (I assume this is your pack: http://api.technicpack.net/modpack/redacted-minecraft-server-mods ) You have Mo' Creatures mod but not the required dependency mod CustomMobSpawner. This requirement is clearly stated on all the author's download locations. Did you get this mod from the author? iChunUtil mod is out of date. Update to the latest 4.x version. Other than that the pack seems to work as expected.

As Disconsented suggested, your dropbox URL for your modpack is incorrect. Dropbox public share links must be changed in order to work correctly (make them direct). Change the "www" to "dl" and remove the "?" at the end and everything after it. Your /bin/modpack.jar is named modpack.jar.jar. Google "windows explorer always show file extensions" to learn how to prevent this problem. Your modpack.jar(.jar) file is in RAR format. All archives intended for use in the platform must be in ZIP format only. That being said, you should not be messing with the Forge JAR in any way other than to rename it to modpack.jar. The modpack.jar file is simply the correct version of the Forge universal binary JAR file renamed to modpack.jar. Don't extract it, don't recompress it, don't add anything to it. Just rename it. Your selected Forge version is very old. You will need to use a newer version of Forge. You have BigReactors (and MFR, ThermalDynamics, ThermalExpansion, ThermalFoundation) but are missing the required dependency mod CoFHCore. Your Extra Utilities mod is out of date. Your Tinkers' Construct mod is out of date.

You have altered your modpack archive download without changing/incrementing the pack version number. The only way the Launcher gets notified that an update is available is if the version number changes. Your modpack archive is in RAR format. All archive files intended for use in the platform must be in ZIP format only. You should remove the "(1)" from iChunUtil (and any other mod file names). This sometimes causes issues. You have somehow found an ancient version of Thermal Foundation. Make sure you are downloading the mods directly from the authors. This needs updated. You have added the 1.8 versions of CodeChickenCore and Not Enough Items. You need the latest 1.7.10 versions. That attention to detail would go a long way.

I get a "domain does not exist" error. Not that the file gets redirected, but that the domain doesn't function at all.

As it seems you already figured out, it is "mods" not "mod" for your mods. You are missing CoFHCore, a required dependency mod for Thermal Expansion. You have iChunUtil for Forge/MC 1.8. You need the latest 1.7.10 version (4.2.2). You are missing Mantle, a required dependency mod for Tinkers' Construct. You are missing Thermal Foundation, a required dependency mod for Thermal Expansion. You are missing CodeChickenCore and Not Enough items, both of which are required for NEI Integration and NEI Addons. It would be prudent to have a bit more attention to detail. Each of the authors explain at some length the installation process which includes an enumeration of which dependency mod(s) must be installed. Address these issues and come back here if you are still having difficulties.

The contents of your modpack are in a subfolder. The three required folders (bin, config, mods) must be a the top level of the folder structure inside the modpack archive. You are missing the /bin/modpack.jar. The modpack.jar file is the correct version of the Forge universal binary JAR file renamed to modpack.jar. You have EnderIO 2.2.x and Mekanism 8.x. EnderIO 2.2 if for Mek 7. You need to update to EnderIO 2.3.x. Calclavia's mods should currently be considered dead (MFFS, Resonant Engine, Resonant Induction, Universal Electricity) and should be removed. You might be able to get some of them working, but it will take some research and testing. Project Red is out of date with known critical issues. Address these issues and come back if you are still having troubles.

That link doesn't work for me at all.

I don't know what to tell you, man. It works fine for me and I'm able to use the pack and it works as expected.

If you can provide the URL you are trying I'll run it through the tester.

Use a pastebin service for log data. Additionally, please provide the latest forge log from the /logs/ folder (also in a pastebin).

@Er0194: How could you possibly know that you have the same problem when you can't see what OP's problem was? This is why we don't hijack other people's threads. Your issue (which is almost certainly not the same) is that you haven't added Lexmanos' legacy Java fixer to your server's mods folder.