plowmanplow

It looks like you are either missing a dependency mod or a dependency mod and its dependents are out of date/mismatched. Since the modpack archive referenced in your pack settings no longer exists I cannot provide any more details.

Always provide the API URL or a link to your pack details page. Edit: I assume this is your pack? http://technicpack.net/modpack/giga-mix.605938 Your modpack contains Forge 1.7.10 but the pack settings are configured for MC 1.8.1. You need to change the pack settings to 1.7.10.

Creating a server from a custom modpack:

This post belongs in Platform Pagoda. Hopefully an industrious moderator will move it. You need to add Lexmanos' legacy java fixer to your pack: http://www.technicpack.net/article/attention-modpack-authors.105 Also, always provide the API URL or a link to the pack details page when requesting help. I'll assume this is your pack: http://www.technicpack.net/modpack/fart-adventures-modpack.579733

There are a couple ways to do this. Disable copper ore generation in all but one of the mods (if possible) and increase the generation amount in the remaining mod (if possible and desired). Disable all copper ore generation (if possible) and use ThermalFoundation to do all ore generation.

The contents of your startserver.bat should be: @echo off java -Xms2048m -Xmx2048m -jar forge-1.7.10-10.13.2.1291-universal.jar nogui I corrected the post of mine where you likely got your incorrect batch file contents. My bad.

Updated 1.7.10 to #1307 "Recommended". Updated 1.8 to #1333p "Latest".

Your TeamCoFH mods are mismatched. Get the latest release versions for each of the mods you are using at their website: http://www.teamcofh.com/downloads/ Might as well update Botania, BuildCraft, NEI Integration, NEI, Thaumcraft and Twilight Forest while you are at it. You are still using "bad" versions of iChun's mods. http://ichun.us/ You are still using "bad" versions of IC2: http://ic2api.player.to:8080/job/IC2_experimental/ You are still using "bad" versions of OpenMods: http://openmods.info:8080/

Yes. There is no connection between them in any way. They are completely separate programs with completely separate folder structures for storing data. They have no impact on each other in any way.

Your server progress is stored on the server. You could even go to a different computer and log into the server and your progress would not be lost.

There is no cross-over between the Technic Launcher and the Vanilla Launcher. Nothing you do locally will affect your progress on servers, however, you will need to make sure your mod versions match whatever servers you are trying to use.

The current modpack archive for your pack contains duplicates of the listed mods.

You have incremented the pack version number but not changed the modpack archive. I cannot diagnose something I cannot examine.

What have you changed? I noticed that you did increment the pack version number from 1.0 to 1.1. However, the contents did not change so all of my previous comments still stand.

I can assure you that would not save any time for me.

Yes, the current version of Tekkit is for Forge/MC 1.6.4. All of the mods have been tested to work with each other. As soon as you start adding mods you will likely need to update many of the existing mods. Think of the current Tekkit as "a moment in time". If you add a mods from a later point in time you will probably need to update all the other mods to that same "moment".

Discussing how to obtain Bukkit or its derivatives is not permitted on these forums.

Think "rate of change". Possibly first or second order derivative. I don't know if they are making it that complex, but in the end it's largely a factor of "how fast are the numbers changing".

I believe you are mistaking blunt/direct for rudeness. Being rude would imply that I am being dismissive or condescending, yet I have only ever stated cold hard facts. When I provide precise or specific information on how to address an issue and that information is disregarded I try to be a little more blunt/direct since there must have been a communication issue of some sort the first time around. Case in point: The 1.2 (current) version of your modpack still has the wrong version of IC2 Nuclear Control. I understand that you are having troubles with getting the server up and running. However, the first step in getting a stable, reliable server is to have a stable, reliable client modpack. A significant portion of having a stable and reliable client modpack is having the correct, matching versions of mods. Until you have that it is not prudent or productive to try to get a server working. I count at least 25 mods which are at least a few versions old. Some of those are nearly 100 build versions old (i.e. Logistics Pipes should be build #294). I am not saying this to be critical, this is just the current state of the pack.

Specifically, please provide the API URL (the URL you paste into the Launcher) and the download URL you are trying to set in your pack settings page.

Mods with odd names: For instance, you have the Hats mod which is named "Hats-Mod-1.7.10.jar" (and if you look inside the mod JAR it is an old version). The author provides that mod with the version number in the name "Hats-4.0.1.jar". You are either renaming the mods (bad, but unlikely) or you aren't getting the mods from the authors (very bad). Any time you change the modpack archive simply increment the pack version number on the settings page. It appears as though you have done this as the version number is now 1.1, but the pack archive itself hasn't changed. Just make sure you increment it every time you change the pack.

You do realize there is a way to edit your posts, right?

I know I've mentioned this before, but you are updating your modpack archive but not the pack version number. This is bad and will cause problems for anyone using your pack. Always update/increment the pack version number when you change your modpack archive. Every time. No exceptions. Your pack has two different versions of AE2, Biomes O' Plenty, BuildCraft, CoFHCore, Extra Utilities, Mekanism, and Thermal Expansion. You are still using mods with odd names. The implication (as I mentioned before) is that you aren't getting them directly from the authors. This will result in you using out of date or mismatched mods.

We'll need the API URL (as usual) in order to proceed.

Looks like you maybe got a 1.8 version of one of the mods you updated.