DaemonUmbra

If you are referring to a "These libraries failed to download" message during installation, try these instructions:

Please provide logs as described in the EAQ thread and/or my signature below.

Please provide logs as described in the EAQ thead and/or my signature below.

The twitch launcher does something weird with the native launcher, you'd have to tell Twitch to use the older jar launcher to get it to generate logs correctly.

Coremods are mods that directly rewrite Minecraft and/or other mods code when they are in memory and should be avoided where possible as the rewrites they do tend to threaten compatibility with other mods and almost never leave a trace back to the original mod when they screw up. They are removed like any other mod, just remove their jar file from the mods folder, though some may extract additional jars into the mods\[version] folder so you'll need to check there. In more recent versions you can check debug.log for the message Instantiating coremod class <Class Name>. Sadly a lot of coremod devs don't name their Coremod class with a reference to their actual mod, however the line after that should list the package for the mod which should include the mod developer's name or online handle, as well as the mod ID.

You should be using the build task. In your image: Tasks > build > build

Would you mind posting your source code on GitHub? It's easier than showing individual files.

You're sure it's the same error?

For Windows it's %appdata%, if you're using any other operating system the .minecraft in my signature is a link to the Minecraft Wiki page that will tell you where it is depending on your OS.

It sounds to me like a runaway thread on the server. Also I just noticed an error coming out of a known vanilla bug that I personally don't know a fix for, the ServerHangWatchdog's use of Thread.Sleep(). I am not an expert on this though, so we may need to wait for a more experienced person to come along.

They will be in your logs folder, see my signature below for more information.

It's not recommended to do so, have you tried following these instructions?

I don't see anything abnormal in the log, did you let this one quit itself or did you kill it? Also if you haven't I would recommend adding pause to the end of your launch.bat script, if you do that you will not want to touch the server between "Server Stopping" and "Press any key to continue..."

Code Style #1 and #2 In addition: Are you sure you have your server proxy in the right place AND have your serverSide set correctly in the @SidedProxy annotation?

Seriously? Even a couple of the sites I say not to use in my signature are less sketchy than the one you chose (Clicking OK on their message about browser cookies downloaded an EXE that I did NOT ask for). Uploading a text file will NOT crash PHP on any of the sites I linked and if it crashes your browser then you need to get a much more reliable browser.

Problematic Code #15

Has he changed any mods on his end?

You shared the log of one of the unsuccessful launches (Failed to bind to port, which means the previous server instance hasn't fully shut down yet). A log from the server instance that starts and takes ages to shut down would be of more use.

My signature echoes what is said in the EAQ, what you posted doesn't have as many details as the files we are asking for.

1.7.10 is no longer supported due to its age. Please update to a modern version of the game to receive support.

1.7.10 is no longer supported on this forum due to its age. Please update to receive support.

You need to do more research on Shadow, you are using the wrong plugin id and, if you are using the same gradle version I am (2.14, which the MDK has been shipping with for a while now), you are requesting the wrong version of Shadow.

To be honest this is the issue I'm seeing here, this is not directed solely at you, but you are the most recent case. 1.7.10 and 1.8.9 are old versions and should not be used for active development, your excuse that "I've seen others use 1.8.9" is the core of a cycle that keeps these ancient versions in a zombie-like state. People see others developing for these versions and assume that they are still valid versions to use, resulting in users ignoring recent versions in favor of using old versions that may be lacking features and/or security improvements that come from later versions. Imagine you had developed a game and after discovering and fixing a horrendous security issue in your game you then learned that people playing your game refused to update past the version just prior to the fix, then complained about the bug while insisting you continue to support that version of the game. As long as people continue to use the excuse of "They are doing it so it must be ok" old versions and the bugs in them will continue to haunt users of those versions as well as those they demand assistance from.

Try following these instructions:

If you insist on using an old version I’m afraid I can’t help you.