plowmanplow

Since you have yet to provide a link to your Technic pack page or API URL I can only assume you haven't updated your modpack yet and are referring to the version I did my previous analysis on. I have already said it a couple times so I am not sure how to be more explicit. Do these steps EXACTLY as I state here and your modpack.jar should be fine. Your current version is completely messed up, as previously mentioned: Download the Latest Forge universal binary JAR file from here: http://files.minecraftforge.net/ Rename the file you downloaded in Step #1 to "modpack.jar". Place the file you renamed in Step #2 in your bin folder.

You have include a version of Soul Shards for 1.5.2 which requires a minimum verison of Forge to be 7.8.0.716 but your version of Forge is 7.8.0.684. Update to the latest version of Forge for 1.5.2: http://files.minecraftforge.net/minecraftforge/index_legacy.html

Don't hijack a thread, especially an extremely old one like this, with a new problem. Start a new thread, provide links to your Technic pack page or API URL and try to clearly state your problems.

The API URL is the URL that you copy/paste into the launcher to add the pack. Your modpack contents are all in a subfolder. This won't work. The main folders (bin, config, mods, etc.) MUST be at the top level of the folder structure in your modpack archive. As I mentioned previously, your modpack.jar is STILL in RAR format. That file MUST be a ZIP format archive. Just download Forge and rename it to "modpack.jar". Don't extract it. Don't move things around inside of it. Don't re-compress it. Just rename it to modpack.jar, put it in your bin folder and you are done. Forge/MC 1.6.4 does not use a coremods folder in any way. All mods go in, or below, the mods folder. Fix these and come back if you still have problems.

It is safe for you to interpret that bullet point as "Download Forge and rename it to modpack.jar".

Forge does not include that option by default. Take a look at the file I liked for an example of how to add it.

Keep in mind that most, but not all, item IDs are up-shifted by 256 in game versus what is set in the config files.

Since none of the links you have posted in this thread function it will be difficult to help you. Post a link for your Technic pack page and/or API URL.

Be more specific. The "second step"? The second step of what? The second bullet point? The second paragraph? Please state precisely which part you do not understand. Is that the only part you don't understand?

If you are using dropbox, and have a current public URL then yes, you would add ?dl=1.

This probably belongs in the Tracker for the launcher (top of this page).

Make sure your client pack is working well. No unresolved item ID conflicts (check your FML client log). Create a folder for your server. We'll refer to that as SERVER. Install Forge server into that folder. http://files.minecraftforge. http://files.minecraftforge.net/ Copy the config and mods folders (and any other pack specific top level folders like Flan or Chocolate) to SERVER. Remove any client only mods from SERVERmods. This would be things like DamageIndicators, ArmorStatusHUD, BloodParticles, Optifine, etc. Start server with a command like: java -Xmx2G -Xms2G -XX:MaxPermSize=128m -jar forge.jar nogui That's it.

ID numbers for blocks, items, biomes, enchantments, potions, etc. are completely arbitrary except for the restriction that certain types of IDs should be in certain ranges: Blocks <=4095, Items <=31743, Biome & Enchants <= 255, Potions <= 31. There would almost never be a reason to edit every single ID in all the mods. Just examine your FML client log while building/debugging the pack to identify conflicts and fix those. The only mods you can't edit are those that don't provide config files. Believe it or not there are still people making mods with in-game content that don't make or use config files. Hard coded IDs are the suck. I have seen situations where someone tried to make a pack with two of these that conflicted with each other. The only way around this is to remove one of them. PermSize can easily be increased by editing the version.json file in your modpack.jar. Here is an example of a 1.6.4 modpack.jar with increased PermSize: http://solder.circlecraft.info/mods/minecraft-forge/minecraft-forge-1.6.4_9.11.1.965_PG.zip The "correct" way to build a pack (IMO) is to start with JUST forge in the pack (binmodpack.jar). Make sure that works and then start methodically adding mods. Add them singly if they stand alone (like BuildCraft or Mystcraft) or in logical groups (all Immibis' mods, ProjectRed's mod collection). Test continuously so that you will know exactly what is causing the problem and can more easily resolve issues. Adding 100 mods into a pack and then trying to start it just yields frustration.

Heh, I suspect you answered your own question there.

@rjstonge: It will give you that error if there is something fatally wrong inside your modpack archive. In your case your modpack.jar file is all screwed up: It is in RAR format. All archive files intended for use in the platform MUST be in ZIP format. The contents of the modpack.jar file are inside a subfolder inside the archive. This is "bad". The modpack.jar file is simply the correct Forge universal binary JAR file renamed to "modpack.jar". Don't mess with it other than renaming the original downloaded Forge JAR. There may or may not be other problems. I didn't test the pack locally. If you still have difficulties after fixing this just come back here. @emesquita: I responded to you in your thread.

You still have the Helicopter mod extracted. Fix that. Look in your ForgeModLoader client log: [iNFO] [sTDOUT] CONFLICT @ 31743 item slot already occupied by com.advGenetics.Items.ItemScraper@61fad4bd while adding am2.items.ItemOre@1aa4f68c [iNFO] [sTDOUT] CONFLICT @ 31739 item slot already occupied by com.advGenetics.Items.ItemHelix@512237ed while adding xreliquary.items.ItemEmptyVoidTear@1d85d238 [iNFO] [sTDOUT] CONFLICT @ 31722 item slot already occupied by icbm.core.items.ItemPoisonPowder@54ab46fe while adding mods.gra.energymanipulator.common.item.ItemEnergyBattery@526a6c53 These are three of many conflicts reported in the FMLClient log.

