plowmanplow

Someone will assist you when and if they can. Bumping your thread doesn't help. I know that, for myself, I always start with the oldest threads and work up when responding and if I run out of time I don't get to the top so bumping your thread may be counterproductive for you. Your download URL set in your pack is not a direct link. You need to add "?download=1" (without quotes) to the URL. Your binmodpack.jar file is incorrect. The modpack.jar file is simply the correct version of the Forge universal binary JAR downloaded and renamed to modpack.jar. You have an outdated version of Forge for 1.6.4 with extra stuff in it as your modpack.jar. This must be fixed. You have Bukkit plugins (Essentials) in your mods folder. These should be removed. You have a bspkrsCore file in both the mods folder and the mods1.7.10 folder. This mod belongs only in the 1.7.10 folder and should never have duplicates.

You can only allocate 3G of RAM to what? How much physical RAM does your PC have? What version and platform of Java are you using?

Adventurer's Dream: The binmodpack.jar file is named "modpackAD.jar". This would need to be renamed to modpack.jar before the pack will start. The modpack archive includes no config files. This is always bad. The pack has an automated ID fixing mod, but they seldom provide a 100% solution. The pack has some item ID conflicts. The Ethernal Flame RPG: This pack is packaged and built in just a fundamentally improper way that it just needs to be started over from scratch. It is a modpack in name only.

Yes, the API URL would be handy As for your log, if you aren't familiar with it, there is a website ( http://pastebin.com/ ) which will allow you to paste your log files, maintaining formatting, and give you a URL you can paste into the forum here.

You have the wrong version of Forge as your modpack.jar. Download the latest 1.6.4 version of Forge and replace your existing modpack.jar.

I see that now. That's the kind of information that would be handy if provided by the OP. As the issue clearly looks graphics/GL related I am suspicious that this issue might be more general on his system. Obviously without more information it is impossible to say.

The contents of your modpack archive are in a subfolder. All the required folders (bin, config, mods) must be at the top level of the folder structure inside the modpack archive. Your modpack.jar file is named "modpack.jar.jar". Google "windows always show file extensions" to find out how to prevent this problem. You have Forge for 1.7.10 as your modpack.jar(.jar) but your modpack settings are set to 1.7.9. You need to adjust your pack settings. You have OptiFine for 1.7.4. You need to get the latest version for 1.7.10. You have a number of mods that list their versions as for Forge/MC 1.7.2. Double check to make sure that the authors indicate that those mods work for both 1.7.2 and 1.7.10 or they'll probably need to be removed.

MouseTweaks{2.4.4} [Mouse Tweaks] (MouseTweaks-2.4.4-mc1.7.10.jar) Unloaded->Constructed->Pre-initialized->Errored This is a client-only mod.

If this is happening with one of the modpacks created and maintained by the Technic group you need to be using the appropriate Tracker: http://forums.technicpack.net/tracker/

This sounds like it belongs in the tracker for the Launcher: http://forums.technicpack.net/tracker/project-1-technic-launcher/

How much physical RAM does your PC have? What type and size of hard disk drive do you have? How much memory are you allocating to the launcher? What version and platform of Java are you running? Your PC may be becoming overburdened when running both your local client and the server at the same time. Doing that is always suboptimal but with some tweaking (depending on your answers to the questions above) you might be able to improve performance a bit.

Yes to both. It's basically Tekkit Lite for 1.6.4.

While 1% packet loss isn't great, it shouldn't be enough to cause a problem like that.

The challenge for me is that your updated download you provided works. The modpack itself does not because you haven't updated the version number and download URL in the pack settings. Until the latter happens your client modpack won't change and you won't get a Forge log.

Whatever entry that references that number should be changed.

For 1.6.4 packs, the logs are in the modpacks's folder.

Unless your PC has 16G of RAM you really, really don't want to be setting your launcher to allocate 7G. Set it to 3G unless you are trying to use 256x or higher texture packs in which case you would set it to 4G. at net.minecraft.network.packet.Packet24MobSpawn.func_73279_a(SourceFile:87) I see the above error frequently when OreSpawn is included in large(ish) packs that have other entity manipulation in them. Try removing OreSpawn and see if you are able to start things up.

@Daniscool: That's because OptiFine does "weird sketchy things" and is often incompatible with a ton of mods. Make sure you are using the latest version for your version of Forge/MC. If that doesn't work you won't be able to use it.

The file in your bin folder named "modpack.zip" should be removed. The binmodpack.jar file, which is the only file that should be in that folder, is simply the correct version of the Forge universal binary JAR renamed to "modpack.jar". http://files.minecraftforge.net/ All versions of Forge from 1.6 on do not use a coremods folder in any way. All mods belong in or below the mods folder. However, the Forge universal JAR does not belong in the mods folder at all (see bullet point #1). Your folder named "flan" should be named "Flan" (case matters here). The files that go into the Flan folder should be left as ZIP files. Do not extract them. You have "idfix-1.6.4-1.1.0.jar" in your mods folder. Forge/MC 1.7+ mods do not require ID fixing. This should be removed. Your ChickenBones mods are out of date and should be updated (CodeChickenCore, NEI). After making these changes I was able to start your pack in a test environment.

You have set an item or block (looks like a block) to ID #200000. Block IDs must be <= 4095 and item IDs should be set to be between 4096 and 31743 in the config files. Find this ID and fix it. This post on fixing conflicts may help you:

The reason I always ask for the API URL is because I use this page: http://www.circlecraft.info/platform/ . It allows me to see the pack details and link to the download URL in a similar fashion as the Launcher and makes it easier to track down problems. You have a couple item ID conflicts that need fixed. Search your ForgeModLoader-client-0.log file for the word CONFLICT. Not all of them can/should be addressed, but the ones that list a conflict between two different mods (like ThermalExpansion and AlchemicalWizardry) must be fixed. When I copy your config and mods folders to my BareBonesPack setup for 1.6.4 the client starts just fine (other than the aforementioned conflicts).

There is a file in the modpack.jar file named "version.json". In that file you can see other java arguments at the top. You can extract that file, add those arguments, and put the file back in the archive (rename it to modpack.jar.zip first). You might also try OptiFine and fiddle with the options there. It helps some, does nothing for others, and total fails with some. Your mileage may vary.

Good to see someone getting use out of my BareBonesPack As for your crash: Caused by: java.lang.NoClassDefFoundError: cofh/util/ThermalExpansionHelper You have an old version of BigReactors (which uses the CoFH APIs). You need to update BigReactors. Come back if you still have troubles after that.

The Eureka mod is not behaving properly. It seems as though it isn't properly proxying the client only API calls. It will have to be removed (until it is fixed) and therefore you will have to remove Buildcraft Additions as well. You Chickenbones mods (CodeChickenCore, EnderStorage, NEI) are very out of date and must be updated. Your AE2 mod is out of date. I would recommend updating any of your outdated mods.

If it is truly a client crash you might get more help in the Tracker for TekkitLite. Always include a crash report and follow their template.