JaariAtmc

If you left the launcher alone for, say, 2 hours, since this post, this has been resolved.

Yeah, it seems to be looking for a texture it can't find. Might've something to do with CustomMainMenu, as you are missing your CustomMainMenu, as you didn't include the required resources folder for that.

Oh no no no, you don't get here doing all that fancy stuff with not downloading mods from 9mc, actually including configs, and doing some prior lookin up information about how stuff works. What I gotta be angry about now? /s When I started your modpack, it did crash for me. This was caused by optifine. After removing optifine (and replacing forge 1558 with forge 1614), I got to the point that logistics pipes requires buildcraft to work. You might want to run a couple more tests to check if all dependencies are fulfilled. For the configuration, have you checked the JAS wiki? https://github.com/ProjectZulu/JustAnotherSpawner/wiki/Example-Configuration-Files

I checked your modpack again. Why the hell did you include all kinds of files normally found in the forge universal in the top folder?

In short, there were two main versions of Applied Energistics 2 in 1.7.10. One is rv2 (revision 2), the other one is rv3 (revision 3). Mods that require AE2 to be installed had to make their own different versions for rv2 and rv3. In this case, make sure you download a version of Wireless Crafting Terminals for rv3.

You included the wrong version of Wireless Crafting Terminals. https://www.curseforge.com/minecraft/mc-mods/wireless-crafting-terminal/files/all?filter-game-version=2020709689%3A4449 You included a version for AE2 rv2, while you have AE2 rv3 included.

Why are you distributing the server forge as the client forge? You can't run the server clientside, they need the forge universal.

What's the name of the modpack?

Remember the part where you needed to rename the forge jar to "modpack.jar"? In your case, you need to rename it to "modpack" instead of "modpack.jar".

Yes. You made a modpack for 1.12.2. You used Forge for 1.12.0 (aka 1.12). You need to use a Forge version for 1.12.2.

Can you add a screenshot of your logged in launcher please?

Your alternate option is the what is going to be the newish FTB launcher. That's your only alternative. Twitch is no longer an option as that will stop working the 31st. So, in 4 days. MultiMC does not support 1.13/1.14. Technic Launcher doesn't support 1.13/1.14. ATLauncher dev told that they were very sad at their attempt to make it work, and it sorta does. FTB launcher will possibly work, remains to be seen how well. Twitch offers the functionality for the next couple days and then their partnership with FTB is over. So yeah, there's pretty much no alternatives.

1. Your graphics drivers are outdated (Intel HD graphics), and this is due to you likely having upgraded this computer from an older windows version to Windows 10. 2. If updating graphics drivers doesn't work, you'll have to downgrade your java to 8u51/8u25, as that's the last update that worked in this case.

Mods WILL crash with a cracked client.

The "modified by hackphoenix.com". Could you also try with the actual technic launcher instead of a cracked one?

that's because Technic Launcher does not support modded 1.13/1.14 due to changes in how forge works. Fixing that would break any modpacks below 1.13/1.14.

What does it say in the bottom right corner?

Ah, can you provide a screenshot to your logged in technic launcher? Just gotta verify something.

1. Download your mods from Curseforge. Use this browser plugin to help you: https://stopmodreposts.org/downloads.html 2. Your communist mod is outdated and likely contains clientside only code. Might want to update this. Refer to point 1.

Nah, necroing old threads while not describing your own issue in any way or even checking if it was relevant is a pretty big nono on, like, any forums...

Eh. You actually got 3 issues. 1. Your graphics drivers are outdated (Intel HD graphics), and this is due to you likely having upgraded this computer from an older windows version to Windows 10. 2. If updating graphics drivers doesn't work, you'll have to downgrade your java to 8u51/8u25, as that's the last update that worked in this case. 3. You'll need to use java 64bits. The link in point 2 already provides a 64bits option. Currently you are allocating 512 MB, which is nowhere near enough RAM to use modded 1.12.2.

"I have downloaded and dropped the ''legacyjavafixer-1.0'' java file into my mods folder into the modpack (Yaopack) folder." This made it worse, as legacyjavafixer only has to do with pre-1.7.10 forge builds and is included by default starting with Build 1345 (recommended/latest Forge for 1.12.2) is 2768/2847. You see that screenshot that has a clickable link for the crashreport? Why not include that?

There's a Open Logs button under Launcher Options. Use the relevant day's log. Upload it to pastebin.com or paste.ubuntu.com (if too large for pastebin). Share the link here.

Remember that part where it said to name the file "modpack.jar"? In your case, only name it "modpack".

Eh, its what you get after the gazillionth case of this...