plowmanplow

That isn't related to ComputerCraft other than a CC incduced crash possibly causing the DimDoors data to become corrupted. You may need to remove the DimDoors data from your world save in order to get it working again.

The Forge universal JAR in your /bin/ folder should be renamed to be "modpack.jar". Your Biomes O' Plenty mod is fatally out of date (not compatible with your version of Forge). Your ChickenBones' mods need to be updated. You probably want to be using the 2.3.x branch of EnderIO, not the 2.2.x branch. Your ProjectRed is out of date. MineTweaker is in the pack, but no scripts are included. Is this intentional? Address these issues and come back here if you are still having difficulties.

Always provide the API URL or a link to the pack details page for any custom modpack assistance.

Please stop posting log data here in the thread. Use a pastebin service. Copy.com public share URLs must have "?download=1" (without quotes) appended to them in order to make them direct and work properly in the Platform. Forge for 1.7.10 does not use a coremods folder in any way. All mods belong in or below the mods folder. You should not be including the libraries folder nor its contents. CoFHLib is intended for use only by mod developers and should not be included in your pack. If you are looking to provide that functionality in a modpack you should be including CoFHCore. Your version of Not Enough Items is fatally out of date. You should be using the "latest" versions for 1.7.10. Thermal Expansion mod requires Thermal Foundation.

This thread belongs in the Platform Pagoda forum. Hopefully a patient forum admin will move it. Your modpack archive has no config files. For most 1.6.4 packs of more than just a few simple mods this is typically fatal. You need to be building your pack methodically in order to achieve/maintain a working state and then include the final collection of config files in your modpack archive. You have multiple mods from illegitimate sources. Any mod named in the format of "ModName-Mod-1.6.4" is almost always from an illegitimate source. Always get your mods directly from the mod authors. (Yes, this means you will need to re-download most of your mods from the correct locations). You have an incorrect version of IC2 i n your pack. If you intend to include IC2 in your 1.6.4 pack I highly recommend reading this post: http://forums.technicpack.net/topic/58847-industrial-craft-tekkit-164/?do=findComment&comment=482083 Address these issues and come back here if you have more troubles.

[21:36:48] [main/TRACE] [FML/]: Adding NotEnoughItems-1.8-1.0.5.104-universal.jar You have included NEI for 1.8 instead of the version for 1.7.10. Get the latest 1.7.10 versions of ChickenBones' mods from here: http://chickenbones.net/Pages/links.html

You have built what looks to be a 1.7.10 modpack, but your pack settings indicate a 1.6.4 modpack. You probably want to change your pack settings. You have the LiteLoader installer JAR in your mods folder. You need to run the installer and extract the liteloader mod JAR into your mods folder. Remove the installer afterwards. You have the CartLivery mod but not the required dependency mod CoFHCore. The MCF post nor the Curse page mentions it, but it is required.

Which specific packs? Does this happen with all packs? Only custom modpacks? Packs from Technic?

Copy the legacyjavafixer-1.0.jar from your client's /mods/ folder over to the server.

On your local computer, name your modpack ZIP file to: welcome-to-war.zip Upload that ZIP file to DropBox and get a new public share URL In that URL, replace "www" with "dl" and remove the trailing question mark and everything after it. Paste that altered URL into the modpack settings "Modpack Location" field and increment the pack version number. Save the settings.

OreSpawn both greedy in its acquisition of block/item IDs and course in its configuration options. The only option available is to set the starting ID for where OreSpawn begins swallowing IDs. For blocks it's not too bad and you can make it work with TekkitMain by changing the BaseBlockID setting thusly: I:BaseBlockID=3500 Item IDs are much more of a pain since OreSpawn handles item IDs in a very crappy way and takes A FREAKING TON of them. You would need to find a block of 500 consecutive item IDs for OreSpawn to not be in conflict with existing items. Turns out there is a suitable range here by setting BaseItemID thusly: I:BaseItemID=10500

Providing the API URL in your original post was sufficient for me to provide an analysis. I then told you what needed to be fixed. I will try to be more explicit. In your modpack settings is a field labeled "Modpack Location". This is the DIRECT URL used to download your modpack. This is what is current set in that field: https://www.dropbox.com/s/5v069xi6s0bqpaq/Welcome%20to%20war%20%281%29.zip?dl=1 However, that URL does not work and returns the HTTP error code 404 which means it was not found. You need to correct this before I can even look at the contents of your pack.

