Jump to content

JaariAtmc

Ascended
  • Posts

    3045
  • Joined

  • Last visited

  • Days Won

    112

JaariAtmc last won the day on May 20 2023

JaariAtmc had the most liked content!

Recent Profile Visitors

20598 profile views

JaariAtmc's Achievements

  1. 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.
  2. And your modpack is?
  3. You still need to install java 8 to run the launcher.
  4. It probably tried to run on java 8, while Minecraft 1.20+ requires Java 21 or something.
  5. 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.
  6. 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.
  7. Private paste.
  8. 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.
  9. 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:
  10. 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.
  11. Mojang login is offline. It will not come back online. That's per microsoft/mojang.
  12. 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?
  13. "There is insufficient memory for the Java Runtime Environment to continue." Don't. Allocate. Memory. You. Don't. Have. Available.
  14. 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.
  15. 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
×
×
  • Create New...