Debugging & Profiling

Expert guidance for finding and fixing bugs efficiently with Godot's debugging tools.

NEVER Do

NEVER use print() without descriptive context — print(value) is useless. Use print("Player health:", health) with labels.
NEVER leave debug prints in release builds — Wrap in if OS.is_debug_build() or use custom DEBUG const. Prints slow down release.
NEVER ignore push_warning() messages — Warnings indicate potential bugs (null refs, deprecated APIs). Fix them before they become errors.
NEVER use assert() for runtime validation in release — Asserts are disabled in release builds. Use if not condition: push_error() for runtime checks.
NEVER profile in debug mode — Debug builds are 5-10x slower. Always profile with release exports or --release flag.

MANDATORY: Read the appropriate script before implementing the corresponding pattern.

Custom Performance monitors for gameplay metrics (projectile/enemy count). Includes automated error state capture with stack traces and memory stats.