godot-optimization
Expert knowledge of Godot performance optimization, profiling, bottleneck identification, and optimization techniques. Use when helping improve game performance or analyzing performance issues.
What this skill does
You are a Godot performance optimization expert with deep knowledge of profiling, bottleneck identification, and optimization techniques for both 2D and 3D games.
# Performance Profiling
## Built-in Godot Profiler
**Accessing the Profiler:**
- Debug → Profiler (while game is running)
- Tabs: Frame, Monitors, Network, Visual
**Key Metrics to Watch:**
- **FPS (Frames Per Second)**: Should be 60 for smooth gameplay (or 30 for mobile)
- **Frame Time**: Should be <16.67ms for 60 FPS
- **Physics Frame Time**: Physics processing time
- **Idle Time**: Non-physics processing time
## Performance Monitors
```gdscript
# Enable performance monitoring in code
func _ready():
# Available monitors
Performance.get_monitor(Performance.TIME_FPS)
Performance.get_monitor(Performance.TIME_PROCESS)
Performance.get_monitor(Performance.TIME_PHYSICS_PROCESS)
Performance.get_monitor(Performance.MEMORY_STATIC)
Performance.get_monitor(Performance.MEMORY_DYNAMIC)
Performance.get_monitor(Performance.OBJECT_COUNT)
Performance.get_monitor(Performance.OBJECT_NODE_COUNT)
Performance.get_monitor(Performance.RENDER_OBJECTS_IN_FRAME)
Performance.get_monitor(Performance.RENDER_VERTICES_IN_FRAME)
# Display FPS counter
func _process(_delta):
var fps = Performance.get_monitor(Performance.TIME_FPS)
$FPSLabel.text = "FPS: %d" % fps
```
# Common Performance Bottlenecks
## 1. Too Many _process() Calls
**Problem:**
```gdscript
# BAD: Running every frame when not needed
func _process(delta):
check_for_enemies() # Expensive operation
update_ui()
scan_environment()
```
**Solution:**
```gdscript
# GOOD: Use timers or reduce frequency
var check_timer: float = 0.0
const CHECK_INTERVAL: float = 0.5 # Check twice per second
func _process(delta):
check_timer += delta
if check_timer >= CHECK_INTERVAL:
check_timer = 0.0
check_for_enemies()
# Or disable processing when not needed
func _ready():
set_process(false) # Enable only when active
```
## 2. Inefficient Node Lookups
**Problem:**
```gdscript
# BAD: Getting nodes every frame
func _process(delta):
var player = get_node("/root/Main/Player") # Slow lookup every frame
look_at(player.global_position)
```
**Solution:**
```gdscript
# GOOD: Cache node references
@onready var player: Node2D = get_node("/root/Main/Player")
func _process(delta):
if player:
look_at(player.global_position)
```
## 3. Excessive get_tree() Calls
**Problem:**
```gdscript
# BAD: Repeated tree searches
func update():
for enemy in get_tree().get_nodes_in_group("enemies"):
# Process enemy
func check():
for item in get_tree().get_nodes_in_group("items"):
# Process item
```
**Solution:**
```gdscript
# GOOD: Cache groups or use signals
var enemies: Array = []
func _ready():
enemies = get_tree().get_nodes_in_group("enemies")
# Update when enemies added/removed via signals
```
## 4. Inefficient Collision Checking
**Problem:**
```gdscript
# BAD: Checking all objects every frame
func _physics_process(delta):
for object in all_objects:
if global_position.distance_to(object.global_position) < 100:
# Do something
```
**Solution:**
```gdscript
# GOOD: Use Area2D/Area3D for automatic detection
@onready var detection_area = $DetectionArea
func _ready():
detection_area.body_entered.connect(_on_body_detected)
func _on_body_detected(body):
# Only called when something enters range
pass
```
## 5. Too Many Draw Calls
**Problem:**
- Too many individual sprites
- No texture atlasing
- Excessive particles
- Too many lights
**Solution:**
```gdscript
# Use TileMap instead of individual Sprite2D nodes
# Use MultiMeshInstance for repeated objects
# Use texture atlases to batch sprites
# Limit number of lights and particles
# Example: MultiMesh for coins
@onready var multimesh_instance = $MultiMeshInstance2D
func _ready():
var multimesh = MultiMesh.new()
multimesh.mesh = preload("res://meshes/coin.tres")
multimesh.instance_count = 100
for i in range(100):
var transform = Transform2D()
transform.origin = Vector2(i * 50, 0)
multimesh.set_instance_transform_2d(i, transform)
multimesh_instance.multimesh = multimesh
```
## 6. Unoptimized Scripts
**Problem:**
```gdscript
# BAD: Creating new objects every frame
func _process(delta):
var direction = Vector2.ZERO # New object every frame
direction = (target.position - position).normalized()
```
**Solution:**
```gdscript
# GOOD: Reuse objects
var direction: Vector2 = Vector2.ZERO # Reused
func _process(delta):
direction = (target.position - position).normalized()
```
# Optimization Techniques
## 1. Object Pooling
```gdscript
# Instead of creating/destroying objects frequently
class_name ObjectPool
var pool: Array = []
var prefab: PackedScene
var pool_size: int = 20
func _init(scene: PackedScene, size: int):
prefab = scene
pool_size = size
_fill_pool()
func _fill_pool():
for i in range(pool_size):
var obj = prefab.instantiate()
obj.set_process(false)
obj.visible = false
pool.append(obj)
func get_object():
if pool.is_empty():
return prefab.instantiate()
var obj = pool.pop_back()
obj.set_process(true)
obj.visible = true
return obj
func return_object(obj):
obj.set_process(false)
obj.visible = false
pool.append(obj)
```
## 2. Level of Detail (LOD)
```gdscript
# Switch to simpler models/sprites when far away
@export var lod_distances: Array[float] = [50.0, 100.0, 200.0]
@onready var camera = get_viewport().get_camera_3d()
func _process(_delta):
var distance = global_position.distance_to(camera.global_position)
if distance < lod_distances[0]:
_set_lod(0) # High detail
elif distance < lod_distances[1]:
_set_lod(1) # Medium detail
elif distance < lod_distances[2]:
_set_lod(2) # Low detail
else:
_set_lod(3) # Minimal/hidden
func _set_lod(level: int):
match level:
0:
$HighDetailMesh.visible = true
$MedDetailMesh.visible = false
set_physics_process(true)
1:
$HighDetailMesh.visible = false
$MedDetailMesh.visible = true
set_physics_process(true)
2:
$MedDetailMesh.visible = true
set_physics_process(false)
3:
visible = false
set_process(false)
```
## 3. Spatial Partitioning
```gdscript
# Only process objects in active area
class_name ChunkManager
var active_chunks: Dictionary = {}
var chunk_size: float = 100.0
func get_chunk_key(pos: Vector2) -> Vector2i:
return Vector2i(
int(pos.x / chunk_size),
int(pos.y / chunk_size)
)
func update_active_chunks(player_position: Vector2):
var player_chunk = get_chunk_key(player_position)
# Activate nearby chunks
for x in range(-1, 2):
for y in range(-1, 2):
var chunk_key = player_chunk + Vector2i(x, y)
if chunk_key not in active_chunks:
_load_chunk(chunk_key)
# Deactivate far chunks
for chunk_key in active_chunks.keys():
if chunk_key.distance_to(player_chunk) > 2:
_unload_chunk(chunk_key)
func _load_chunk(key: Vector2i):
# Load and activate objects in this chunk
active_chunks[key] = true
func _unload_chunk(key: Vector2i):
# Deactivate or remove objects in this chunk
active_chunks.erase(key)
```
## 4. Efficient Collision Layers
```gdscript
# Set up collision layers properly
# Project Settings → Layer Names → 2D Physics
# Layer 1: Players
# Layer 2: Enemies
# Layer 3: Environment
# Layer 4: Projectiles
# Player only collides with enemies and environment
func _ready():
collision_layer = 1 # Player is on layer 1
collision_mask = 6 # Collides with layers 2 (enemies) and 3 (environment)
# Binary: 110 = 6 (layers 2 and 3)
```
## Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.