Logging, Events & Diagnostics

IModLogger emits owner-tagged messages through ModAPI and BepInEx:

mod.Log.Info("Content", "Registering Ember Axe.");
mod.Log.Warning("Compatibility", "Optional dependency was not found.");
mod.Log.Error("Content", error);

FTK2API.Diagnostics.DumpState returns a text-only main-thread snapshot containing versions, lifecycle state, game-data generation, registered owners, subscribers, active content, patch state, and recent diagnostics.

1. Confirm API_INITIALIZED and versions.
2. Confirm the consumer's MOD_REGISTERED entry.
3. Confirm GAME_DATA_READY before native-template work.
4. Read the first owner/content error before secondary failures.
5. Attach the startup block and relevant context to a bug report.

ExampleMod's numbered PASS/FAIL reporter is a maintainer tool. Consumer mods can use public logging and diagnostics without adopting that internal harness.