plowmanplow

Indeed, it does. The list from your OP is a VERY long list of plugins. Time to start adding them one at a time until it stops working.

Not to my knowledge, no.

The Tracker links are at the top of every page in these forums.

Since this is for one of the Technic's official packs, requests of this nature belong in the tracker. You are correct that it is indeed a memory issue: java.lang.OutOfMemoryError: Java heap space You have cut off part of the crash report which would be useful in solving the issue (whether the client is using 32bit or 64bit Java, and which version)

Duly noted, and corrected. You learn something new every day.

Your versions of Thaumcraft and Thaumic Tinkerer don't match. Get the latest versions: Thaumcraft: http://www.curse.com/mc-mods/minecraft/223628-thaumcraft#t1:other-downloads Thaumic Tinkerer: http://jenkins.nekokittygames.com:8080/job/Thaumic%20Tinkerer/ Thaumic Exploration: http://jenkins.nekokittygames.com:8080/view/Thaumic%20Explorer/job/Thaumic%20Explorer/

"Hold the most fun" is an opinion not held by most folks I interact with. However, setting up a simple script or web interface to do name changes on an old server would be trivial so this really shouldn't be in an issue.

Forge/MC >= 1.6 does not use a /coremods/ folder in any way. All mods belong in or below the /mods/ folder. Forge for 1.7.10 >= #1230 does not require the use of Lexmanos' LegacyJavaFixer JAR file. This should be removed. Waila and Wawla are woefully out of date. Update to the latest versions: http://www.curse.com/mc-mods/minecraft/waila#t1:other-downloads and http://www.curse.com/mc-mods/minecraft/224712-wawla-what-are-we-looking-at I highly recommend updating to NEI 1.0.4.83 Your pack includes PixelPoints which is only for servers and seems to exist for the sole reason of squeezing money out of children and idiots. This should be removed from your pack. Something is going wrong with GlobalTradeSystem (GTS) mod. The Pixelmon website lists the latest version as being 1.0.5, your version is 1.0.2, and when you download it from Pixelmon you get 1.0.1. This is what is crashing your client.

If you need to send signals that far you would be much better off using Wireless Redstone.

From the crash report: Caused by: java.lang.OutOfMemoryError: Metaspace . . . Operating System: Windows 7 (x86) version 6.1 Java Version: 1.8.0_25, Oracle Corporation Java VM Version: Java HotSpot(TM) Client VM (mixed mode), Oracle Corporation Memory: 381877944 bytes (364 MB) / 880881664 bytes (840 MB) up to 1037959168 bytes (989 MB) The client is running out of memory because either: Windows 7 32bit is installed and will only run 32bit Java. This will limit the memory allocation to a maximum of 1G. Java 32bit is installed on Windows 7 64bit. In this case the user needs to uninstall the existing Java and install the latest 64bit Java 8 then allocate more memory in the Launcher settings.

If none of your packs work then this is a Launcher issue and you should be using the Tracker for the Launcher (link at the top of this page).

Yeah, the current state of mods, and specifically mod interactions, in SMP is a bit sketchy on 1.7.10 because server development has essentially halted. The most recent Cauldron is good, but obviously not perfect. My Tekkit Lite server sees weeks of uptime before I end up restarting it. My less complex 1.7.10 packs (on Forge/MC/Cauldron #1272) seem pretty stable. My big pack seems to have a memory leak somewhere which starts causing issues in the 20-24H mark. No big deal to restart when nobody is on and just something we have to deal with given the current state of things.

If you are having trouble with people using quarries then just restrict their use. On my primary public server I only permit quarry use in a dedicated mining age for this very reason, and only permit landmark quarry expansion to Veteran ranked players since they have proven that they aren't idiots.

Try making sure it's not opped, and have them temporarily do a "/trust [buildCraft]" when they need to use it.

What Forge/MC version? What MCPC+/Cauldron version? Do not /op the BuildCraft fake player. You can minimize the risk by restricting landmark use on lower ranked players or by restricting quarry use.

Yes, those are entertaining as a joke, but really need to just be disabled in the configs.

OptiFine is not compatible with one of your mods. This is not uncommon.

There is some kind of issue going on which I've been unable to resolve yet. I've been going back and forth with the Technic devs in IRC when they are available. This is kind of a "known issue" with no current resolution other than to use a different host ( copy.com works well )

Your pack settings are incorrect. You have the pack set to Forge/MC 1.7.2, but the pack is built for 1.7.10.

Uhh, sure, you can edit that link text in your pack settings. Or, you could paste it into Notepad, edit it, re-copy it and paste that into the platform.

Client Pack: Your modpack is more than twice the size it should be because you are including too much in the archive file. The modpack archive should only contain the folders: /bin/, /config/, /mods/. The /bin/ folder should only contain the file: modpack.jar Client Only Mods: (remove these mods on the server) Better Foliage Custom Main Menu Holo Inventory Thaumcraft NEI Plugin After removing those mods from the server's /mods/ folder I was able to start up a Forge 1.7.10_1272 server and connect with your client with no crashes.

Your modpack download URL needs to end in ?dl=1 instead of ?dl=0 The ZombieCraft mod you are trying to use is: A) Dead and unsupported, B ) Not designed in such a way as to be usable in the Launcher, C) For an ancient version of Forge/MC that no one wants to support anymore.

Always provide the API URL or a link to your custom modpack page when requesting assistance. The /bin/ folder should only contain the file modpack.jar. All mods go in or below the /mods/ folder. Your ChickenBones mods (CodeChickenCore, NEI) are named oddly (not what the author names them). The implication is that you didn't get them from the correct location. Get the latest versions for Forge/MC 1.7.10 here: http://chickenbones.net/Pages/links.html

Assuming this is a 1.7.10 server, you may be able to use some of the server-based Forge mods like WorldEdit, WorldGuard, Forge Essentials, etc.

In my experience (the servers I run), I seem to be seeing better memory management in general when using Java 8. This is anecdotal in nature so I wouldn't take a strong stance just for that, but there are so many compelling reasons to switch to Java 8, and so few not to, that it just makes good sense at this point. There is always a decent amount of HD I/O going on ranging from "some" to "a crapton" (technical term). The system will run MUCH better on an SSD, especially when lots of folks are generating a lot of chunk churn, and when backups hit.