Issue Description:

When I try to load EnderIO together with Applied Energistic minecraft crashes at launch.

What happens:

Minecraft crashes at launch.

What you expected to happen:

Minecraft loading properly.

Steps to reproduce:

1. Put EnderCore, EnderIO and Applied Energistics in mods folder.
2. Launch Minecraft.

Affected Versions (Do not use "latest"):

• EnderIO: v3.0.1.141_beta
• EnderCore: v0.4.1.61-beta
• Minecraft: 1.10.2
• Forge: 12.18.3.2185
• Applied Energistics 2: v4_alpha_9

Your most recent log file where the issue was present:

http://pastebin.com/wpZ9MDr9

Extra Information:

As I am not sure which of the 2 mods is responsible I posted this in both githubs, the other ticket can be found here: AppliedEnergistics/Applied-Energistics-2#2708

This is very weird, I tried it again and it still crashes. Also, I don't really know what logfile you are looking for as missing, because I did post a crashlog pastebin link above. If I know what you are missing I can provide it!

Screenshots of modlist with either just EnderIO or just AE2:

Tried to reinstall forge without mercurius as that seemed to be a major difference between your modlist and mine, but it still crashes.

Here is another crashlog: http://pastebin.com/u9E9Htuf

Closing this one, see AE2 ticket for status.

@HenryLoenwind, Just a little question, so I can make better reports in github in the future. This topic has "log missing" as a tag, what log other then the two crashlogs do I need to post that were missing now?

Those are crash reports you posted. I wanted to have a look at the normal logfile of that run. The one that shows up in the launcher window. Because there I can see what happened before it finally crashed, e.g. if some mod wrote a line like "not registering oredict entry because there's a full moon today" or if one of those cracked launchers was used that corrupt the game startup process, or ...

Ah, thats clear, I also asked that in a post above because I am more then happy to provide anything a mod author needs to find out what goes wrong! I will post both in future tickets, thanks for clarifying!

Funny thing is: Whenever a report contains a full log and everything, I can diagnose the problem with a look at the first line of the stack trace and don't need anything more. ;)