How do I diagnose a specific console error (plugin, mod, thread, or config error)?

Most startup and runtime errors tell you exactly what went wrong — if you read the first error, not the last. The trick is finding that first line and working from it, rather than chasing the cascade of errors that follows.

How it works

When something breaks, one root failure often triggers a string of follow-on errors. Scrolling to the last line usually shows only the fallout. The earliest ERROR or severe line is where the real problem lives.

How to diagnose

1. Open the Console or latest.log and scroll to the first ERROR/severe line — later errors are often just fallout from it.
2. Note any file, plugin, mod, or class name mentioned.
3. Search that exact message plus your software and version, or share the full log via mclo.gs.
4. Apply the fix (correct the config, update or remove the add-on, add the missing dependency) and restart.

Tip: Use the Console's Share logs via mclo.gs button — a full log link lets us or the community pinpoint the cause far faster than a screenshot.

Tips & best practices

• Back up your files before big changes (via Files/SFTP while the Backups tab is being rebuilt).
• Test add-ons one at a time so a single bad one is easy to spot.

Frequently asked questions

Should I use the crash report or latest.log? Both help. If a crash report was generated, grab it too — it often has extra detail alongside latest.log.

Where's mclo.gs? It's built into the Console header, and you can also upload logs to it manually if you prefer.