Always provide the API URL for your pack or a link to the pack's details page when requesting custom modpack assistance. That crash report does not match the data in your modpack archive. The crash report indicates Forge #1448 but the modpack contains Forge #1291. Where is the discrepancy coming from? Forge for MC 1.7.10 does not use a coremods folder in any way. It should be removed from the pack archive. All mods belong in or below the 1.7.10 folder. Legacy Java Fixer is not required for Forge >= 1230 and should be removed from your pack. Please address these issues and return here if you have more issues.

Your email is not necessary and probably shouldn't be in the post. This thread belongs in the Platform Pagoda forum. Hopefully a kind/patient forum admin will move it. The URL referred to by the "Modpack Location" setting in your pack is invalid.

How about that, right on the first link you provided are two of the things I asked for. Why am I doing your work? Details page: http://www.technicpack.net/modpack/cytrax API URL: http://api.technicpack.net/modpack/cytrax Unless I can get the FULL LOG from the server, which you seem to have (or at least part of), I will not be able to help you. You have said yourself that you are unable to fix it and think that the portions of the log you have provided are relevant. It is highly likely that somewhere in the rest of the log is relevant data. Now, I do this for fun and after I finish with dinner (hour+ from now) I might take the pack and turn it into a server and test with that pack just for my own edification. However, since I have no way of knowing (once I get it working) what your server setup is like any information I find will likely be of little use. If you really want to help fix this then get me a ZIP (or RAR, or tar.gz, or whatever) of these full folders from the server: /config/ /mods/ /libraries/ whatever server JAR is in use Edit: Client Pack Analysis The modpack is missing the /bin/modpack.jar file. The modpack.jar file is the correct version of the Forge universal binary JAR file renamed to modpack.jar. Many of your mods are fatally out of date, such as (but not limited to): Mekanism, EnderIO, Tinkers' Construct, Factorization, Botania, MystCraft, Biomes O' Plenty, Applied Energistics, Blood Magic, etc. At least some of your mods are fundamentally incompatible. For instance: EnderIO 2.2.x is compatible with Mekanism 7.x. EnderIO 2.3.x is compatible with Mekanism 8.x. You have them mismatched. You are making things harder on yourself by having 99% of the pack in a monolithic archive and only a couple extra "mods" being served by Solder. Until you are ready to fully switch to Solder you are better off keeping it a molithic pack. Until these issues are addressed there is no reason to move forward trying to diagnose a client <-> server communication issue.

Until you create an actual modpack in the platform, which we can see and test, it is very difficult to help you. Once you do that, I can say "Fix this, this, and that. Do this and that differently." If I were to start with that pack, push it into a test environment, add (and unspecified) version of OreSpawn, and then get it working I am basically making a pack for you and that's really not what we do here.

That's a bit like asking, "I'm going to be in a race. What kind of car should I have?" We would need much more details about things like which modpack (and its details), what kind of server process (Forge, Cauldron, etc.), server configuration details (view distance, etc.), what kind of plugins you might have... I'm sure you see my point.

This belongs in the Platform Pagoda forum. Please create a new thread there and provide the API URL or a link to your pack details page.

Which modpack? (API URL or pack details page link)

I have some experience working on custom modpacks and servers for the same. It's a hobby.

Many of your mods are from illegitimate sources. This causes many problems, not least of which is that you won't know what requirements the mod author has imposed (specifically things like which version of Forge to use). Any mods named in the format of "ModName-Mod-1.7.10.jar" is almost surely from an illegitimate source. Redownload all of those mods directly from the mod authors. Update your Forge to the latest 1.7.10. Update all your legitimate mods to their latest versions (such as Forestry, CoFH mods, etc.) The "forge-1.7.10-10.13.4.1448-1.7.10-universal (1).jar" file in your /mods/ folder should be removed. Forge is the modpack.jar file and belongs nowhere else.

We're still among the land of the living. Our latest addition to spawn is a fancy arena:

Always provide the API URL or a link to the pack details page for any custom modpack for which you are requesting assistance. Without that we will be unable to help you.

Always provide the API URL or a link to your pack details page when requesting custom modpack assistance. I would normally let this ride since DrDisconsented has linked to an excellent way to proceed. However, the platform profile for "MrGuyX" has no modpacks associated with it. Are you working on your own pack? Have you published it yet?

<sigh>forums</sigh>