docs(naming): dance codes are ceremony-based (<ceremony><NN>)
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
@@ -36,9 +36,11 @@ Two-stage names. **New dances get a provisional id, never a content name**: at
|
|||||||
conversion, assign the next free `nd##` from the registry — pack `nd08`, clip `ND08`,
|
conversion, assign the next free `nd##` from the registry — pack `nd08`, clip `ND08`,
|
||||||
JSON `nd08.json`, variants `nd08_pp`/`ND08PP` — regardless of what the PC export was
|
JSON `nd08.json`, variants `nd08_pp`/`ND08PP` — regardless of what the PC export was
|
||||||
called (a take named "firedance1" turned out to be dance1's choreography). Only when
|
called (a take named "firedance1" turned out to be dance1's choreography). Only when
|
||||||
Jeremy **adopts** a take for a specific in-game dance is it renamed to its dance code:
|
Jeremy **adopts** a take for a specific in-game dance is it renamed to its dance code —
|
||||||
`<style><NN>` lowercase pack (`haka01`), PascalCase clip (`Haka01`) — via
|
codes are named after the **dance ceremony** the take corresponds to: `<ceremony><NN>`
|
||||||
`tools/rename_clip.py` + JSON rename + registry update. Rejected takes are archived
|
lowercase-ascii pack (`powhiri01`, `hulakahiko01`, `sivaafi01`), PascalCase clip
|
||||||
|
(`Powhiri01`) — via `tools/rename_clip.py` + JSON rename + registry update. Never
|
||||||
|
guess the ceremony; Jeremy assigns it. Rejected takes are archived
|
||||||
(`archive/` here; `archive/dances/` in ariki-game, which is `.gdignore`d), never deleted.
|
(`archive/` here; `archive/dances/` in ariki-game, which is `.gdignore`d), never deleted.
|
||||||
Numbers are never reused. Always update the registry row when converting/adopting/archiving.
|
Numbers are never reused. Always update the registry row when converting/adopting/archiving.
|
||||||
|
|
||||||
|
|||||||
@@ -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
|
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).
|
"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
|
**Stage 2 — adopted (chosen for a specific dance ceremony).** Dance codes are named
|
||||||
specific in-game dance, it is renamed to its **dance code**: `<style><NN>` — lowercase
|
after the **ceremony the dance belongs to in the game**: `<ceremony><NN>` — the
|
||||||
pack (`haka01`, `hula02`, `fire01`), PascalCase clip (`Haka01`), variants
|
ceremony slug in lowercase ascii (no spaces/diacritics: `powhiri`, `kapahaka`, `wero`,
|
||||||
`haka01_pp` / `Haka01PP`. Rename with:
|
`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
|
```bash
|
||||||
/Applications/Blender.app/Contents/MacOS/Blender --background --python tools/rename_clip.py -- \
|
/Applications/Blender.app/Contents/MacOS/Blender --background --python tools/rename_clip.py -- \
|
||||||
|
|||||||
Reference in New Issue
Block a user