• Content count

  • Joined

  • Last visited

  • Days Won


JaariAtmc last won the day on October 30

JaariAtmc had the most liked content!

About JaariAtmc

  • Rank
  • Birthday

Recent Profile Visitors

8592 profile views
  1. Downgrade your java to 8u51 and try again.
  2. Update CTM https://minecraft.curseforge.com/projects/ctm/files/2629306 Changelog explains why.
  3. Considering that this process was changed only with minecraft 1.9 and up (so minecraft 1.8 and below are affected), and since CCL is required for almost every modpack out there... Also, for later versions, some other mods also store their required dependencies on the forge servers...
  4. I asked one of the admins, and they were unsure why technicssp is not included. I checked the old launcher (cannot be logged into anymore, thus useless), and saw that said modpack was included. https://github.com/TechnicPack/Technic/blob/master/technicssp/modpack.yml This page shows which mod versions were included. It is actually possible to still download these files. Start a PM if you are interested in downloading these.
  5. Forge pushed some fix, and it broke some downloads in return. In your case, the download of CodeChickenLib, which is stored on Forge's servers.
  6. You added the required dependency for MoCreatures, right?
  7. error

    "Everything seems to be in order" Then why is the modpack's size 2.5 GB? Oh, found it. This modpack is a copy of the 1.7.10 pack, with a cache folder of 2 GB, which contains the copied modpack twice, next to the newly named modpack, which is there twice.
  8. Ah, this was resolved on Discord. I remember seeing the log there.
  9. We do not support cracked launchers in any way. They either pay for a minecraft/mojang account, or they can kindly (or not so kindly) piss off.
  10. What Sp client are you talking about?
  11. Its like its almost written out in the log... Missing Mods: forge : [,) net.minecraftforge.fml.common.MissingModsException: Mod twilightforest (The Twilight Forest) requires [[email protected][,)] I dunno, you may be having some outdated Forge or something...
  12. error

    Yes, this issue was fixed about two hours after the initial report.
  13. This issue was fixed about 2 hours after the initial report.
  14. This issue was fixed about 2 hours after the initial report.
  15. Issue was fixed 2 hours after the initial report.