Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by JaariAtmc

  1. Don't use 15 GB. That's the whole problem, you are allocating way too much memory.
  2. JaariAtmc

    Hexxit wont work

    Downgrade your java to 8u251 and try again. https://javadl.oracle.com/webapps/download/AutoDL?BundleId=242044_3d5a2bb8f8d4428bbe94aed7ec7ae784
  3. Translation of the issue: You are using jdk13 for forge below 1.13 (1.7.10 in this case). ONLY Java 8 works for those versions.
  4. When the modpack updates, the mods folder is wiped and restored from the cache folder, which contains the new mods. Your old additions are just gone.
  5. Did you use the Forge installer? That's only for forge 1.12.2 (2851 and up) and 1.13+. For any older version, keep on using the Forge universal file.
  6. This belongs in Platform Pagoda. Have them install and use this version of java. https://javadl.sun.com/webapps/download/AutoDL?BundleId=107944
  7. This is a platform pagoda thing, really. TechnicLauncher bugs end when you can open the launcher. Platform pagoda starts when you click start/play on any modpack. Note: The following is based on experience and the information provided. For better support, provide a techniclauncher log. Use pastebin or paste.ubuntu.com for the log upload. That said, sounds like she'll have to downgrade her java, considering she doesn't have a dedicated gpu, which implies integrated graphics on the intel cpu, in which case most older cpus have issues with newer java versions. I suppose I can assume her cpu is older, since she only had 6 GB RAM in her computer/laptop?, which is an uncommon amount these days, which thus implies an older computer, thus an older cpu. Based on the age of her cpu, she'll either have to use java 8u251 or 8u51. I cannot determine from the message if she has a Mac or Windows computer, so I'll provide the 8u251 download link for both OS' here. Close the launcher, install the downloaded java, start the launcher again and select the version under Launcher Options -> Java settings. Windows: https://javadl.oracle.com/webapps/download/AutoDL?BundleId=242044_3d5a2bb8f8d4428bbe94aed7ec7ae784 Mac: https://javadl.oracle.com/webapps/download/GetFile/1.8.0_251-b08/3d5a2bb8f8d4428bbe94aed7ec7ae784/unix-i586/jdk-8u251-macosx-x64.dmg
  8. Did you press Add Microsoft account or did you press Log In?
  9. Quite literally, install 64 bit java. https://java.com/en/download/manual.jsp
  10. Microsoft account? If so -> Log out, then log back in BY PRESSING THE ADD MICROSOFT ACCOUNT BUTTON.
  11. Have them log out, then log back in BY PRESSING THE ADD MICROSOFT ACCOUNT BUTTON.
  12. This is the Attack of the Bteam subforums. It has nothing to do with the Omega Messpack. RAM has little to do with lag, unless you don't have enough allocated. Then it causes lag (due to running out of memory). Besides enough RAM, the Omega Messpack also needs a really decent cpu and/or gpu since its such a pile-on mess.
  13. This is a thing between Chrome and the download buttons. Other web browsers do not have this issue. Try using Firefox, Edge or Safari to download the server.
  14. Pixelmon, considering it is 1.12.2, requires 4-6 GB memory. 2 GB will get you stuck on the screen you shared as a picture.
  15. Downgrade Java. https://javadl.oracle.com/webapps/download/AutoDL?BundleId=242044_3d5a2bb8f8d4428bbe94aed7ec7ae784
  16. "If you have previously logged in with a Microsoft account and your packs are showing as offline or you're unable to join servers, and can log in to the vanilla Launcher, then click Log Out, and then Add Microsoft account and proceed to log in again to solve this issue."
  17. Manually update this mod to version .48. https://www.curseforge.com/minecraft/mc-mods/codechickencore/files/3293859
  18. Microsoft account? Log out and press the Add Microsoft Account button.
  19. Well, if the modpack you are playing is below minecraft 1.8, then yes, they will always be a non-slim skin.
  20. Microsoft account? Log out, then log back in using the Add Microsoft account button.
  21. Finally had some time to check. I downloaded the pack, started it, ran as vanilla. Went into the bin folder, delete the version.json and the modpack.jar. Put the Forge 2854 installer in there, renamed to modpack.jar. Observed the modpack starting with forge. Froze around startup phase 3, as I had my RAM set to a low amount, due to playing an older modpack.
  • Create New...