plowmanplow

Your bin folder should only contain the modpack.jar file. Remove the other contents. You have included no config files with your pack. In your case this is a fatal oversight as the default config files generated by the mods have multiple block ID conflicts. You need to resolve these locally then included the resulting fixed config files in your modpack archive.

If you have updated your pack settings with a new version/download then I can check it out. However, in the future please be more specific than just "I failed again". Also, make sure you are using spoiler tags when posting large copy-paste/logs/etc. Edit: In the future, please provide a link to your Technic pack page or API URL: http://www.technicpack.net/api/modpack/mechanical-vincenzo The download URL you have configured on your pack settings page is not "direct". For copy.com links you need to add "?download=1" (without quotes) to make a link direct. You have an exceedingly large number of item ID conflicts which will make large portions of a number of mods unusable. Check your ForgeModLoader-client-0.log file for the word CONFLICT.

The bin folder should only contain the file "modpack.jar". This file is the Forge universal binary JAR file renamed to be "modpack.jar". You have a ton of mods in the mods1.6.4 folder. This folder is only for specific libraries used in conjunction a few mods and will usually be downloaded by the mods themselves. Nearly all the mods you have in the folder belong in the mods folder. You have a mods1.6.2 folder with a version of REIMinimap for 1.6.2. This folder and the mod contained within need to be removed. You have a version of Metallurgy mod for 1.6.4 but the dependency library KeithyUtils for 1.6.2. Always follow the mod author's instructions and get the correct files/libraries associated with a mod at the same time and location. Many of your mods are very out of date. You would likely benefit from going through them all to make sure you have the latest stable versions. This page might help you with that:

Ahh. Dynamic Lights is a client-only mod. It must be removed on the server.

I'm really not trying to pick on you. It's just that when you have such critical issues and ask for other assistance before addressing those issues I can't really suggest anything because any additional fixes/changes have to be predicated on the original issues being resolved first.

You use the zip file.

You want the folder structure to look like this. '> Note that all those folders are currently selected. You would do the same, then right-click and add them to a zip file.

Make sure the "cleanuptime" setting in ChickenChunks.cfg is set to 0 (zero).

Just like anything else Forge/MC related. You download the newest version and follow the author's installation instructions.

The folder structure inside your archive ZIP file looks like this: Crafting Z 1.6.4 |- bin |- config |- Flan |- mods Note that the required folders are inside of a top level folder. This is wrong and will cause the pack not to work. All four of those folders should be at the top level of the folder structure. Practically speaking, you need be inside the folder on your hard drive with those folders and select JUST those folders, right-click and use the context menu for your ZIP archiving software to create the modpack archive.

The contents of your modpack are still inside a subfolder. Both previous points about your modpack.jar file have not been fixed. Many of your mods are absolutely ancient. You need to go through and update the outdated mods. You have a staggering number of item ID conflicts. Check your ForgeModLoader-client-0.log. If you aren't going to fix/address all the issues I clearly point out why are you asking for more help? edit: You really don't want to be including a world save in your modpack archive. Provide it as a separate download. The zip file in your resourcepacks folder is not a valid resourcepack.

Running: MCPC+ version git-MCPC-Plus-jenkins-MCPC-Plus-164-230 (MC: 1.6.4) (Implementing API version 1.6.4-R2.1-SNAPSHOT) This shows that your server JAR is MCPC+ B230. The bug you are having was fixed in B251, but there are MUCH newer versions of Cauldron available. MCPC+ switched to the name Cauldron a couple months ago.

That error is typically caused by using a mod for a different (usually newer) version of Forge/MC. I would need the bottom few hundred lines of your most recent ForgeModLoader-client-0.log file to know which one(s).

Ahh, now that is a crash report I can work with and is unrelated to your other issue. That is caused by using an amazingly out of date version of MCPC+. MCPC+ is now called Cauldron. You need to get the latest version of the Cauldron installer, install it, and switch to using that.

The whole point of me providing feedback to you is for you to learn how to resolve these problems yourself. I have responded twice with almost the exact same information and this is likely the same issue. Providing a crash report with no additional information about context, what was going on when it happened, the relevant section of your ForgeModLoader-client-0.log file, or anything else makes the crash report basically useless. I'm typing this as I wait for the pack to download again. If it's the same issue as before I might be grumpy. ... The solutions to your problems are in a previous post in this thread: It squanders my time to ask for more help when you haven't fixed the problems which I have previously diagnosed.

In the future, always provide a link to your modpack page or API URL link. I did some sleuthing and found it myself here: http://www.technicpack.net/modpack/details/mechanical-vincenzo.428629 The download URL link you have set in your modpack settings is invalid.

The pack seems to launch for me. That being said, you have a TON of item ID conflicts you need to resolve for the pack to be playable.

Inside dimensions for nether portals in Forge/MC <=1.6 is 2x3 WxH.

That looks like an error caused by using a 1.7.2 or 1.7.10 version of a mod with the 1.6.4 Forge you seem to be using.

@FatmanPWNS: what you are thinking of is PermSpace or Permanent Generation Space. When you have a ton of mods, or many large mods it is sometimes necessary to increase the PermGen (PermSpace) allocation when using Java 7 or earlier. However, there are very specific errors that show up if you run out of PermGen memory allocation and that doesn't seem to be the case here.

That sounds like BungeeCord and I'm pretty sure it won't work with current Cauldron for 1.6.4.

@itiri45: Your reading comprehension must be a bit below grade if you make a post hijacking another thread right below a post by me saying don't hijack someone else's thread.

I believe that qCraft can accomplish this, provided both servers have the exact same mods/configs.

On Forge/MC 1.4.7? Yeah, pretty much.

Assembling a modpack with those three mods would take about 5 minutes. Go for it. The challenge with what you are asking for concerning searching is that the vast majority of packs are large, monolithic zip files containing a collection of mods, configs, etc. Technic has no practical way to retrieve and index the contents of all of those remotely hosted modpack archives.