Godot profiling and exports
Finds why the delivered game stutters or loads differently from the editor. It separates scripting, physics, graphics and loading costs before choosing a focused improvement.
godot-profiling-export
See how it helpsWhen is it useful?
Use when editor performance differs from the game players actually run.
What does it help you do?
- Separates script, physics, rendering and loading costs.
- Checks export templates, project filters and included resources.
- Compares the same route before and after scoped changes.
Try asking this
Our exported action game pauses when entering the forest. Record the same route before and after a targeted fix, inspect resource loading and shader costs, and check the export contains every required asset. Report measured frame times rather than an estimated speedup.
Detailed documentation
Read the skill’s original instructions, examples and checks in their authored language.
Show less
Godot — profiling export
Use when diagnosing Godot stalls, render cost, memory growth or platform export failures.
Version and project gate
Inspect project.godot, config/features, .tscn and .tres files, export_presets.cfg without credentials, input actions, autoloads, renderer, physics backend and installed Godot executable. Distinguish Godot 3 from 4 before selecting APIs. Never turn a task into an engine upgrade without the user’s intent. Read the version-matching official reference when an API decision depends on it.
Work
Capture the exact scene, device, renderer and export target. Separate script, physics, rendering and loading cost before changing code. Compare a representative exported build with the editor; record warm-up and repeated transitions. Check export templates and project filters for missing resources.
Deliver
A before/after evidence record with the measured bottleneck, scoped fix and exact export limitations. Keep the change in the existing project structure; separate actual observations from the proposed acceptance scenario below.
Failure to prevent
Editor FPS alone does not establish player performance; removing debug output is not proof of fixing GPU cost.
Acceptance scenario
Run the same player route before and after the change and revisit the level repeatedly; report unavailable hardware honestly. Follow the project’s execution and verification permissions. If execution or a target device is unavailable, provide the reproduction steps and name the remaining uncertainty; do not mark it passed.
Scope and sources
This skill belongs to Rune. Agent selection is restricted by Orqestria’s assigned-agent policy, including forced skill selection; instruction text alone is not an access control. These are original task workflows researched from official documentation, not a copied or endorsed vendor skill.
Included files 1
SKILL.md