What problem does it solve? When a SparkEngine subsystem misbehaves (AI behavior trees, weapons, the ImGui editor, undo/redo, MMO modules, localization, cinematic audio, ECS ticking, or network prediction), developers waste time editing the wrong file. This Skill maps each concrete symptom to the exact source location, the expected correct code, and a cheap discriminating experiment to confirm the cause before changing anything. ## Core Features & Use Cases - Symptom-to-cause triage table: Nine verified entries covering cloned behavior trees, weapon damage attribution, editor world-swap UAF crashes, undo/redo dirty tracking, MMO dependency injection, localization dangling references, sequencer audio wiring, ECS phase ticking, and client-side prediction rubber-banding. - First-response toolkit: Log macros (SPARK_LOG_*), debug hooks, fault isolation (SPARK_GUARDED_UPDATE), crash dumps via crash_mode, and test selectors (SPARK_TEST_FILE/SPARK_TEST_NAME) for gathering signal before guessing. - Regression detection: Each row documents the fix that should be present, so you can spot when a historical bug has regressed versus a look-alike failure. - Use Case: Your ECS system compiles but never ticks. The Skill directs you to check CreatePhaseSystemManager registration, the flat-vs-phased AddSystem overload, null subsystem dependencies, and fault isolation status via fault.status in SparkConsole. ## Quick Start Describe the wrong behavior you observed in a running SparkEngine subsystem, such as "my ECS system never ticks" or "weapon damage is attributed to entity 0", and ask where to look and how to confirm the cause.
