plowmanplow

You have provided insufficient information to allow us to give you specific help. Here is a bit of general server making information: Thread on Custom Servers: '?do=embed' frameborder='0' data-embedContent>> My Creating A Server Summary:

The crash report from the first post is something you would see when you have a client-only mod in your server mods folder or when a mod that should work in SMP is not properly proxying its client only API calls. This "may" be coming from Chocolate Quest but without further testing it is impossible to know for sure. If you removed that and are still crashing then either you have problems with multiple mods or it wasn't Chocolate Quest causing the issue. As Vlandox mentioned, it is likely time for an updated crash report and a link to the API URL for the client modpack you are using.

I don't know what to tell you. No matter what I do to the BBP, as long as I remove the folders I listed above (bin, cache, lib, resourcepacks, texturepacks) it starts up exactly as it should. Also, the links you have provided so far have no crash reports in them.

The mod versions are reported to Forge by the mods themselves. As long as that reported version number doesn't change the client will not fail the synchronization check with the server.

Any time it "goes back to the launcher" you are seeing a crash. The latest crash-report should have lots of useful information. Feel free to put that in a pastebin and link it here or put it inside a spoiler tag in a post here.

Oh, yeah, you should never use multicore for chunk loading. Bad things happen.

The download URL set in the Platform pack settings page is not a direct URL. Being a copy.com link it needs to have "?download=1" (without quotes) appended to the URL. You have some very old versions of at least a few mods. ChickenBones mods are the beta versions and the release versions have been available for quite some time. Those should be updated. Your OptiFine should also be updated to the latest 1.7.2 version. Other than that everything seems to work fine and I am unable to reproduce your error? Can you provide some context for the issue? When does this happen? Can you reproduce it reliably?

In a Forge/MC <=1.6.4 modpack I feel I can say with confidence that the MOST important thing in the pack is the config folder and its contents. Without those files configured correctly and included in your modpack archive you will never have a successful pack. The modpack archive you just provided is in RAR format (even though it has a ZIP extension). All archive files intended for use in the platform must be in ZIP format only. You have removed all the minimap mods. I assume you wanted to keep one? You still don't have a mods1.6.4 folder with anything in it. (see previous post) You have many of ChickenBones' mods but don't have the required dependency mod CodeChickenCore. Again, this is all just from browsing through your mods folder. I don't know how to say it any more clearly than I did last time so I'll use red text in an effort to stress how important it is. Without a full compliment of config files, which have had all the conflicts resolved, in the config folder for your modpack your modpack will never work.

BareBonesPack (BBP) works fine right out of the box if you select a "version" in the pack settings. However, if you have previously used it for anything (even other versions of Forge) you MUST remove all the extra folders before trying to start it (when you are trying to "start over"). I have a script that deletes everything but these folders: bin, cache, lib, resourcepacks, texturepacks. That basically "resets" the pack to the default for the version you have selected. You don't have to add Forge to BBP. Forge is the only thing in it by default. The file binmodpack.jar is the Forge mod for the pack and should not need to be messed with or altered in any way in normal operations. Optifine for Forge/MC 1.6+ goes in like any other mod. However, it has very poor support for everything after Forge/MC 1.6. It crashes every pack I've ever worked with on Forge/MC 1.7+ when there are more than just a handful of mods present. You found the exact right locations to get both Forge and ChickenBones' mods.

@DiddlyDoo802: java.lang.IllegalArgumentException: Slot 1000 is already occupied by com.advGenetics.Blocks.BlockDNAAnalyser@5af6af5f when adding factorization.shared.BlockRenderHelper@7973b4a0 A clear case of a block ID conflict at ID #1000. This post about fixing ID conflicts may be helpful: On another note, problems like this probably belong in the Server Op Swap Shop. This thread is more about "how to make a server" than "I need help with my setup". If everyone who needed server/pack help used this thread it would get so polluted it would be useless.

We figured this out. A prime example of not trying to scale low-end power production to massive proportions. Hundreds of Galacticraft coal fired furnaces with thousands of coal in transparent item ducts = bad.

For those who come here looking for a solution to a similar problem, here is the link to the 1.5.2 (and 1.5.1) version of MCPC+: http://ci.md-5.net/job/MCPC-Plus-Legacy/

Your modpack.jar file is incorrect. The modpack.jar file is simply the Forge universal binary JAR file renamed to modpack.jar. You have included the incorrect version of HEE. Get the version for Forge/MC 1.6.4. You have included ReiMinimap mod for 1.6.2. Get the version for 1.6.4. CodeChikenLib mod goes in the mods1.6.4 folder. You need to manually download the latest version of Forge Multipart for 1.6.4 and put it in mods1.6.4. You have included the Forge universal binary JAR file in your mods folder. This should be removed. I'm not sure what the file modsICBM-1.4.2.386-wx9.003.zip is for, but it should probably be removed. You have two different versions of MineChem in your mods folder. One must be removed. The Mystcraft API zip is not intended for use in the client. Remove this file. WorldCore mod goes in the mods1.6.4 folder. You have included three map mods (ReiMinimap, MapWriter and Zan's Minimap). Pick one, not three. This report is just from looking through the mods folder. Attempting to start this pack without a full set of working, balanced, deconflicted config files is pointless so I have not done so. You cannot drop almost 200 mods into your mods folder at once and expect it to work. The pack must be built methodically. Add mods in singly or in logical groups (mods and their dependencies), testing as you go so that the config files get generated and you can resolve conflicts and address mod interaction. Good luck. You are going to need it. Come back here after fixing everything I have listed here if you have any additional issues.

