What problem does it solve? Unreal Engine gameplay bugs — wrong values, bad positions, intermittent AI decisions, crashes — are hard to diagnose with logging alone. This Skill guides you to the right debugging tool for each question: DrawDebug shapes for spatial issues, the Visual Logger for events over time, the Gameplay Debugger for live AI/system state, and the native debugger for crashes. ## Core Features & Use Cases - World-space visualization: DrawDebugLine, DrawDebugSphere, DrawDebugCapsule, DrawDebugString, and on-screen messages via GEngine->AddOnScreenDebugMessage to inspect traces, ranges, and live values. - Timeline replay with Visual Logger: Record UE_VLOG text and spatial entries per actor, then scrub the timeline to reproduce intermittent or AI bugs that unfold over seconds. - Custom Gameplay Debugger categories: Register FGameplayDebuggerCategory subclasses with CollectData/DrawData replication to overlay your own system's state in PIE. - Native debugging and console tooling: VS/Rider breakpoints with natvis, Live Coding caveats, ensure vs check usage, and stat/showdebug/cvar commands for runtime interrogation. - Use Case: An AI bot in your Battle Royale project occasionally picks the wrong target. Record UE_VLOG_SEGMENT entries of its perception checks, replay the Visual Logger timeline, and confirm the exact frame the wrong target was acquired. ## Quick Start Ask the AI to help you visualize a weapon trace or AI detection radius in your Unreal Engine project using the appropriate DrawDebug or Visual Logger technique.