godot-optimization_skill

Overview

This skill provides expert guidance for profiling and optimizing Godot projects to improve FPS, reduce frame time, and lower memory usage. It focuses on finding bottlenecks across processing, physics, rendering, and scripts, then prescribing concrete fixes like caching, pooling, LOD, and spatial partitioning. Use it to get actionable steps, code snippets, and a repeatable workflow to measure gains.

How this skill works

I inspect profiler output and key monitors (FPS, frame time, process/physics time, render metrics, memory and object counts) to locate the dominant bottleneck. Then I drill into common hotspots—excess _process() calls, node lookups, heavy draw calls, collision checks, and allocations—and recommend targeted changes with sample GDScript patterns. Finally I guide re-measurement and platform-specific adjustments for mobile or web builds.

When to use it

• When you see FPS drops, stuttering, or high frame times
• When profiling shows Process, Physics, or Render as dominant cost
• Before shipping to mobile or web to meet target performance
• When memory usage grows or scenes cause high object counts
• When heavy draw calls (many sprites/particles/lights) impact frame time

Best practices

• Profile first—measure before changing code and after to verify improvement
• Cache node references and group lookups to avoid repeated searches
• Reduce _process/_physics frequency or disable processing when idle
• Use object pooling, MultiMesh, TileMaps and texture atlases to cut draw calls
• Use Area nodes, collision layers, and spatial partitioning to limit checks
• Apply deferred calls for physics modifications and free unused resources

Example use cases

• Diagnose a 30–60 FPS regression in a crowded 2D scene and convert sprites to MultiMesh/TileMap
• Fix physics slowdowns by moving expensive checks out of _physics_process or using Area detection
• Reduce memory spikes by switching duplicated scenes to instancing and clearing ResourceLoader cache
• Optimize mobile build: reduce particle counts, simplify shaders, lower viewport resolution, and disable SSAO/glow
• Implement LOD and chunked loading for large 3D open worlds to limit active objects