plowmanplow

Support requests for modpacks made and maintained by Technic need to be made in the Tracker for the pack. The link to the tracker is at the top of this page.

Every item and block must have a unique ID. Blocks need to be <=4095. Items must be <= 31743 (as set in the config files) and should be >= 4096.

Download Cauldron installer here: http://files.minecraftforge.net/Cauldron/ Run the installer you downloaded in Step #1

For some reason you seem to be missing the Forge libraries for 1.5.2. I have them here: https://copy.com/FgQpweRKxPeE?download=1

I won't be near a PC to work on this until late tonight or tomorrow morning.

If you only have access to vanilla items/blocks then you are starting the minecraft server jar instead of the Forge jar (Voltz.jar).

If you want people to test or try your pack then you need to post a link to it. Making people request or "register" for it means that basically no one will do so.

Your CFM mod (Crayfish Furniture Mod) is extremely out of date. Update to the most recent version here: http://www.mrcrayfish.com/furniture.php?p=2 In the future, please include a link to your modpack page or API URL to make it easier for us to support you. There may be other problems with the pack and doing all the debugging at once instead of one error at a time is much more efficient.

Forge 1.6+ does not use a coremods folder in any way. All mods belong in or below the mods folder. Since you have all the mods currently in the coremods folder inside your mods folder it is safe to just completely remove the coremods folder (along with the unneeded libraries folder) from your modpack. You have woefully outdated versions of KeithyUtils and Metallurgy. Update both of those to the most recent versions for 1.6.4 (1.3.30 and 3.4.0.29 respectively). You have a block ID conflict between Metallurgy and Steve's Carts at ID 909. You have item ID conflicts between: Metallurgy & xReliquary, Simply Jetpacks & BigReactors, Tinker's Mechworks & Metallurgy, Metallurgy & Mekanism, Food Plus & Carpenter's Blocks. You have a file named "CodeChickenLib-master (1).zip" in your mods folder. This should be removed. You have the Forge universal jar in your mods folder. This should be removed. Your ChickenBones' mods are mismatched. Download the correct updated versions here: http://www.chickenbones.craftsaddle.org/Files/New_Versions/links.php You need to updated ProjectRed to the latest 1.6.4 version as the one you currently are using has known crashing problems. Fix all of that and if you are still having problems just come back here.

In your current pack: Your version of CoFHCore and ThermalExpansion are mismatched. You need to upgrade to CoFHCore 2.0.0.5. You have 3 block ID conflicts between Advanced Repulsion Systems and Witchery. You need to update to the latest MMMPS and Numina builds here: http://build.technicpack.net/view/MachineMuse/job/ModularPowersuits/ You need to change the value of B:"override vanilla blocks" to false to fix the Chisel/Glass Pane related crash.

You'll need to contact the pack author/creator to get assistance with that pack. Making suggestions about how to fix it would be futile since you don't have the ability to persist any changes.

You can share individual files with Dropbox with a free account. Simply share the file, copy the link and append "?dl=1" to the URL.

Each mod has a config file associated with it (or should). Fix the IDs in your local client pack (the path you referenced) then once you get everything working correctly you would simply include that full config folder in your modpack archive.

Cauldron (formerly known as MCPC+) has moved sites and build services. The new downloads are here: http://files.minecraftforge.net/Cauldron/ If you want Forge and Bukkit plugins that is what you'll need to use.

Yes, for instance: 500: classReika.RotaryCraft.Blocks.BlockMIMachine from RotaryCraft - block.solderingstation from extracells Both RotaryCraft and ExtraCells are setting a block to use ID 500. You need to change one of them to a different ID.

Which ID conflicts? The block ID or item ID conflicts? After you get all the other problems fixed and start the pack it should generate an IDConflicts.txt file and warn you about it. Open that file. It references which mods are conflicting on which blocks. Just change one of their configs. For item ID conflicts, you have to examine your FML client log for the word "CONFLICT" (without quotes) and fix them the same way as block IDs by changing the config of one of the mods.

Or just post the download somewhere I can access it. Trying to diagnose crashes when you have numerous item ID conflicts is a recipe for frustration.

So, just so we are on the same page, you are trying to make a server for someone else's modpack? If you don't have control over the modpack then you cannot change anything during the server setup process or the client won't be able to connect. If you want to change things just start with that pack, change what you want and then make a new pack of your own in the Platform. That being said, here is what I did to make a server with this pack that I could connect to with the (unaltered) client: Start the client. The modpack does not include a full compliment of config files and those will be needed for the server. We will refer to the client modpack folder as CLIENT. Create a folder for your server. We will refer to that folder as SERVER. Copy the config, Chocolate and mods folders from CLIENT into SERVER. Remove the following client-only mods from the SERVERmods folder: Enhanced Books In Game Info StatusEffectHUD Damage Indicators minecolonies Rei's Minimap Download the Forge installer for 1.6.4 (#965) and install the server into SERVER. Rename the Forge jar in SERVER to "forge.jar". Create a batch file to start your server with and use a line similar to this to start the server: java -Xms2048m -Xmx2048m --XX:PermSize=128m -jar forge.jar nogui Launch the newly created batch file to start your server, connect and enjoy.

The modpack currently referenced in your pack settings STILL has most of the problems I have already mentioned. Fix those problems, all of them, and then we can continue diagnosing crashes if they still happen.

Getting Mods:

You'll just have to go through the pack and test things to figure out which mod is causing the problems. Removing that mod will be the only way to get your pack working (unless there's an update for it which might fix things as well).

those are usually safe to leave. Some mods overwrite vanilla stuff on purpose.

Since you didn't provide it, check the end of your ForgeModLoader server log. It will have more details concerning the crash. For additional assistance, please provide a link to your client pack page or API URL.

One of your mods is not properly using the Forge entity registry. Not sure which one. OreSpawn is a common cause, but you don't have that.

Item IDs must be <= 32006, and preferrably between 4096 & 32006. However, an in-game ID 31999 would (usually) correspond to a config setting 256 below that, thus the 31743 as the preferred maximum setting in your config files.