AlexanderDupre

Situation handled. It was one of the mods. I deleted it.

So, I got a modpack going, and it's about half done. I just need to do some tweaking. It works perfectly in MultiMC, but I upload it to Dropbox, and re-download it via Tekkit, and it crashes. I spent half the day uploading that pack over and over, mainly due to forgetting something, and having to fix it. It takes almost an hour to upload, and I'm getting pretty angry, fist through my laptop angry. I need help. Modpack: Night Terrors I uploaded the console log. That log was taken after I removed LiteLoader, and Voxelmap, as I think they might have been one issue. They were obviously not the right issue.

Well thank you for letting me know what I didn't need help with, where I could find the help I didn't need help with, and where I could ask for help with the problem I didn't have. You have been an enormous help. Problem solved.

No... CLEARLY you can't READ. My initial statement is NOT incorrect. Some people were helped, some were not. I am getting the same error as the guy who started this post, and it is obviously not fixed by the first sticky. If it were.... THIS POST WOULDN'T EXIST. I have tried using the latest build, instead of the recommended build, but I get error-ed out. It says that the Mine colony mod has an item in conflict. Fine with me, I wasn't planning on using it. Unfortunately, the mod manager button is faded out in the launcher. Possible fix: In Options, select Latest build (1.2.5) rather than Recommended build (1.2.1/1.2.3). Before hitting log in, delete the Mine Colony mod and folder from the .techniclauncher\yogbox\mods\ folder. Hit login, and all should be ok... On my end, so far so good. I will update otherwise.

I am aware. I did that. I downloaded both 1.2.1 and 1.2.3 (recommended builds), renamed them to minecraft_#.jar, and selected them in options. This did not work. Once I read a suggestion, I tend to try it, and any alternative to it that I can think of before posting.

I will reply to you quote with another one! This is a quote from my own post, the same one you read.

That sticky fixes Tekken and Technic, not Vogbox, Voxel or H/M. Those are still a problem, reaplacing their JAR files does nothing, switching versions in Options does nothing, or errors out once MC starts. There is nothing, so far to fix this issue. The first sticky has thirteen pages of fail. It fixes the first bit on the first page, and rambles incoherently from then on.