Jump to content

JaariAtmc

Ascended
  • Posts

    3052
  • Joined

  • Last visited

  • Days Won

    112

Everything posted by JaariAtmc

  1. Forge installation process changed drastically in 1.13. Don't expect it to work for 1.13, 1.14 and 1.15. Probably not for 1.16 and 1.17 either. Good luck changing LexManos' mind. Hell freezes over, thaws and freezes over again before that might happen.
  2. You cannot. The old way to do so broke when Forge changed the whole installation process in 1.13.
  3. Remove DamageIndicators, for it is a clientside-only mod. You might have to do the same for the UptoDate mod you (or whoever made the modpacK) included.
  4. Get offline java (https://java.com/en/download/windows_offline.jsp) and allocate 2-3 GB RAM in Launcher Options -> Java Settings.
  5. Your issue has fck all to do with their issue. Your issue has to do with the Ex Compressum Skin registry for the autosieve.
  6. Buy Minecraft.
  7. Downgrade your java to 8u51.
  8. Why have you been sourcing mods from 9mc (that's really bad) and what file is missing in your bin folder?
  9. You forgot CodeChickenCore and why are you still using Java 7 (and u40 too)?
  10. Forge broke this process in 1.13, so 1.13, 1.14 and 1.15 simply don't work anymore. No ETA for fix, if it'll ever be fixed. Getting Lex to change this process? Eh, hell freezes ten times over before he changes something.
  11. Remove the .jar from your modpack.jar. (you got a modpack.jar.jar). Also, you used the Forge universal, right? Not the forge installer, like the mac file I see in your mods folder, right?
  12. I do not know if you changed something in the meantime, but I downloaded and started your modpack. Got to the main menu, 81 mods loaded.
  13. It would potentially help if you kept the download link working. Both here and on the launcher. Thanks for the easy to find name though, that's quite rare actually.
  14. How about adding CoFHcore?
  15. Well, normally, you'd use the method I described...
  16. Yes, that's the process. However, these folders are now added to a folder, and THAT folder gets zipped. And that's what's not working. That folder shouldn't be there. I should open your zip and immediately see the bin/config/mods folder.
  17. Remove the .jar from your modpack.jar.
  18. Again, you didn't zip the folders in the correct way. Select the bin/config/mods folders -> Add to archive. That's the correct way of zipping.
  19. Yes, you have those zipped, however, your situation is that you zipped it like this: Zip > modpack > bin/config/mods/resources. You need to directly zip those folders, aka: Zip > bin/config/mods/resources. For the modpack host, either selfhost it, use paid mediafire, or use free dropbox.
  20. I hope you are aware that your free mediafire link has already broken. You zipped your modpack incorrectly, directly zip the bin/config/mods/resources folder.
  21. How about buying normal minecraft and not using mcleaks?
  22. What's your minecraft account name? Have you ever used mcleaks?
  23. Log shows you opened Bteam just fine, although its cut a bit short.
  24. Downgrade java to 8u51/8u25 and try to update your intel drivers with this: https://www.intel.com/content/www/us/en/support/detect.html
×
×
  • Create New...