How to Use the Crash Report to Report a Bug to a Mod Author

Getting a report the author can actually use

A vague "it crashed" report gets ignored. Not Enough Crashes gives you a formatted, complete report with the information maintainers need. Your job is to copy it correctly and add context.

Steps

1. Reproduce the crash once so the report is fresh.

2. On the crash screen, use the copy button to copy the full log to your clipboard.

3. Paste it into a paste service rather than directly into a forum post, since reports are long.

4. Check the involved-mods list and open the issue tracker link for the most likely culprit.

5. In your bug report, include: what you were doing, whether it happens every time, your mod list, and the paste link.

6. Mention that the report came from Not Enough Crashes so the author knows the format.

What the extra details give the author

The syntax-highlighted stack trace shows exactly which line threw the exception. The NBT data section shows the state of the block entity or item involved, which is often the missing piece when a crash only happens with a specific machine or container. The involved-mods list saves the author from guessing which other mods are in play.

Before you post

Search the tracker for the same exception line. Many crashes are already reported, and adding your log to an existing issue is more useful than opening a duplicate.