How to Diagnose Crashes Using Forgified Fabric API's Enhanced Reports

When a Fabric-dependent mod misbehaves on NeoForge, the crash report is your best tool, and Forgified Fabric API makes those reports more informative.

Find the Right Report

After a crash, locate the latest crash report in your instance's crash-reports folder, or read the console output if the game closed before writing one. The report is divided into a description, a stack trace, and mod-related sections.

Read the Stack Trace Top-Down

Start at the first line mentioning a mod's package name rather than Minecraft or Java internals. Forgified Fabric API adds extra information to crash reports, so look for entries naming Fabric API classes or the dependent mod. The class or method named there tells you which API feature was expected.

Separate API Problems from Mod Problems

If the missing class belongs to Fabric API itself, the API may be outdated relative to the mod, or the mod uses a Fabric API module not covered by the port. If the missing class belongs to the dependent mod, that mod is likely incompatible with NeoForge regardless of the API.

Reproduce and Isolate

Remove other mods and retry with only Forgified Fabric API plus the suspect mod. If it still crashes, the incompatibility is between those two. If it works alone, add mods back in small groups until the crash returns, which identifies the conflicting mod.