Things I mentioned in my last assessment which have not been fixed: Your mods are still mostly missing the version numbers in the file names. Baubles mod is out of date, and the old version is now a couple sub-folders down inside the mods1.7.2 folder. Fix this. Fix these, and I mean really fix them, then come back here if you are still having troubles.

You have still included almost no config files in your modpack. I cannot emphasize enough how important this is. Without configs you simply DO NOT have a correctly assembled modpack. Your config folder has 4 files in it. It SHOULD have 48 files. Fix this. You have not included Forge Multipart mod in your mods1.6.4 folder. This mod will be automatically downloaded when required, but it will get the bare minimum version required to act as a dependency library. You need to manually download Build #250 and put it in your pack. As for your pack, I am able to start it successfully. Not sure what else you need.

Your modpack.jar file is in RAR format. All archive files intended for use in the platform MUST be in ZIP format only. Your modpack.jar contents is inside a subfolder. The modpack.jar file is simply the Forge universal binary JAR file for your chosen version renamed to modpack.jar. Don't extract it, don't mess with it, don't do anything but rename it unless you REALLY know what you are doing. Not sure where PowerCrystalsCore-1.1.8-10.jar came from. Pretty sure the last released version was 1.1.8-9. Might want to look into that. You need to upgrade to 4.3.7.32 of ProjectRed. You have ArmorStatusHUD installed but not the dependency mod bspkrsCore. You have Chisel installed but not the dependency mod AutoUtils. You have CompactUtils installed but not the dependency mod Aroma1997Core. You have RotaryCraft installed but not the dependency mod DragonAPI. You have Modular Force Field Systems installed but not the dependency mod CalclaviaCore. You have (an outdated version of) Modular Powersuits but not the dependency mod Numina. You have Portal Gun installed but not the dependency mod iChunUtil. You have ThermalExpansion installed but not the dependency mod CoFHCore. You have ThaumicTinkerer installed but not the dependency mod ThaumCraft. Thaumic Tinkerer "enhances" the large mod that is ThaumCraft. It is useless without ThaumCraft. You have More Food installed but not the dependency mod ClashsoftLib. You have Opis installed but not the dependency mod MobiusCore. You have Immibis Microblocks installed but not the dependency library Immibis Core. You have a completely ancient version of Immibis Microblocks installed. However, the file does not have the same name as the files downloaded from the author's website. The implication is that you didn't get the mod from the author. This is always "bad". The default config files generated by the mods have a staggering number of block ID conflicts. You need to work through all these to fix them because the pack will never start unless you do. You have not included any config files with your modpack. Config files are generated the first time each mod is injected into Forge/MC. The config folder and all of its contents MUST be included in your modpack after all conflicts have been resolved. Without getting the pack to start (see previous bullet point) it is impossible to say, but I suspect there are numerous item ID conflicts in the default config files. After resolving all the block ID conflicts you will need to inspect the ForgeModLoader client log to identify item ID conflicts and resolve any which can be resolved. It is clear that you have never tried to test or debug this pack locally before assembling your modpack. It is also clear that you are either not getting the mods directly from the author's preferred distribution channels (don't copy mods from other packs) or have failed to read any of the author's installation instructions. This is "bad". Always follow author's instructions. Always get mods directly from the mod authors preferred distribution channels. The "correct" way to create a pack, especially one this big, is to start with ONLY forge in your modpack (binmodpack.jar) and make sure that works as expected in the launcher. Then methodically add in mods singly, or in logical groups (mod and dependency, multi-part mods like ProjectRed, etc.), so you can test things as you go and identify individual problems before you have a large laundry list of problems like you see above. Make all of these corrections and come back here if you are still having trouble.

The modpack download URL in that pack's settings points to a file that does not exist.

Always provide a link to your pack (API URL works great) when asking for help. You have cut off most of the error information. I assume this is from a crash-report, but not 100% sure. This problem might be related to IC2 if you are including that. If you are attempting to include IC2 for 1.6.4 you need to check out this post:

Correct, I am not aware of any 1.6.4 mods which implement the CC 1.6 BundledRedstone API. Most of the mods you are familiar with (MFR, PR, etc.) will never support it directly on 1.6.4.

You are getting an unknown host exception for dropbox.com which is odd. However, you also have your URL set incorrectly for downloading your modpack. The URL must be a direct download. If you use the URL and it takes you to a page which presents you with a download button it is not a direct URL. You need to append ?dl=1 to the URL, like this: https://www.dropbox.com/s/u6hgbvqbvypcvki/modpcak.rar?dl=1

CC 1.6 changed the API such that any "bundled" cable (MFR Rednet, PR Bundled, etc.) must be implemented by the individual mods. That means that, for 1.6.4 at least, few mods will support direct integration with CC. MFR & PR both have frozen 1.6.4 development so those two are definitely out.

You run the installer: (replace the listed version with the name of the installer jar you downloaded) java -jar cauldron-1.6.4-1.965.21.83-installer.jar Select "Install Server" and choose a folder to install it into. That's it. There's nothing else to do.