plowmanplow

Mekanism: http://ci.aidancbrady.com:8080/job/Mekanism/ Ender IO: http://ci.tterrag.com/job/EnderIO/ Chisel 2: http://coloredlightscore.us.to:8080/job/Chisel-2%20v1.7.10-Dev/ Railcraft: http://minecraft.curseforge.com/mc-mods/51195-railcraft/files

You have the most recent Mekanism, but EnderIO is a number of builds old. Simply Jetpacks is out of date compared to the version of CoFH mods you have. Same with Railcraft. The version of Chisel 2 you have is quite out of date. This may be directly related to your issue.

Which modpack is this?

@enterprise12: The pack doesn't work because it is hot mess. If the new guy makes his own thread I'll get into it with him but the long and short of it is that most of the contents of the /mods/ folder is "bad".

Again, you really just need to be providing the API URL or a link to your pack details page. Without that I can't know how your metadata settings are configured. The pack as it is now seems to be fine.

The current RC versions of CoFH mods have no problems running in Cauldron builds >= #1272. And to answer your next question, no we shall not discuss how or where to obtain them.

Looks like a problem with OpenCCSensors, possibly an error in a config file? Try reverting the config file for that mod back to the version from the TekkitMain pack.

You changed your modpack archive but failed to increment/change the pack version number in the settings. The Launcher is not notified that a new version is available until the pack version number changes. You have NotEnoughItems mod but not the dependency mod CodeChickenCore. Get the latest versions of both from the mod author's website. Your version of LunatriusCore and Schematica do not match. Get the latest LunatriusCore.

This post on creating a server from an existing custom modpack may help you: Client only mods in this pack (as of 20150308 17:15:00EST): (tested with both Forge and Cauldron #1307 servers) ArmorStatusHUD DamageIndicators StatusEffectHUD BackTools TiCTooltips WailaHarvestability Mods which should be removed (both client and server): LegacyJavaFixer: This mod is not needed with versions of Forge for MC >= 1.7.10 #1230. Making the above modifications allowed me to launch the client and connect to a server for the pack.

Your modpack.jar is named "modpack.jar.jar". Google "windows explorer always show file extensions" for detailed information on how to prevent this type of error. Your modpack settings have the pack configured to be 1.8.1 instead of 1.8 which is required to use Forge for 1.8. You will need to use a version of Forge for 1.8 with an updated version.json file in order to get it working in the Launcher. The easiest way to do this is to get the Forge 1.8 modpack.jar I use in my BareBonesPack: http://solder.circlecraft.info/mods/minecraft-forge/minecraft-forge-1.8_11.14.1.1336p.zip

You can provide the servers.dat file in the modpack. However, this will overwrite anything the user adds themselves. It's best to just list the server on your pack details/info pages.

@Glowguy: Your issue is not even remotely related (they never are). Please start a new thread.

I would highly recommend using 1.7.10 instead of 1.6.4. The modpack.jar is the Forge universal JAR for your selected version of MC.

You most likely have the required folder (bin, config, mods) in a subfolder. However, since you haven't provided the API URL or pack details page link I cannot be more specific.

Client pack: You have two different versions of PlantMegaPack mod one of which is for MC 1.8. Client only mods: Damage Indicators JourneyMap Item of note: Waila is not a client only mod. It has server-side features to control what is displayed on clients.

You should probably update to AE2rv2_beta (along with ExtraCells). You have two copies/versions of CoFHCore, CoFHLib and Redstone Arsenal. Download the latest versions of CoFHCore and Redstone Arsenal and remove your existing versions. You have CoFHLib in your pack. This is only used by mod developers and should never be in a modpack.

You can safely ignore that.

Your /bin/modpack.jar is broken (RAR format archive). The modpack.jar file is simply the Forge universal binary JAR file renamed to modpack.jar. You have a huge mix of 1.6.4 and 1.7.10 mods. This will never work. You need to select a Forge/MC version and get mods for that version only.

Calclavia seems to not give two shiny rat's butts about his mods working together. You will either need to ask in his support channels about which of his mods work together or simply remove them.

Yes, we would need your modpack settings to be pointing at a valid modpack archive. A direct link to the archive can suffice in a pinch if you haven't updated the pack settings.

Always provide the API URL or pack details page link when requesting custom modpack assistance.

Yes, and yes. The developer(s) of Cauldron have moved on to Sponge.

Sure enough, that looks like a chunk corruption. You might try using MCEdit to delete/regen the two chunks listed as being wonky. I say this with the utmost sympathy, but there is never any substitute for good backups. If step #1 is getting the server started, step #2 is implement and verify a good backup solution.

You have the OpenBlocks mod but not the dependency mod OpenModsLib.

You would need to use the Solder API: https://github.com/TechnicPack/TechnicSolder