plowmanplow

If you do this: and remove Damage Indicators your server will work.

After downloading Millenaire mod from the author's website, removing the existing millenaire folders from the pack, installing the new folders from the new download and re-building the pack I was able to successfully get the launcher to work with your pack.

As I mentioned before, millenaire mod does something "funky" with their filenames which makes the zip extractor built into MC die. I don't know if they do it on purpose or it is due to them not understanding how to package a mod properly but that is the source of your problems. Unfortunately I don't have time this evening to figure out exactly which file is messing things up as the technic log isn't providing enough information. If you are still having trouble tomorrow I'll check it out then.

It's awfully hard for me to troubleshoot something I can't see. When you have the download URL updated in your pack settings with an updated pack I can provide additional assistance.

Damage Indicators mod is a client only mod. It must be removed on the server.

You are still putting mods in the coremods folder. If you aren't going to follow my advice it doesn't make a lot of sense to continue providing it. As is clearly stated where you download the mod, Computercraft 1.64pr3 is for Forge/MC 1.7.2 and 1.64pr4 is for Forge/MC 1.7.2. 1.63 is for Forge/MC 1.6.4. You STILL have a mishmash of mods for different versions of Forge/MC. As your pack currenlty stands you have mods for 1.6.4, 1.7.2 and 1.7.10. THIS WILL NOT WORK. If you are making a 1.7.10 pack you need to be using mods which are all specifically for 1.7.10. Some mods work for both 1.7.2 and 1.7.10 but in those cases the author will clearly state that. Your modpack settings have your pack set to 1.7.2. Are you making a 1.7.2 pack or a 1.7.10 pack? You need to make a decision and make sure everything is set and configured for the same version. Read through this post, then fix your issues:

@bear251170: It would be best at this point to start a new thread in the Server Op Swap Shop forum so as not to pollute this thread. Include a link to your API URL in the post as well as a link to your latest Forge logs and the most recent crash report if you have one.

You need to be using the latest version of Cauldron instead of the default Forge as your server binary.

I maintain a modpack called BareBonesPack which exists for the purpose of debugging modpacks or building new ones. You might have an easier time using it:

Try changing the value of "cleanuptime" in the jcliteconfigChickenChunks.cfg file to 0 (zero). Like most 1.6.4+ packs that are large-ish, worldgen can be an HUGE load on the system. SSP basically runs a tiny server on your local system behind the client for you to play on. Moving rapidly creates a lot of worldgen (when in new areas) and can cause significant load. Try changing that value in the first bullet point and see if you have better results.

You may have approached the IRC channel from the wrong perspective. You may have better luck going in like so: State that you seem to be having a hard-freeze/threadlock issue with your server. State that you have a stack trace of the frozen/locked server and provide a pastebin link to the stack trace. Wait for relevant response.

This would require the use and implementation of the Solder API.

I go into some detail about the configs in my post about how to use my BareBonesPack to build your client: Fixing ID conflicts:

Ahh. Are you attempting to set up a server for one of the default packs then? Can you provide more details as to your problems? Logs, crash-reports, console output, which modpacks, etc.

Your pack works fine for me both in my test environment and when directly added to the Launcher. Please provide the most recent log from the crash-reports folder in your client modpack folder if you are still having problems.

You have zipped up your entire client folder as your modpack archive. Your modpack archive should ONLY contain the folders "bin", "config" and "mods". The "bin" folder should ONLY contain the file "modpack.jar". Your modpack.jar file seems to be the correct version of Forge, but it is an odd size. Unless you have very specific, uncommon reasons for doing so the modpack.jar file is simply the Forge universal binary JAR file renamed to "modpack.jar". I would recommend fixing this. You have OpenBlocks mod but not the required dependency mod OpenModsLib. You have the GeoStrata mod but not the required dependency mod DragonAPI. You have the Mariculture mod but not the required dependency mod Enchiridion. Your BloodMagic mod is so out of date that it is conflicting with other mods. You have the FlatSigns mod for Forge/MC 1.7.10. You need to get the version for 1.6.2 (which works in 1.6.4). The GeoStrata mod has a fatal item ID conflict in the default configs. You can safely change the 10000-10006 to 11000-11006. You have the wrong ExtraCells mods. You need: ExtraCells-1.6.9e.jar (not the deobfuscated version) Your IndustrialCraft mod is out of date. If you intend to include IndustrialCraft for 1.6.4 in your pack I would recommend reading through this: There is a block ID conflict between GeoStrata and Mariculture for ID #800. Change GeoStrata's SmoothRock ID to 839. After figuring out all the problems a few things are clear: You are not testing the pack as you go. On cannot simply drop 75 mods into the pack and expect it to work properly. The pack must be built methodically with mods being added singly or in logical groups. It is clear that you are either not getting your mods from the author's preferred distribution channels or are not following their instructions for installation. You would probably benefit from reading through this: Come back here if you are still having troubles.

This likely belongs in the Tracker for the launcher. There is a link at the top of this page.

You should be downloading the Installer (Installer or Installer-Win) so that you can install it to your SERVER folder. This process will place the server JAR and a folder with the required libraries in your SERVER folder. There is a beta version of ComputerCraft available for 1.7.10 in their forums. The "builds" listed in the settings for BareBonesPack are the different MC and Forge versions available. For instance, you can select 1.7.10_10.13.0.1197 or 1.7.2_10.12.2.1147 (there are more options available). On the left is the MC version. On the right is the Forge version. Once you select one of the builds, click Save and then PLAY it will launch the client successfully and you should see the main client window. It will report that there are 3 mods installed.

My own take on how to make a client and server pack: Getting your mods: Using my BareBonesPack to make a client pack: Resolving ID conflicts: Creating the server: @bear251170: Read the links provided here. They will probably help you.

Try it with the latest version of Cauldron for 1.6.4. Blood hit his paetron goal so is now updating 1.6.4 with a lot of fixes from later versions. You might get better luck asking in Cauldron's IRC channel. It is possible to pull a stack trace from a running server if you have the JDK instead of the JRE using jps (to get the java process ID) and jstack (to pull the stack trace)

I have no clue which pack we are referring to anymore as this is now spread across three different posts. What is the API URL to the pack you are referring to with this crash? I do notice that you have Java 8 installed. Don't do that. Use Java 7 #65 64bit (latest Java 7).

It's just a Java app so it is likely a Java issue on your local client. Make sure you have the latest Java 7 JRE for your OS installed (and only that version). Also, this might belong in the Tracker.

You haven't provided enough information: Which custom modpack are you using? What is the API URL? Provide your most recent ForgeModLoader-server-0.log file as a file download somewhere. Don't paste it into the thread here.

What "modpack page" are you talking about? What "modpack folder"? Technic group has no official servers. All servers are run by community members for community members.

Your version of Thermal Expansion (3.0.0.b2) does not match your version of its dependency library CoFHCore (2.0.0.5) Don't copy mods from other modpacks. Read this: