plowmanplow

When I try to click that link I get a HTTP protocol error 403. That means access is forbidden and I do not have the rights to download the content in question.

Maybe I wasn't communicating very well. I'll try to be a little more verbose: Forge/MC for 1.6.4 and up does not use a coremods folder in any way, under any circumstances. If there are items in that folder inside a modpack archive they will be totally ignored. The very thing that the person above complained about, that it doesn't find bspkrsCore, is because that mod is inside the coremods folder. Simply moving it over to the mods folder (along with the rest of the contents of coremods) corrects the problem. Looking inside the ForgeModLoader client log when using the config/Flan/mods folders from your assembled modpack archive yields dozens of item ID conflicts. These can be found by searching for the word "CONFLICT" (without quotes). Some mods purposefully overwrite existing IDs so a few conflicts, depending on the mod in question, are not necessarily bad. However, the large number that exist between wildly differing types of items and mods means that the mods in question will operate in unexpected ways or not at all. These MUST be fixed for proper modpack/mod operation.

This probably belongs in the Tracker for the launcher.

@Pugsley: The pack you provided a link for in post #12 in this thread: The modpack.jar file is oddly sized. This file is just the Forge universal binary jar renamed to modpack.jar. Nothing more, nothing less. There are a number of files in the coremods folder. Forge/MC 1.6.4 does not use a coremods folder. All mods go in the mods folder. There are item ID conflicts between: BCTools & Metallurgy, BakingCraft & something (maybe, not familiar with this mod or its initialization), FoodPlus & Carpenter's Blocks, FoodPlus & Metallurgy, FoodPlus & Turtle. Failure to fix these conflicts will result in significant problems.

Different mods have longer initialization times. The bigger or more invasive the mod, the longer it takes. GregTech, for instance, takes forever but that is just one example.

The modpack.jar file in the bin folder is just a ZIP format archive. Rename it to "modpack.jar.zip", open it with your preferred ZIP archive program and pull out the version.json file. The top of the file has a line with a few parameters. Simply add/change the ones you want with your text editor of choice and then drag the file back into the modpack.jar.zip archive. Rename the file back to modpack.jar and you are good to go.

@Clonex10100: It looks like you have Mek Tools and Mek Generators but not the core Mek mod itself. This is just reading information from your log file. Try re-downloading all three mods from here: http://ci.aidancbrady.com:8080/job/Mekanism/

@DiddlyDoo802: I recently saw that when debugging someone's custom pack. If my memory serves (and it seldom does) that error might be related to you having the MCCapes mod on your server. That mod doesn't work on an SMP server.

That crash report kind of looks like you might be trying to use Cauldron (formerly known as MCPC+). The library locations changed a while back and only the latest versions of Cauldron will automatically retrieve their libraries. You can either get the latest Cauldron here (best option): http://ci.md-5.net/job/Cauldron-164/ Or get the libraries here: https://copy.com/qLsTvZfUUkkb?download=1

