gistfile1.txt

- I see some mods unfairly blamed for crashes or crashes that have missing mod assignments?

Sometimes we can't get full and/or valid information about package sources. Mod identification will never be fully reliable. That's why we have labels like "likely involved mods".

Here are common causes:
1. Due to few coremod's magic (like NEI), built-in mechanism of finding class source can sometimes fail (though in newer versions of OpenEye we use more reliable method).
2. Mod includes API classes. STOP THAT, it's not needed. If you include other mods' APIs you may be blamed for crashes in that part of code. Use @Optional.* and correct build process.
3. Stacktrace contains class from shared library. Every mod that includes this class will be marked as possible candidate.
3. Mod failed on startup (i.e. is in 'errored' state). When multiple mods crash on startup, only one exception is logged (FML limitation). We can retrieve information list about other mods that failed to initialize, but not stacktrace.
4. Crash has "We were unable to collect all information about this crash" annotation and empty mod list. Collection of information took too long and OpenEye skipped mod identification to prevent Minecraft from hanging. If crash happens next time and missing information is sent, it will be merged to current one.

It's also recommended to search for crashes by involved packages.