tinqs/animation
5
0
Fork 0
Code Pull Requests Actions Packages Projects Releases Wiki Activity Issues

docs(naming): dance codes are ceremony-based (<ceremony><NN>)

Browse Source 
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Jeremy
2026-07-16 14:28:35 -07:00
parent b918d8670f
commit 6a1290b1d1
2 changed files with 12 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/dances/REGISTRY.md
+7 -4
View File
@@ -11,10 +11,13 @@ suffix: `nd08_pp` / `ND08PP`. The `nd` prefix means "not yet adopted — subject
rename or archive". Never name a new dance after its content (a take called
"firedance1" turned out to be dance1's choreography — content-guessed names lie).
**Stage 2 — adopted (chosen for a specific dance).** When Jeremy picks a take for a
specific in-game dance, it is renamed to its **dance code**: `<style><NN>` — lowercase
pack (`haka01`, `hula02`, `fire01`), PascalCase clip (`Haka01`), variants
`haka01_pp` / `Haka01PP`. Rename with:
**Stage 2 — adopted (chosen for a specific dance ceremony).** Dance codes are named
after the **ceremony the dance belongs to in the game**: `<ceremony><NN>` — the
ceremony slug in lowercase ascii (no spaces/diacritics: `powhiri`, `kapahaka`, `wero`,
`hulakahiko`, `hulaauana`, `sivaafi`, …), a two-digit index for multiple dances within
the same ceremony, PascalCase clip. Examples: pack `powhiri01` / clip `Powhiri01`,
variants `powhiri01_pp` / `Powhiri01PP`. A take is only renamed once Jeremy says which
ceremony it corresponds to. Rename with:
```bash
/Applications/Blender.app/Contents/MacOS/Blender --background --python tools/rename_clip.py -- \