Jump to content

DaemonUmbra

Members
  • Posts

    11222
  • Joined

  • Last visited

  • Days Won

    67

Everything posted by DaemonUmbra

  1. 1.7.10 is no longer supported on this forum, please update to receive support. As a general rule Forge supports only the two most recent versions of Minecraft, any older than that and you will pretty much be on your own.
  2. Your debug.log file would provide more information, it's located in Minecraft's logs folder, the easiest way to get there would be to open a Run Prompt (Windows Key + R) and type %APPDATA%\.minecraft\logs This will open the logs folder in File Explorer, please use Pastebin or GitHub's Gist service to upload it, either site will give you a link to include in your post.
  3. Debug.log is found in your logs folder, if you are using the Mojang launcher on Windows you can get there easily by opening a Run prompt (Windows Key + R) and typing in %APPDATA%\.minecraft\logs this will open file explorer in your logs folder
  4. 1.7.10 is no longer supported on this forum. As you have already been told.
  5. Which part are you having trouble on, finding debug.log or using one of the sites?
  6. The first file appears to be corrupted, the second one all I can tell is that the issue is likely a coremod. Typically debug.log holds more information than the crash report.
  7. I might need a fresh log in that case, for modern versions debug.log would be best.
  8. You said you were opening your 1.10.2 Forge? Also do you really have 6 versions of Optifine in your mods folder?
  9. You used the given arguments on the universal (the one that starts the server) rather than the installer...
  10. You are registering this handler to the Event Bus, right?
  11. Please post your debug.log from the logs folder, preferably using a site like Pastebin or GitHub's Gist.
  12. Remove sourceSets from your build.gradle, the paths are wrong and regardless they are not needed for basic modding. I believe sourceSets are being set up for you by ForgeGradle at this stage, no need to override the defaults.
  13. Please make your own thread, this one is 4 years old and long dead.
  14. Please use a GitHub repository with the git root in the same directory as the .gitignore file the mdk comes with.
  15. Only the two most recent version of Minecraft are supported... please update.
  16. Well then you can't really say nothing is generated, can you? If you're using Windows an easy way to get to logs from the vanilla launcher is to open a run prompt (Windows Key + R) and type %APPDATA%\.minecraft\logs that will open the logs folder in Windows File Explorer, from there please upload your debug.log to a site like Pastebin or GitHub's Gist service and post the link it gives you.
  17. Which launcher? Do you know where to find the logs generated by that launcher?
  18. What a way to ask for assistance... Are you running a client or a server? What do you mean crashing, does it show any sort of window? What launcher are you using? By "no reports" do you mean no logs are generated at all?
  19. Please just follow our advice, it's not hard and will benefit any other Java apps you try to run. If you continue to insist on using 32-bit Java we will get nowhere...
  20. Can you post the debug.log file on pastebin, it usually contains more info than a crash log does. Note: If it's too long for pastebin GitHub's Gist service might accommodate larger files.
  21. Open cmd and type java -version The result you want to see will look like this: java version "1.8.0_152" Java(TM) SE Runtime Environment (build 1.8.0_152-b16) Java HotSpot(TM) 64-Bit Server VM (build 25.152-b16, mixed mode) Note the "64-Bit" part of it, if yours does not say "64-Bit" then you are running 32-Bit
  22. The 32-bit version of Java will not let you allocate more than 4G of RAM... that is why we are telling you to uninstall the 32-bit version and install 64-bit.
×
×
  • Create New...

Important Information

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