plowmanplow

I don't think you are quite following me. The SERVER doesn't care if the CLIENT has OptiFine installed. Having OptiFine on the client does nothing to/for the server and so the client can have it installed while playing and that is what you are seeing. If you watched a YouTube video of the server it would be a very boring scrolling of text up the screen. What you are seeing is a person who has installed OptiFine (or smart moving, or shaders, etc.) on their client into an existing modpack and then connected to the server normally.

Mods on a server can be completely disabled by either removing the mod from the mods folder or by renaming it to have the extension ".disabled" (without quotes).

It looks like the text of the link might be correct, but because of the way the forum shortens link displays all I can get is the dropbox download link out of that. Please provide the API URL. Tropicraft is not installed properly. Open the ZIP file and follow the mod author's instructions. You are missing Universal Electricity Core mod. Resonant Engine mod has a potion ID problem. Change the potion IDs in the Resonant Engine config file to 26, 27 and 28. There is a block ID conflict between ExtraBiomesXL and Thaumcraft for ID #2400.

The link you provided is not what I requested. Yes, it seems to be a modpack download, but there are many issues that can arise from improper settings and if you provide the API URL you only have to post it once. That being said, the link you provided does not work.

cpw.mods.fml.common.MissingModsException You are missing a mod dependency. Check your latest Forge log in the logs folder.

Client only mods are those which only change the way things are displayed or rendered on the client. They are mods which do not modify the data going between the client and server. As such, they all need to be removed since the server does not have the client render code included. In your case, OptiFine is only ever used on the client. You can safely use it on your client even though it isn't (and can't be) installed on the server. This would go for any other client only mods such as DamageIndicators, ArmorStatusHUD, DynamicLights, etc.

Your current modpack still has the old version of NotEnoughCodecs. You need to be updating the modpack (including incrementing the version number) in order for us to be testing it. You have a 1.7.2 version of MapWriter mod. I'm not sure if there is a 1.7.10 version available, but the 1.7.2 version won't work in 1.7.10. Numina doesn't like something else in the pack. Not sure if it is just Forge or another mod, but it can (and should) be safely removed since nothing in the pack is using it.

You have an ancient version of Java 7. Update to the latest Java 7 for your OS/platform. Always provide a link to your details page or API URL when requesting assistance for a custom modpack.

When I try to access the API URL for your Solder installation ( http://thisischrys.zapto.org/TechnicSolder/public/api/ ) it doesn't work. Your Solder API URL should return something like this: {"api":"TechnicSolder","version":"0.6","stream":"DEV"}

When I switch to the correct version of NotEnoughCodecs, and use Forge #1231, the pack starts as expected: http://openmods.info:8080/job/NotEnoughCodecs/lastSuccessfulBuild/artifact/build/libs/NotEnoughCodecs-1.7.10-0.3-snapshot-11.jar

If this is a crash with Tekkit (or one of the other Technic packs) this probably belongs in the Tracker for that pack. If this is a custom modpack, please provide a link to the details page or the API URL for the pack.

We will be unable to help without a link to your pack details page or the API URL. An anecdotal list of what is in the pack serves little purpose.

Try using the latest version of Java 7 instead of Java 8_20: http://www.technicpack.net/article/view/concurrentmodificationexception-in-java-18020.89 If that doesn't help you then come back for more.

Client: Your modpack download URL is not direct. copy.com public share links need "?download=1" (without quotes) appended to the URL. You have no config files in your modpack archive. This is always bad. Config files allow you to tweak configurations of mods and to balance mods against each other. Including a full compliment of config files is not optional, especially when intending to use the modpack with a server. CoFHLib is not required and should be removed. Mods removed for the server: ArmorStatusHUD AdvancedHUD DynamicLights LiteLoader voxelMap.litemod OptiFine WailaHarvestability SouldShardsAlpha - This mod should work in SMP, but it doesn't. It is improperly implementing the client/server API and failing to start on the server. AromaBackup - Not sure if this mod is supposed to be SMP or not, but it is throwing a massive number of ConcurrentModificationExceptions. With these changes I was able to create a local server and join with the customized client.

Forge for MC 1.6+ does not use a coremods folder in any way. All mods go in or below the mods folder.

You could use MCEdit to remove it.

That's because you still have the contents in a subfolder.

Yes, it will start without having configs since you only have one mod which adds blocks.

The contents of your modpack archive are inside a subfolder. The required folders (bin, config, mods) must be at the top level of the folder structure inside the modpack archive. Your modpack is set to be MC 1.7.10, but your Forge version and mods are for 1.6.4. You have an ancient version of Forge as your modpack.jar. Get the latest 1.6.4 version of Forge (#965). You have two .class files in your mods folder. These should be removed. You have mods in the coremods folder. Starting with Forge for MC 1.6+ the coremods folder is unused. All mod go in or below the mods folder. Your modpack has no config files. This is always bad. Since your pack has few mods which add blocks/items you can get away without config files, but a full compliment of config files is a requirement in all cases.

If the pack doesn't start when the mods are installed correctly (i.e. not unzipped) you need to examine your ForgeModLoader-client-0.log file for the cause of the problem. I downloaded the latest 1.6.4 versions of the mods you had unzipped and tried to start the pack. There was an ID conflict between GeoStrata and RivalRebels. This post on ID conflict resolution may help you: . The catch here will be that you must change the IDs in the GeoStrata config file (change the IDs from 100xx to 99xx) because RivalRebels just overwrites anything you change with the default value (lame). After making these changes the pack starts just fine and I was able to place modded blocks in SSP.

There is no 1.7.2 version of Mekanism. It went directly from 1.6.4 to 1.7.10. If you are building a modpack now, building it for 1.7.10 is almost always the right way to go.

Great. That's the idea. I always try to keep the Forge/MC versions in parallel to the versions of Cauldron/MCPC+ available.

Building a modpack is a process. There are multiple steps to the process which can help preserve one's sanity. I would recommend using something like my BareBonesPack ( ) to test and assemble your modpack.

Please provide the API URL for the pack.

Mods which generate their own folder structure and contents should be allowed to do so on the client instead of in the pack, provided that none of the content inside that structure has editable features. The hats mod, for example, makes a hats folder which can safely be excluded from the modpack provided no additional content is added outside of the default configuration.