DaemonUmbra

Which part are you having trouble on, finding debug.log or using one of the sites?

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.

I might need a fresh log in that case, for modern versions debug.log would be best.

You said you were opening your 1.10.2 Forge? Also do you really have 6 versions of Optifine in your mods folder?

You used the given arguments on the universal (the one that starts the server) rather than the installer...

You are registering this handler to the Event Bus, right?

Please post your debug.log from the logs folder, preferably using a site like Pastebin or GitHub's Gist.

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.

Please make your own thread, this one is 4 years old and long dead.

Try these instructions:

Please use a GitHub repository with the git root in the same directory as the .gitignore file the mdk comes with.

Only the two most recent version of Minecraft are supported... please update.

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.

Which launcher? Do you know where to find the logs generated by that launcher?

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?

Direct Link

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...

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.

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

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.

See MDW01's response:

Try replacing RoughMobs with RoughMobs2, apparently it was rewritten with bugfixes and performance fixes (what you seem to have here is RoughMobs making the server take too long to tick, thus it gets killed by the Watchdog)

You appear to be using 32-bit Java, although that does not appear to be the cause this time you really should get the 64 bit version. You are still only allocating 1G of RAM to the game, as you have -Xmx2G before -Xmx1G, in JVM arguments the last one wins. Note: I do not see a crash here, so I cant definitively say this is the issue, I can just say these are the flaws I see in the information you have provided.

Are you saying you have looked and there is no log? Setting up a log is on of the first things Minecraft does, usually this is before it has a chance to crash. If there is no log please upload a screenshot of what cmd or powrshell spit out when you try to start the server, and make sure the cmd/powrshell window is big enough that it dos not get cut off.

The log will have been saved as debug.log in your logs folder, please use a site like pastebin or Github's Gist tool and post the link it gives you.