JaariAtmc

Please make sure that you have set a username on the vanilla mojang launcher (Account button at the top -> Manage Minecraft: Java Edition Profile -> In opened window, choose Profile Name and set a name if you didn't already). If you have that, make 300% or 400% sure you are ACTUALLY using the right email. We've already had people swear up and down they were using the right email, only to find out they were, in fact, not using the right email.

And your modpack is?

You still need to install java 8 to run the launcher.

It probably tried to run on java 8, while Minecraft 1.20+ requires Java 21 or something.

Make ABSOLUTELY SURE, like REALLY, REALLY, REAAAAALLLY sure you are using the right email. Secondly, make sure you've set a username in the vanilla launcher.

This particular one had absolutely nothing to do with Jurassicraft, because this one had to do with MoarCarts and seemingly its compatibility with Minefactory Reloaded. Yes, nowadays it's most likely going to be LLibrary and Jurassicraft, but don't reply to 5 year old threads attempting to provide help on something you yourself said you have no clue about.

Private paste.

It's something stupid. You put the bin/mods/config in a folder, then zipped that folder. You have to select the bin/mods/config -> Add to zip instead. Right now, there will be a lovely "modpack" folder in your modpack's folder, which contains your 'missing' folders.

Please try to make sure that your NVIDIA card is used. This particular issue is because of the drivers of your Intel graphics driver. It affects minecraft up to 1.7.10. Copied below from the Technic Discord, hence the formatting looking a bit wonky:

Known issue, is being worked on. Forge changed something with their installers, which causes the "wrapper" that Technic uses to start Forge to not work properly anymore for a bunch of new versions of Minecraft. I think the cut-off version is like 1.16. However, it's not a simple case of updating the wrapper, as that breaks almost all older modpacks.

Mojang login is offline. It will not come back online. That's per microsoft/mojang.

A minor look through google indicates too many biome altering mods. As a test case, could you try removing Endless Biomes from your modpack and see if the issue persists?

"There is insufficient memory for the Java Runtime Environment to continue." Don't. Allocate. Memory. You. Don't. Have. Available.

You are trying to allocate 6 GB RAM, but this crashlog is telling that the game tried to allocate that but couldn't, as it wasn't available.

Grab 40.2.9 from the all versions list instead. That works as well, as per https://github.com/MinecraftForge/MinecraftForge/issues/9765#issuecomment-1783862198

You have a modpack for 1.18.2, but you included the forge installer for 1.20. That does not work.

What kind of graphics card do you have? The reason I'm asking is because of the warning on the 128x Full.

Have you grabbed the 128x or the 128x Full?

The name displayed on the Launcher is the name associated with the account you are logging into. If the name doesn't match, then you are not logging in with the correct account.

So, which of the patches are you two using?

The amount allocated doesn't matter here, as you are only using about 1 GB to about 2.7 GB for the modpacks. Are you sure you aren't experiencing thermal throttling of your cpu/gpu while playing minecraft? You can check this by downloading programs like CPU-Z or HWiNFO (HWiNFO preferred by myself).

Have you checked the "Used Memory" line above that as well?

Right, because the forums is absolutely filled with this exact issue. I looked through the discord, we have exactly 10+8 messages which cover the two errors present, all are for different things, all were fixed by restarting the launcher once, twice or thrice, with the exception of a bug fix for something related but unrelated to this back in 2021. So yes, we don't test for edge cases that are 1 in a 10 million chance of happening.

That's your Intel HD Graphics drivers. If you do not have a dedicated GPU, you have to downgrade your intel graphics drivers to version 1069. This issue affects modpacks up to 1.7.10 only. 1.8+ is not affected.

Which modpack version are you using?