plowmanplow

Wherever you saved it. When you download the Launcher for your OS you are downloading the executable. There is no "installer".

This post about creating a server from an existing modpack may help you: http://forums.technicpack.net/topic/61989-server-of-fury-i-would-like-more-help/#comment-519381

I really don't want to take over this thread. Please post issues/discussion in the pack's Potluck thread: http://forums.technicpack.net/topic/126415-1710-a-teams-revenge/

Always provide the API URL or a link to the pack details page when requesting custom modpack assistance. Please use a pastebin service (like http://pastebin.com ) to post logs. The attachments in the forums aren't working.

Please provide the API URL or a link to the pack details page for your custom modpack.

Your modpack archive is in RAR format. All archive files intended for use in the platform must be in ZIP format only. bspkrsCore belongs in /mods/1.7.10/. ForgeMultipart belongs in /mods/1.7.10/. You should be using the latest beta of AE2rv2. The older versions are not compatible with most current mods. You should be using at lest the Buildcraft 6.4.x branch. All of the CoFH mods need to be updated. Your Galacticraft is very out of date. You need both ICBM and VoltzEngine from the new maintainers, BuiltBroken. iChunUtil, InventoryTweaks, Lucky Block, Simply Jetpacks, Steve's Carts, Trailmix, Waila are all from illegitimate sources. Get them from the mod authors. NEI is fatally out of date. I've already mentioned this: You have at least one mod with (1), (2), etc. in the file name. This is caused by downloading a file with an existing name to a folder. All the file names need to be fixed by removing the extra space, parenthesis and numbers. Failing to do so can cause issues with mods. Your ProjectRed mod is out of date.

java.lang.OutOfMemoryError: Registering texture Allocate more memory to the launcher (Launcher Settings).

I have no idea what you just said. In order for us to provide assistance we will need you to provide the API URL or the details link of your pack.

Always provide the API URL or a link to your pack details page when requesting assistance.

This may help: http://forums.technicpack.net/topic/103596-still-looking-for-help-building-custom-modpack/#comment-571785

From looking at the filename it appears as if you have downloaded the Reliquary mod from an illegitimate source. Always download your mods from the author's preferred locations. The crash report states that there is a problem with Reliquary. You need the latest dev version of the mod in order to be compatible with the rest of your mods.

Please use a pastebin service (like http://pastebin.com ) to post your crash report as attachments don't seem to be working. You should remove the string "(1)" (or any other number enclosed by parenthesis) from the filenames of your mods. This can cause issues. You have included the 1.6.4 version of EE3. There is a 1.7.10 version available, but it is basically non-functional at the moment and should probably be removed from your pack. Until Calclavia completes his internal migration to his own Nova Core you should consider all of his mods non-functional and they should be removed from your pack (MFFS, Resonant Engin, Resonant Induction). I'm not sure where you got your Quarry Plus mod, but it seems to have a problem. Get the newest version from the authors MCF thread. Buildcraft Schematic Mod (BSM) is not compatible with the current 6.4.x releases of Buildcraft. You will need to remove BSM. I would recommend adding Buildcraft's own BuildcraftCompatibility mod. Your Minions mod is not installed properly. Open the ZIP archive and follow the mod author's instructions. Your MineTweaker mod is fatally out of date. In a general sense, your crash was happening because you simply tossed well over 100 mods into a folder and tried to start the client. Many mods require specific versions of dependency libraries or are only compatible with specific versions of other mods. You would get much more clear information if you build the pack methodically so you know exactly what is causing problems as you go.

OreSpawn does something "weird" with mob/entity spawning and often ends up in conflict with some other mod and causing this exact issue. You may get some traction going directly to the author's website, but your only real alternative is to remove OreSpawn.

At a minimum, you have added an ancient, incompatible version of Applied Energistics. You need to be using the latest AE2rv2.

The /mods/am2/ folder should be removed. You have the Forge/MC 1.6.4 version of Binnie Mods. Get the 1.7.10 version. Your Biomes O' Plenty mod is very outdated. Address these issues and come back if you still have troubles.

Is your pack having some particular problem at the moment? If so, please clearly state what issues you are having.

<shakes Magic 8-Ball> Because potato. In all seriousness, please provide your API URL or a link to your pack details page. otherwise, anything we suggest will just be a guess.

Your modpack location URL is incorrect. Copy.com links must be appended with "?download=1" (without quotes) to make them work properly. Your Logistics Pipes is out of date. You are on #246. The latest/last 1.6.4 version was #294. Why would you update Galacticraft and not use the latest/last 1.6.4 version? You have #1084. The latest/last Galacticraft is #1098 Address these issues and come back if you still have troubles.

This may help you: http://forums.technicpack.net/topic/61989-server-of-fury-i-would-like-more-help/#comment-519381

Every time you change your modpack archive you need to change the version number in the pack settings page. The Launcher is only notified that a new version is available when this number is incremented/changed. You have removed the version numbers from the file names of every mod in your pack. Why have you done this. It makes it basically impossible to support you and keeping the pack up to date (or just updating it) would be a nightmare. I'm not even going to try running the pack in my test environment. You are going to need to re-download all the mods in your pack and leave the filenames/version numbers intact. Once you have done that, if you are still having problems feel free to come back here.

Yes, sorry. That was meant as an example.

If this is your client pack, this thread belongs in Platform Pagoda. If OpenEye is complaining about EnderIO, and the crash-report is complaining about EnderIO, and the FML latest log specifically calls out EnderIO... it might be EnderIO. An upgrade wouldn't be out of order. However, it also could be caused by an API mismatch. Dropping in a ton of extra mods at once is usually a recipe for disaster. Add them one at a time so you can figure out where the conflict is coming from.

Did you remove one or more mods? Looks that way.

This sounds like an API mismatch issue. Galacticraft includes support for other mods, specifically Mekanism and Ender IO. You need to ensure you are using versions with compatible support.

The only thing I can guess is that you aren't properly incrementing/changing your version number in the pack settings page. I'm able to add your pack and run it successfully.