plowmanplow

What is "Keephunger on death" set to in your TinkersConstruct.cfg. If that is set to true you'll see some odd things when you switch dimensions.

I am not familiar with Ge.tt as a file host. Please provide a public share URL for your file so we can take a look. If the link is not "direct" (i.e. it doesn't do anything but pop up a save file dialog when clicked in the browser) it won't work in the platform. Also, please provide a link to your Technic pack page or API URL (the URL you add to the launcher).

I mean build your pack to the best of your ability (yes, including config files), upload it to your public file host and update your pack settings to reference the changes.

The error you posted often occurs when your platform pack settings have the MC version set to one thing but the modpack.jar is a different version (i.e. settings are set to 1.7.2 but modpack.jar is Forge 1.6.4). This is why you should provide a link to your platform page or API URL when requesting assistance. Forge/MC 1.6+ (your pack is 1.6.4) does not use a coremods folder in any way. All mods belong in or below the mods folder. You have the Mekanism MDK (development kit). This does not belong in a client pack and should be removed. The MMMPS recipe files belong in configmachinemuserecipes not mods. Some of your mods have odd names (i.e. Waila. Don't rename the files which are downloaded from authors. Only get mods directly from the author's preferred distribution channels. You have the Forge universal binary JAR in your mods folder. This should be removed. You are missing your config files. This is always bad. Read through my guide on using the BareBonesPack to build a modpack for additional details on where config files come from and how to assemble your pack.

You are using an absolutely ancient version of MCPC+. You need to install (not drop in the JAR, actually run the installer) the latest version of Cauldron (formerly known as MCPC+) to your server and run that. http://cauldron.minecraftforge.net/

You need to update your Java. You are on Java 7_25. The latest version is 7_67 and there are some mods which require at least 7_45. The symptoms you describe are exactly what happens when you start vanilla MC instead of Forge (or Cauldron). Somehow, even if not intentional, you are not starting the correct server JAR.

I know that Tinker's Construct has some "hard mode" stuff related to hunger. Other mods as well. What's in your pack?

This may help you get a little closer to your goal:

If you update your modpack settings with the new/updated pack I'll take a look.

Keep in mind that the IDConflicts.txt file does not get created unless the game detects conflicts at a particular stage in the initialization process. The ForgeModLoader-client-0.log file is always up to date.

You need to be including the config folder and all its contents in your modpack archive ZIP once you get all the conflicts resolved.

You have no config files in your modpack archive. This is always bad. Read through this post for details about configs and how you get them: You have a mishmash of mods for both 1.7.10 and 1.6.4, many of which are duplicates. Pick a Forge/MC version and build your pack for that. You have duplicate Tinker's Construct mod files. You have a giant 132meg file called "Factions' End.zip" in your mods folder. This obviously does not belong and needs to be removed. You should update your ForgeMultipart to the latest version for 1.6.4. Fix these problems and come back if you are still having issues.

Well, that would surely disable it. You can also (more easily) change the extension to ".disable".

You need to be searching through these logs for things like this around the error: 2014-08-20 12:48:57 [SEVERE] [ForgeModLoader] Caught exception from B0bGrowsOre java.lang.ArrayIndexOutOfBoundsException: 4096 This states that you have set a block ID in the B0bGrowsOre config file to 4096, which is an invalid ID for a block. They must be <= 4095.

I believe some punctuation might make that very long sentence more understandable. Can you provide more specifics? What mods do you think need to go into the modpack.jar file?

java.lang.ArrayIndexOutOfBoundsException: 4096 It looks like you have set a block ID to >=4096. I've mentioned a few places that block IDs must be <=4095. You'll need to check your ForgeModLoader-client-0.log file in order to better determine which mod has the issue.

Please don't PM me when we have an ongoing thread for your modpack. It makes it very difficult to keep track of what is going on with the dozens of active requests. Your current crash report: http://pastebin.com/yt0Jgdz7 CONFLICT: Potion IDs: am2.buffs.ArsMagicaPotion@3cd0546e @ 35 Look through this guide: The process for resolving potion ID conflicts is the same as for items. Disable AM2 temporarily, dump the potion IDs, change AM2 potions IDs to unused values, re-enable AM2.

You would be better off dropping ForgeEssentials and switching to using Cauldron (or MCPC+ if you are trying to use the 1.5.2 version of Hexxit) which allows you to use Bukkit plugins.

Make sure you are updating the version number in your pack settings. Make sure you are updating the URL for the modpack ZIP file if it has chnaged. Make sure you are restarting the Launcher. It is only notified of new pack versions at startup.

2014-08-19 21:33:07 [SEVERE] [ForgeModLoader] Caught exception from B0bGrowsOre [B#439] java.lang.IllegalArgumentException: Slot 4049 is already occupied by CakeIsALie.common.BlockEnderCake@30002876 when adding mods.B0bGary.GrowOres.BlockOreReed@28319836 You can change either EnderCake in CakeIsALie mod config or Reed in B0bGrowsOre mod config from 4049 to one of the IDs listed as open in the ranges from your previous IDConflicts.txt file. An alternative would be to disable one of those mods and launch the client. Assuming it starts you can dump a CSV file of all the used/unused IDs and then change the 4096 in one of the above mods to something unused in the CSV file (but below 4095) then re-enable the disabled mod.

Or you could actually be helpful and contribute to the community by posting your information here where it might be useful (and indexed).

Try using my BareBonesPack. Here's a guide:

Let's examine some details from the IDConflicts.txt file you posted: 480: centrifuge from CloneCraft - vilewoodSlabDouble from NetherX Suggested Ranges: 976-1439 (464 IDs), 3385-3845 (461 IDs), 1532-1889 (358 IDs) The first line says that both CloneCraft and NetherX have a block set to use ID #480. The second line lists a few ranges of IDs which are free and can be assigned in the configs of one of the conflicting mods. In this case we can change "I:CENTRIFUGE_ID" in CloneCraft.cfg from 480 to 980 since that ID is in the "Suggested Ranges". This would resolve one of the conflicts. You would need to do the same thing for the rest of them. However, since your modpack still has no config files, it won't matter what you fix because folks who add/download your pack will never see the changes you make. In your case it is safe to say that if you don't include a full compliment of config files in your modpack archive that it will never be usable.

I would expect to see an issue like that when one of your mods or libraries does not match your Forge/MC version. Please provide a link to your Technic Platform page or your API URL.

You need to uncheck the box in your pack settings page that is labeled "Force Directory Change". If I add your API URL to my launcher I am able to successfully start the pack.