The post on getting mods which was previously provided: Nowhere in that post does it say you should rename the mods you download. Additionally, it clearly states that you should only get mods from the mod author's preferred distribution channels. The mod you have included named "Not-Enough-Items-1.7.10.jar" is not the name of the file which you would have gotten from the mod author. It should be named "NotEnoughItems-1.7.10-1.0.3.48-universal.jar". Notice that the file name has the actual mod version number included. This is vital information for debugging and maintaining a pack. The same goes for "CodeChickenCore-1.7.10.jar" which should be named "CodeChickenCore-1.7.10-1.0.3.23-universal.jar". I'm not trying to pick on you. I don't know of any other way to encourage attention to detail than to point out the specific things which you overlooked and how they should be different. Fix these issues and come back if you are still having troubles.

Your Mekanism files are broken. Download them again: http://ci.indiewikis.com:8080/job/Mekanism/46/

Your download URL set in your Platform settings is not a direct URL. For any public share URL from copy.com you need to add "?download=1" (without quotes). Your IC2 mod has an odd file name. Either you renamed the file from the one provided by the authors or didn't get it from the mod authors. Either of these are extremely bad. You have NotEnoughItems mod but not the dependency mod CodeChickenCore. I have provided the exact same information for the same problems in other replies to your issues and [url='?do=embed' frameborder='0' data-embedContent>>. It would be much better for everyone involved if you more closely followed the advice provided to you. It turns out that you did have CodeChickenCore, but had it in the wrong location. Forge/MC does not use a coremods folder in any way, for any purpose after version 1.6. The coremods folder should not even be included in your pack.

Please provide a URL to one of your ZIP entries for mod versions in your Solder setup that you feel isn't working properly. I think there may be a fundamental misunderstanding about how the Solder API does versions and provides files to clients.

This post belongs in the Tracker for the Launcher which is available at the top of this page.

Forge Multipart is one of those mods which get downloaded automatically by the pack (deploaded) when requested by other mods which require it. In your case, you have built a 1.6.4 pack but included the 1.7.10 version of Mekanism. You must use matched versions of Forge, mods, and all dependencies. Additionally, Things like Forge Multipart should be manually added to your modpack archive so that it doesn't have to be downloaded automatically and you can specifically include newer versions than the ones requested by the mods. The Forge Multipart mod belongs in the mods1.6.4 folder (for a 1.6.4 pack... I am sure you can figure out the pattern).

What modpack is this? Please provide an API URL. Try removing OptiFine. OptiFine for 1.7.2 is incompatible with a TON of mods.

The contents of your pack are in a subfolder inside the archive. All of the required folders (bin, config, mods) must be at the top level of the folder structure inside the modpack archive. You have included too much stuff in your archive. The fourth bullet point on using the BareBonesPack is quite explicit on how to package your archive once it is working correctly. Go back and read that. Recreate your modpack archive. When I provide a guide or a how-to it is vitally important that the instructions be followed completely and in order. When making a cake you can't just decide to leave out ingredients or the results you pull out of the oven will be inedible. Making a pack is the same way. Come back if you still have problems.

Provided you update your pack correctly (change what you want locally, create your modpack archive from that local data, upload your modpack somewhere public and get a direct URL, change your pack settings to refer to the new direct URL and increment the pack version) all clients will get a notification that the pack has updated and allow them to update their installation of your modpack.

Update your Java to the latest Java 7 JRE 64bit. Update Project Red to the last/latest version for 1.6.4 (yours is ancient). Update CoFHCore and Thermal Expansion. Update to the latest version of PowercrystalsCore for 1.6.4. Update all your OpenMods mods to their latest 1.6.4 versions: http://openmods.info/ Update to the latest versions of all of ChickenBones mods for 1.6.4: http://chickenbones.net/Pages/links.html

Starting with Forge/MC 1.7+ you just add liteloader like any other mod. Put the LiteLoader JAR file into your mods1.7.2 (or mods1.7.10) folder and you are done. No need to mess with anything in the Forge JAR at all.

Something is looking messed up with Gany's Nether. By itself it works fine but with the rest of the mods something is going off the rails and causing packet/proxy communication errors between the client and server. While it may be the fault of another mod I would focus my energy on Gany's Nether until you can prove otherwise.