plowmanplow

The platform takes care of that for you already.

Always include a link to your pack, either the pack page or the pack download. That helps us isolate problems.

Wow. You have some amazingly old mods. Get them all updated to current and we'll try to help if it still doesn't work.

I was able to get a direct download to a file after sharing the file like normal and getting a URL like this: https://copy.com/ryu0zTQTXApw I tacked on the actual file name like so https://copy.com/ryu0zTQTXApw/LoTRCircles64x_Fancy.zip and it allowed me to download the file directly without having to interact on a web page.

The link to your pack download is broken.

Where did you get this pack from? The Flan's page? Is it for the correct version of Flan's?

Your modpack archive is in 7zip format. All files/archives/mods/etc. you wish to use in a pack or with the laucher must be in ZIP format. Your bin folder should only have modpack.jar in it. The rest of the files get installed by the launcher. It is a violation of the Mojang terms of service to distribute the minecraft.jar and it just needlessly bloats your pack. You have a coremods and a "corebods" (mmmm, tasty corebods) folder. Neither are required and should be removed. You have the packs for Flan's mod installed incorrectly. The packs go into a top level folder called "Flan" not inside the mods folder. You have mismatched Flan's mod packs. Your packs are for Flan's v3.0 and you have Flan's v4.1 installed. Update your packs. Highly recommend installing Waila. This provides a great in-game view of what block you are looking at, but most importantly you can do an NEI search for "flan" and it will show all the Flan's mod items. Great for seeing if everything installed correctly.

Don't include unnecessary files in your pack. The "mac specific" files and folders (.DS_Store and __MACOSX for instance) Your modpack.jar seems larger than necessary and it also has Mac specific files in it. Unless you are adding mods into the modpack.jar (almost never needed) you just want to download the Forge universal jar and rename it to modpack.jar. No extraction/recreation necessary. You have an old version of IC2 which has many known bugs/crashes/interaction issues. Build #397 is the latest/last 1.6.4 version and is quite stable. This mod will "fix" the IC2 recipes displaying in NEI that nobody bothered to fix in the mod. Works great and is tiny. You might benefit greatly from the PowerConverters mod. It is current and works well providing a way to convert between the different kinds of power you have in your pack. You have item ID conflicts between Factorization, CalclaviaCore, OreSpawn, ProjectRed, Railcraft and Telepads. You mentioned adding in a shader mod. I don't see one in the pack link you provided or am not recognizing one if it is there. You have your MMMPS recipe files in the mods folder. They go in the configmachinemuserecipes folder.

More information is required: What is the java command line with options you use to start the minecraft/forge server? Is anything else running on the box? What is the average/max/min ping time for at least 50 packets to the server? What is the average/max/min ping time from the server to 8.8.8.8 for at least 50 packets from the server console? How many concurrent players are connected when you experience block lag? What is the server CPU load and disk/network I/O load while experiencing block lag? What is the in-game TPS while experiencing block lag? What is the output of the linux "free" command both while experiencing block lag? How many chunks and entities are loaded while experiencing block lag? I'm sure I could come up with more, but this should be a good start.

Add the shader mod jar file to the "mods" folder in %APPDATA%.technicmodpacksyourpack Start the pack, go to the shader options Copy shader profile file to the appropriate folder for your shader mod Select shader profile

Your modpack.jar file is a RAR archive format file. All files intended for use by the launcher/platform must be in ZIP archive format. Your modpack.jar file is HUGE. Unless you really need to add mods directly into the file (almost never) you just need to get the correct Forge universal file and rename it to "modpack.jar". You have no config files in your pack. Always, always include config files. It is nearly impossible to guarantee you won't have item conflicts, that you won't have mod interaction problems, and that configs are consistent between players in SMP and SSP without including configs.

I would prefer that the link be here. No one is going to get worked up about you posting it here for support regardless of the pack's contents, but if you must then PM me and I'll respond here.

Include links to your pack page and someone should be able to help.

If it just "stops" it is probably creating an error log somewhere. These files might be a good place to start: %APPDATA%.technicmodpacksyourpackForgeModLoader-client-0.log %APPDATA%.technicmodpacksyourpackcrash-reports<most recent file>

There was a period of time during which the IC2 mod did not have any consistent development or bug fixes. Most packs moved on and found replacements as well as other mods picking up the slack. Thermal Expansion 3 and Mekanism 6 both provide similar experiences and development paths as IC2 does. IC2 is still under active development and has quite stable versions for 1.6.4 as well as being one of the first "cornerstone" mods to have publicly available 1.7.x versions. While it is true that it isn't included in the Tekkit packs you can easily find success adding it in yourself or creating a custom pack with it installed. There are also a number of familiar IC2 mods that work well with the 1.6.4 version of the mod such as Nuclear Control, Advanced Machines (you'll want Immibis' version, not Atomic Stryker's), Advanced Solars just to name a few.

I hear copy.com is decent.

More information would be helpful. Is this a pack you have been using and are now adding one or more mods? Have you never run the pack successfully? If it is the former, is CalclaviaCore or Galacticraft a new mod? If one of them is new, you'll want to change the block with ID 3972 in that mod's config so that you don't mess up existing worlds. If it is the latter, just change one config, won't matter which.

Assuming you are using a 1.6.4 pack, the last version of IC2 Experimental that works is build #397. You are on build #140. Update and try again.

I assume that is a laptop? Laptop video hardware is notoriously poor performing, especially with Minecraft. What kind of framerate do you get with vanilla MC?

Glad that worked. Don't forget about that ID conflict though. It'll bite you in the butt if you don't fix it.

No worries, I was just poking in a good-natured way.

Thankfully, even though it isn't in TekkitMain, Mekanism has filled many of the gaps left by the departure of IC2 in many packs. While I agree that TE is a thing of precision and beauty, going through the huge update to the current version and not including some way to "upgrade" machines to make them faster is just disappointing. Mekanism addresses that. Also, for anyone who wants to add IC2 to their packs, there are very stable, feature complete (as much as any mod is feature complete) versions available for 1.6.4 that integrate quite well with most mods. Many well known mods are even keeping up to date with the IC2 Experimental branch API. Yes, there are a ton of changes, but many of them are pretty fun. Most my users very much enjoy the "current" IC2.

Your modpack.zip is actually a RAR format archive even though it has a .ZIP extension. All archives you wish to have Forge/MC/Java use must be in ZIP format. Your modpack.jar file is not the size I would expect. If it work, then great. Just something I noticed. You have some item ID conflicts. Specifically between Factorization's battery and something from CalclaviaCore. Other than that it seems to start and run.

Are the other two GC mods in? Don't see them in the list (unless I'm just way too sleepy and missing it)

Lots of folks are gravitating towards copy.com. Not used it myself, but it is supposedly nice.