Skip to content

game-asset-slot-handoff-unity

Game Asset Slot Handoff — Unity mechanics

Section titled “Game Asset Slot Handoff — Unity mechanics”

Extends rules/placeholder-first-handoff.md (theonekit-designer), Unity-only: parent = Asset Slot contract, this file = Unity mechanism.

Load-bearing fact — GUID identity, not path identity

Section titled “Load-bearing fact — GUID identity, not path identity”

Unity keys an asset by the GUID in its .meta, not its path — prefabs/scenes/SOs/Addressables all store that GUID. Overwrite in place → .meta untouched → refs survive. Add-then-delete → new GUID → refs silently resolve to None. So: “overwrite Item_Sword_01.png in place,” never “put your sprite in Icons/.”

An asset with no slot kind (a model, animation, rig or image-prop today) gets an append-only amendment to the slot contract and a re-lock, in the same lane as its consumer. It is never left unwired for lack of a kind. A graded join (wired-not-just-present.md) records its grade. The GUID and .meta rules below are unchanged.

  1. Overwrite exactly the slot-table files — same path/filename/extension.
  2. Never rename, add, or touch a .meta.
  3. git diff --stat before commit: only slot-table assets.
  4. Commit, push.

Mechanics (recipes, .meta conflicts, Addressables, checklist, gaps): docs/game-asset-slot-handoff-unity.md.

rules/placeholder-first-handoff.md (theonekit-designer, parent) · docs/game-asset-slot-handoff-unity.md