How to Diagnose Crashes Caused by Connector Extras Submodules

Reading the crash report

Connector Extras is split into submodules, each handling one integration: energy, recipe viewers, reach attributes, config, and others. A crash report will usually name the submodule or the API it bridges, which tells you exactly which integration to investigate.

Narrowing down the cause

1. Read the top of the crash report for the exception type and the first mod-related class in the stack trace. That class usually belongs to either Connector Extras or the mod being bridged.

2. If the crash mentions a config API, the Forge Config API Port bridge is involved. Check whether the source mod's config file is malformed or was written by an incompatible version.

3. If the crash happens during startup before the main menu, it is almost always a bridge loading against an API that is not present. Confirm the mod providing that API is actually installed.

4. If the crash happens when opening a recipe viewer, disable the other viewers and retry. Multiple viewers fighting over the same bridge is a common cause.

5. If the crash happens only in a specific world, test a new world. A corrupted saved attribute or config value can trigger a bridge failure that a fresh world avoids.

Change one thing at a time between tests so you know which change actually fixed it.