Godot resource ownership
Keeps shared artwork separate from each character’s changing data. It also handles abandoned level loads so old callbacks cannot replace the scene the player has already chosen.
godot-resources-loading
See how it helpsWhen is it useful?
Use when changing one actor unexpectedly changes others sharing an asset.
What does it help you do?
- Classifies immutable shared resources and mutable instance data.
- Chooses duplication deliberately and separates imported output from source assets.
- Rejects stale loading callbacks and exposes missing-resource recovery.
Try asking this
Two enemies share one material, but only the wounded enemy should flash red. Separate the changing state, then start loading a dungeon and return to the menu. Verify the cancelled load cannot spawn enemies or replace the menu later.
Detailed documentation
Read the skill’s original instructions, examples and checks in their authored language.
Show less
Godot — resources loading
Use when changing Godot Resources, imported assets, asynchronous loading or memory ownership.
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
Classify immutable shared Resources and per-instance mutable state. Check local-to-scene or duplication choices before editing shared data. Separate import output from source assets. Make loading failures visible and prevent stale completion callbacks from mounting a departed level.
Deliver
An ownership table and a bounded loading/transition change with a missing-asset recovery path. Keep the change in the existing project structure; separate actual observations from the proposed acceptance scenario below.
Failure to prevent
A cached Resource changed by one actor can alter every actor; duplicated assets can inflate memory.
Acceptance scenario
Load two actors sharing an asset, mutate one actor’s state, cancel a level load and revisit the level. 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