Unless you are having trouble with the pack itself we have no need of your pack page link or API URL. You need to edit the version.json file in your modpack.jar file. A version.json file with a setting for 256m of permgen space would look like this (at the top): { "minecraftArguments": "--username ${auth_player_name} --session ${auth_session} --version ${version_name} --gameDir ${game_directory} --assetsDir ${game_assets} -XX:MaxPermSize=256m --tweakClass cpw.mods.fml.common.launcher.FMLTweaker", "libraries": [ The file can just be pulled out, edited and then placed back in the archive. Simply rename your modpack.jar to modpack.jar.zip, do the change and rename the file back to modpack.jar. No need to fully extract and recompress it.

It looks like the Nature Reborn mod is coded "poorly". The mod has no config file and seems to be using some API features incorrectly resulting in the crash you see. You will need to remove that mod in order to run a server for your pack.

You are asking for things that google will easily give you links for. If you google: "minecraft forge" you get a link to the Forge downloads. "minecraftforum thaumcraft" you get thaumcraft See? I'm out for a few days starting now. Good luck!

This is a problem I see over and over when folks include OreSpawn mod in their packs. I don't know what's going on with the mod development but you need to bring this up with the mod author(s). There is a conflict with one of the other mods you have included but the crash report is too generic to tell which one. That being said, here's some info on your pack: Your modpack.jar is Forge for 1.6.4 #953. You need to update to Forge for 1.6.4 #965. Your bin folder has a lot of extra, unneeded stuff. It should only contain the modpack.jar which is simply the Forge universal jar file renamed to modpack.jar. IDFixMinus is intended to be used to resolve conflicts. It should never be distributed as part of a working modpack. Fix any ID conflicts and then remove the mod before creating the modpack archive. You have item ID conflicts between: TerraMine & NatureReborn, TerraMine & DragonCraft, OreSpawn & CraftHeraldry, RailCraft & HEE, Carpenter's Blocks & UsefulFood, CyanSwords & HEE, CyanSwords & Mystcraft, NetherX & TerraMine This highlights an important point that IDFixMinus is decent, but not perfect. It does a decent job of fixing block ID conflicts. Not so much with item IDs. You need to be examining your ForgeModLoader client log for the word CONFLICT to find all the item ID conflicts. Not all of them can (or should) be resolve, but your configs have so many conflicts that most of the conflicting mods will be rendered unusable. BeerMod has to be removed for now. There is a known problem with the mod, specifically related to MapGenStructureIO. Basically, as soon as a village gets generated during worldgen the game will crash. The mod author is MIA so the only solution is to remove the mod until a fix is provided. You have a number of outdated mods.

Keep in mind that the link you provided is not a direct download. This would be the direct download URL for your pack: https://dl.dropboxusercontent.com/s/hcsnh8482bh6h5l/Modpack.rar As for your pack: Your modpack.jar is named "Modpack.jar". Notice the uppercase "M". It must be "modpack.jar". Your modpack.jar is a RAR format archive. All archives intended for use in/by the platform MUST be in ZIP format only. Your modpack.jar is the Forge installer. The modpack.jar file is just the Forge universal binary jar file renamed to "modpack.jar". Don't extract it. Don't re-compress it. Don't mess with it other than to rename it to modpack.jar. You are missing the file "mods1.6.4WorldCore-universal-1.6.4-1.1.0.17.jar". Get it here: http://files.minecraftforge.net/WorldCore/ Your EnderStorage mod is out of date compared to your CodeChickenCore mod. Get version 1.4.3.6. Your Biomes O' Plenty mod is for Forge/MC 1.7.2. Get the latest 1.6.4 version. You are missing Thaumcraft which is required by ThaumicTinkerer. Get the latest 1.6.4 version (4.1.0g). Your Furniture Mod is extremely out of date. Get the latest 1.6.4 version (3.2.9.2). You have block ID conflicts between Galacticraft (core and moon) and Natura in the default generated configs. This highlights an important point. No pack is complete without a full set of config files in the config folder. If the default configs have conflicting block IDs a pack will never work unless the conflicts are resolved and the configs included in the pack. However, there are many things that can and should be tweaked to make the mods work well with each other (TreeCapitator, microblocks, power generation, ore balance, mobs, etc.) Making these changes allowed me to start your pack successfully.

I added your (bare Forge) pack to my launcher and it started just fine.

Going to be up to the author to fix that. The link the pack used for the download location has been nixed by copy.com.

Item ID conflicts between: Pam's HarvestCraft & PortalGun You have Tropicraft installed incorrectly. Open the Tropicraft zip file you have and follow the instructions. You have a file named "ModLoader.jar" in your mods folder. Not sure what this is supposed to be (hopefully not ModLoader, that would be bad) but it doesn't belong. Remove it. Pretty sure "threadedlightning.jar" isn't for 1.6.4, and you probably don't need it even if it is. Remove it. Making these changes allowed me to start your pack successfully.

Your pack is set to MC 1.6.4 but you have included Forge 1.7.2 as your modpack.jar. You need to switch over to Forge 1.6.4 build 965 since all your mods are for 1.6.4. You have item ID conflicts between: Metallurgy & Better Storage, Railcraft & HEE

Crash report please.

The version for 1.6.4 is Alpha state. This means that a lot of stuff isn't finished/implemented and one should expect major bugs and changes before Beta or release.

Item IDs in game are usually up-shifted by 256. What you are seeing is that SG is overwriting RailCraft's item ID so you don't see RC's at all. You need to fix the conflicts.

Don't use Java 8. Use Java 7. For whatever reason the launcher is allocating VERY little RAM: Memory: 57892576 bytes (55 MB) / 482344960 bytes (460 MB) up to 482344960 bytes (460 MB) Gotta figure out what's up with that.

Look in your ForgeModLoader client log towards the end of the file. You will see errors directly referencing the mods and block ID in question. Change to an unused ID (<=4095). You can find unused IDs by disabling the conflicting mod(s) and starting the pack. Use NEI to dump a full list of used/unused IDs and then start enabling mods one at a time and fixing the conflicts that pop up by referencing the list of IDs previously dumped.

No, no. Remove the config in your %APPDATA%.technicmodpacksblahblahblahconfig folder, start the pack, THEN re-package the modpack archive and upload it. Always, always get ALL the bugs worked out before uploading a new one.

http://ci.micdoodle8.com/job/Galacticraft/changes