Reporting a Useful Bug

A useful report should contain enough context to distinguish an API bug, unsupported feature, version mismatch and unrelated mod conflict.

Include:

1. Toolkit version and FTK2 version.
2. BepInEx, Harmony and Unity versions from startup.
3. The full first ModAPI error and nearby log context.
4. Exact steps to reproduce.
5. Whether it happens on a new/disposable campaign or an existing save.
6. The namespaced custom content ID involved, if any.
7. The relevant ExampleMod runtime-test summary when reproducing with the validation harness.
8. Whether unrelated mods were removed for a control test.

Never upload a save containing private information you do not intend to share. For a blocked custom-content load, the missing namespaced definition IDs and the preflight state are usually more useful than repeatedly opening the save.