Jump to content

DaemonUmbra

Members
  • Posts

    11222
  • Joined

  • Last visited

  • Days Won

    67

Everything posted by DaemonUmbra

  1. NEI IS for 1.12.2, it's just a JEI addon rather than its own thing now.
  2. Please provide the debug.log from both the client and server.
  3. This is irrelevant. You need to use Java 8 to launch any pre-1.13 Forge version.
  4. Please do not hijack threads, if you have an issue please make your own.
  5. You're trying to load an ancient coremod in 1.12.2, this is not going to work
  6. No, please do NOT automate Forge installation.
  7. Toss it out and follow a tutorial that's not a pile of poo. I recommend Cadiboo and Cubicoder's tutorials.
  8. There is no other way than getting the new installer.
  9. Please read the "Logs" section of my signature below and provide the appropriate log in the appropriate manner.
  10. Update to the latest version of Java 8: https://adoptopenjdk.net
  11. How can you tell it's not loading mods?
  12. Please don't necro old threads, if you have an issue make your own thread.
  13. What launcher are you using? Please provide a screenshot.
  14. That would require trusting the client, which you should never do.
  15. Why do you think this would be different between IDEs?
  16. Please provide your installer log, it will have the same name as the installer but with .log on the end: Installer: forge-{version}-installer.jar Log: forge-{version}-installer.jar.log Note: If you have Windows Explorer set to hide file extensions(as is the default setting), they will look like this: Installer: forge-{version}-installer Log: forge-{version}-installer.jar
  17. I don't recommend changing to the Jar Launcher because it is outdated and not guaranteed to work with Forge. The Native launcher is what is targeted now. Also there is a video of me going through the steps if you find the written steps confusing.
  18. Foamfix appears to be colliding with another coremod.
  19. It looks like you had OTG installed at one point and then removed it. Unfortunately OTG installs a component of itself into a 1.12.2 folder in your mods folder that tries to run whether the rest of the mod is there or not, and when the rest of the mod is NOT there you get this error. Just remove the otgcore file from the 1.12.2 folder.
  20. You should not be extracting Forge. Just run the installer and make a launcher profile/installation, then select Forge as the version.
  21. There is no need for anything chromium to be packed with Forge. Quick reminder that anything Forge is Open Source on GitHub.
  22. There is nothing Lex or any other member of the Forge team can do without resources they don't have. Couple that with the fact that many of those sites are hosted in countries that don't abide by US Copyright law... Best I can do is recommend that you and your friends read up on the StopModReposts project and install their browser extension, which will alert you when you visit a site they've blacklisted. Beyond that, have them run anti-virus scans
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.