plowmanplow

Looks like mismatched Calclavia mods. Make sure you get the current/matching/working versions from his website(s).

No, you did not: Java is Java HotSpot™ 64-Bit Server VM, version 1.7.0_67 The latest version of Java 7 is u71/u72. Yes, u67 would probably work fine, but the fact that you aren't properly downloading/installing the correct version of Java makes me suspicious of your methods.

Don't use Java 8. Use the latest version of Java 7 for your platform.

Creating a server for your modpack is not extremely difficult, there are a just a few things which need to be done in the correct order to be successful. Building/assembling the pack itself consists of a few steps: Setup test environment: You can do this yourself or you can use my BareBonesPack which makes things super easy. Simply add this modpack to your launcher and edit the settings to select your preferred version of MC (I highly recommend 1.7.10). http://www.technicpack.net/modpack/details/barebonespack.271497 Download mods: Getting the mods is often the most time consuming part of the process, depending on which ones you want. Creating a fun, balanced modpack can be challenging and your selection of mods is the primary focal point. This link should help you find the correct downloads for mods: http://forums.technicpack.net/topic/62513-new-to-technic-what-now/#comment-508175 Build process: It is crucial to build the pack carefully and methodically if you wish to maintain your sanity. This post explains my recommended process for using my BareBonesPack to create a modpack: http://forums.technicpack.net/topic/62318-minecraft-keeps-crashing/#comment-506458 Assembly process: The previous link has some details for how to assemble the modpack archive once you have the test environment where you want it. Modpack hosting: Your modpack archive will need to be posted somewhere public which provides direct download links. I highly recommend http://copy.com/ as your file host. Register for an account (if you want to get some more space for you and me you can use this referral link: https://copy.com?r=cZHpBn ) and upload your completed modpack archive. Sharing the file will yield a public share URL to which you will append "?download=1" (without quotes) when configuring your modpack settings. Technic Platform: Register for a platform account so you can create and maintain your pack. Their front page has information on how to register and create your modpack page. Once you get a working client modpack we can proceed with creating a server. The creation of the server itself is rather trivial, but folks often want the ability to use plugins to enrich the play experience (requires the use of Cauldron which I can also help with... Cauldron is no longer publicly available due to DMCA insanity). You may also need to make some changes to your network depending on where/how you intend to host the server. We'll cross that bridge when we get there.

Please do not link to a website which is stealing content from the creators. Sphax is available (along with patches for mods) from http://bdcraft.net/

Updated 1.7.10 to 10.13.2.1236 Removed very old 1.7.10 versions

I'm not sure what to tell you. The pack works fine when added to my launcher. I suspect that your Java installation is suspect, especially since you seem to have gone from a current Java 1.8 to an outdated Java 1.7. Uninstall anything in your installed programs list related to Java and install the latest Java 7 JRE for your platform.

Come back here if you still have problems after switching to the latest version of Java 7 for your platform instead of Java 8: Java is Java HotSpot™ 64-Bit Server VM, version 1.8.0_25 If you do come back, please provide the API URL for your modpack.

Solder is built using the Laravel PHP framework. That might be a good place to start.

No, you did not. The current version for 1.6.4 from the author's website is "CodeChickenCore-1.6.4-0.9.0.9-universal.jar".

I guess I'm not sure what isn't working. I copied your Flan and mods folders into an instance of my and it worked just fine.

Your modpack download URL in your pack settings is not a direct link. For copy.com links "?download=1" must be added to any public share URL to make it a direct link. Like this: https://copy.com/dZcDxgVjNS8783zs?download=1 Your modpack archive has too much stuff in it. It should only contain three folders: bin, config, and mods. The bin folder should only contain the modpack.jar file. Some of your mods are out of date (well, at least CodeChickenCore). Updating this will fix your NEI crash. Other than that the pack starts for me.

If the list of things you checked are indeed correct then the textures will work fine. However, since it's not working I suspect one of those items is not configured correctly. Please provide links to your custom modpack and the texture pack archive.

Problems like these belong in the Tracker for the pack in question, or the Launcher in general. Links are at the top of this page.

Because of the extensive interdependency of Calclavia's mods it is fairly easy to get API conflicts between his mods and others which use his API. Make sure you are using the latest versions of Calclavia's mods and any mods which depend on them. Update Galacticraft to the latest version as well. You are using an absolutely ancient version of Java (1.7.0_11). Update to the latest 1.7 version for your platform (1.7.0_71/72)

nickrcole: Close, but it's not that difficult. A combination of BanItem and ModifyWorld/PermissionsEX(Pex) will allow you to restrict certain blocks/items to specific ranks. Pex will stop checking for permissions nodes when it finds a match. This makes the order of the listed perm nodes in the config file important, but also makes it easier to restrict only some blocks/items. Place a node at the end of the perm list for a rank: groups: Player: permissions: - modifyworld.* Then, above that you would negate any items/blocks you wanted to restrict: groups: Player: permissions: - -modifyworld.blocks.place.250:15 - modifyworld.* You can even restrict something like a quarry to only be usable in certain worlds: groups: Player: worlds: DIM_MYST5: permissions: - modifyworld.blocks.place.250:15 permissions: - -modifyworld.blocks.place.250:15 - modifyworld.*

Making a server from an existing modpack:

Making a server from a modpack:

For Forge/MC <= 1.6.4 this post should help: '?do=embed' frameborder='0' data-embedContent>> For Forge/MC > 1.6.4 you simply place the LiteLoader JAR file into the mods1.7.10 or mods1.7.2 folder.

When requesting help for a custom modpack always include the API URL. There is insufficient information in a plain crash report to diagnose the issue.

The contents of your modpack archive are in a subfolder. The required folders (bin, config, mods) must be at the top level of the folder structure inside the modpack archive. You are using the correct version of Forge as your modpack.jar file. You are using some woefully outdated mod versions in your pack. All your CoFH mods and ProjectRed stand out as examples. You have the 1.6.2 version of Buildcraft. You need to be using the latest version of Buildcraft for Forge/MC 1.6.4 (1.6.4-4.2.2) Some of your mods (ChickenChunks for example) are named oddly. The implication is that you did not get them from the mod author's preferred distribution channels. You have no config files in your modpack archive. This is bad and often fatal for Forge/MC <=1.6.4. This post on getting mods may help you: This post on using my BareBonesPack to build your modpack has information about config files:

Does this happen with Vanilla? Are your video card drivers up to date? Have you tried beta drivers? Does the memory usage growth seem to be independent of which 1.7.10 modpack you are using?

Yes, anyone who wants OptiFine needs to have it locally installed. Whether that comes from your custom modpack or by manually installing is up to you.

Your binmodpack.jar is malformed. The modpack.jar file is simply the Forge universal binary JAR file for your version of MC renamed to modpack.jar. Forge for MC >=1.6 does not use a coremods folder in any way. All mods go in or below the mods folder. The modpack download URL you provided is not a direct link. In order for download links to work correctly in the platform they must be direct. copy.com public share links can be made direct by appending "?download=1" (without quotes) to the URL. Fix these issues and come back if you still have problems. If you do need to come back, please provide the API URL for your modpack instead of a file download URL.

Yes, the crash report just lists what the exception was. The FML log will show you what was going on at the time of the crash and give you relevant information such as which mod was missing which dependency.