JaariAtmc

Your dropbox link and the dropbox link in your log don't match. You didn't rename the forge. You included Aether for 1.7.10 it seems. You included 3 mods that you did not get from Curseforge or the Modmakers website, but from something like crappy 9mc.

Thanks for pasting all the info of the crashreport that's utterly useless.

You are using 251, not 25.

It's actually 1.13 and higher and there's no fix for it. Forge 1.13+ is incompatible with Technic Launcher.

With that I mean that there's something wrong with the Forge you included. And no, I do not know what it is that's wrong with it.

Works fine after I replace the Forge in the modpack with a version I just downloaded. I dunno what's up with this, you're the third with this recently, and the Forge file structure in your modpack doesn't match the universal download I get.

Downgrade java to 8u51/8u25.

Play some other modpack, the one you are trying to play is dead.

How about adding those crashlogs to this conversation?

Something about an extracted mod jar, and the last one is saying that it tried to use 4 GB but it wasn't available. I Hate Users that dump their whole log.

Java Heapspace, considering that you are allocating 3.5 GB RAM, I dare say you only got 4 GB in your pc/laptop. Modded 1.12.2 is a resource hog, you'll be unable to use any medium to larger 1.12.2 modpacks. See if you can get some more RAM somewhere. No, downloading RAM isn't a thing.

How about your own logs?

Downgrade java to 8u25/8u51.

No log found, please try pastebin.

Hmm, that's strange. That file differs consiredably from the forge-renamed-to-modpack.jar in your modpack. Also, based on what I can see both in the modpack and in the download, the file wasn't changed?

You cannot allocate 4 GB if you only have 4 GB in your pc. It will never work out. Find some other modpack to play.

Post a link to the Forge you are downloading.

Hello Orange Juice, Based on the filesize of the modpack.jar, whatever file you renamed wasn't a Forge universal for 1.12.2. Please make sure to download the forge universal from files.minecraftforge.net.

They forgot to rename their forge, even though they were sure they did. We all have those moments.

That certain version being a snapshot for Minecraft 1.9. So Minecraft 1.9 was the soonest Mojang added compatability for IPv6. I'm sure you'd love to handle all the users that won't be able to play any of the official modpacks anymore?

The moment we enable it again, the launcher will cease working for everyone still using IPv4. That's a LOT of the playerbase, and it still wouldn't actually help with the IPv6.

Yes, you have 4 GB RAM in that laptop. You actually need it available, as in, not in use by other programs.

When we actually supported it, all hell broke loose. IPv4 is still supported by IPv6.

What were you supposed to do with the Forge file? Check again.

You started with 8 GB RAM, which didn't work because it was too much. Then you tried it with 10 GB. How about 5-6 GB max? Its just bloody pixelmon after all.