plowmanplow

Please provide a couple API URLs here which we can test and compare with. Where are you pasting the API URLs? Hopefully into the Launcher's search box.

The "best" version of Forge is the one which: Works well with all the mods included in your pack. Works well with your chosen server process. If you intend on using Forge as your server then you will be fine regardless. If you plan on using Cauldron/KCauldron then you would want to use a version of Forge in the client which works well with that server JAR.

My test environment has Java 7 1.7.0_71-b14.

Yeah, if you are getting that error from a "universal" (supposed to work on client and server) mod then the mod was improperly coded. The server doesn't have those methods/classes so will error out if the mod tries to access them.

Permanent Generation space is kind of like internal storage for classes and objects for the Java virtual machine. Java versions less than 8 required increasing the reservation for that memory beyond the default when there were lots of classes and objects (i.e. when there's a lot of mods). Java 8 eliminated permanent generation space and integrated that back into the normal memory allocation so you would be able to simply allocate with -Xmx and -Xms in order to reserve enough RAM.

When requesting assistance it is best if you can provide a detailed description about what kind of problems/errors you are having. It is quite possible that the pack behaves differently for other people. Without that detailed information it is difficult to provide adequate assistance. You should be using the AE2 stable builds. You should remove the "(1)" from the Blood Magic file name (and any other file names). This sometimes causes fatal issues. Your Modular Powersuits mod is from an illegitimate source. Always get your mods directly from the mod authors. You are also missing Numina mod, a required dependency for Modular Powersuits. http://build.technicpack.net/job/ModularPowersuits/ (MP currently has issues with some recipes which requires MineTweaker to fix). You have Tinkers' Construct but not the required dependency mod Mantle. Address these issues and come back here with details if you are still having problems.

Attachments don't seem to be working in the forums. Please use a pastebin service.

Sounds like something has become corrupted in the smeltery/controller. Storing massive amounts of molten fluids in the smeltery is ill advised. You might have to break it and replace things creatively in order to protect your world.

The implication is that you don't have enough free RAM. Even if your system has 8G of physical RAM, if it is allocated to other processes you can run out of RAM for the BTeam server. Check how much free RAM you have and terminate as many memory hungry processes as possible while running the server.

Try using the 1.6.9.4 version of Factions, or maybe the 1.8.0 version for 1.4.7-1.0. Which specific version of MCPC+ are you using?

You have no options. The Launcher starts with a fixed size. Additionally, a system with those specs is going to struggle to run vanilla, much less a modpack.

You are getting an out of memory error. Here's the line in the crash report detailing your memory selections: Memory: 675984 bytes (0 MB) / 259522560 bytes (247 MB) up to 259522560 bytes (247 MB) You are allocating 256M to the server which likely means you aren't setting an -Xmx or -Xms line at all. The mod collection is fairly tame, but it'll never run in 256M.

MineTweaker: http://minetweaker3.powerofbytes.com/wiki/Main_Page Download: http://minecraft.curseforge.com/mc-mods/224029-minetweaker3/files Holler if you get stuck after going through the Wiki tutorials.

Okay, that was my bad. Sincerest apologies. I don't use Forge as the server (I use Cauldron) so I didn't notice that Forge was out of date. I updated that and everything works as expected. I'm using Java 8v40, but that shouldn't have any impact as I've tested it on 1.7 as well.

That looks like you are pasting the API URL into a web browser. You need to be pasting the API URL into the Technic Launcher to add the pack and then start it from within the Launcher.

Try a new version of Forge. There have been some updates specifically addressing splash screen issues.

The thing is, AM2 doesn't really do much with fluids and the worldgen essence seems to work perfectly in current Forge builds. I am able to launch a pack with the Forge #1424 and AM2 1.4.0.008 without problems including making a compendium and crafting spells.

I can't test what I can't see. Have you updated/changed your modpack archive/download? Have you incremented the pack version number?

I specifically mentioned that you need to use a pastebin service for log data. I'm not even going to look at that. Please remove it and provide a link to that data in a pastebin service.

Your iChunUtil, Morph, NEI, CodeChickenCore and Tinkers' Construct mods are from an illegitimate source. Always get your mods directly from the mod authors. These must be replace with their proper versions. Weather mod is improperly installed. Open the ZIP file and follow the author's instructions. You have included the 1.8.4 version of OptiFine. You need the latest 1.7.10 version. Address these issues and come back here if you have troubles.

You need to use a pastebin service for log data since the attachments here don't work. Dropbox public URLs should have the "www" replaced with "dl" and the question mark at the end removed along with everything after it. Make sure you are incrementing/changing the pack version number every time you change your download archive or location. Your modpack settings indicate the pack is for MC 1.8.3, but you have built the pack for MC 1.7.10. You need to adjust your pack settings. The bspkrsCore, ForgeMultipart mods belong in /mods/1.7.10/. It looks like you've included the contents of the /mods/1.7.10/ folder into /mods/. This is "bad". You should remove the "(1)" (and any similar) from the mod file names. This sometimes causes issues. Address these issues and come back if you are still having troubles.

Your download URL should be changed thusly: the "www" should be changed to "dl" and the question mark at the end should be removed along with everything after it. You should probably include the contents of the /mods/1.7.10/ folder. You have an absolutely ancient version of Tinkers' Construct which should be updated in order to be compatible with your selected version of Forge. I find it hard to believe that no crash report is being generated (on your client or server) if it is truly crashing. In any event, the FML logs will have crucial additional data which will aid you in resolving the issue. I'm unable to duplicate your error/crash. Every villager I can spawn or come across seems fine. Chests there seem fine as well.

Looks like something to do with biome/worldgen. You might try disabling Weather, just for testing. Also, you are on an old version of Forge and many of your mods have known issues that have been addressed in newer versions. You might try updating.

Always provide the API URL or a link to your pack details page when requesting custom modpack assistance. This post belongs in Platform Pagoda. Hopefully a kind admin will move the thread.

Your "orespawn-1.zip" file is definitely messed up. You should be directly downloading the mod from the author's website. The direct download is named "orespawn-1.7.10-20.3.zip" so I don't know where you got your file, but it is surely "incorrect". I see no reference to Lucky Block mod in your 2.0.1 download from earlier today. I can't test it now because your download URL for your pack is currently broken. I did not want to imply that your computer has malware. However, if your pack works everywhere else, and in every test environment I have access to but doesn't work reliably on your PC then the problem is on your PC. It could be a video driver issue, a memory issue of some sort, memory allocation, other system setting, who knows.