- Dashes can be used to signify a sort of hierarchy
- Variants are still separated by : but in a way that sort of merges
into the hierarchy defined by the dashes,
eg. `wardrobe:burned-shelf-book`
- Asset identifier mostly non-controversial; Shortened name is optional,
but try to use it. Asset identifiers can have underscores and numbers,
no problem. (coral_001)
- Collection prefixes should only be used for root collection.
(Put this right after the Asset Collection Hierarchy header!)
- Task layer names no longer have to be included in collection names.
- Expand the concept of "Asset Identifier" to be more like a
"Namespace Identifier", and mention that it should also be used for library IDs
that aren't part of an (Asset Pipeline) asset. (instead of the asset's
name, use the file's name, for example.)
- Add SH-, GN-, CM- prefix conventions for node groups.
- Small correction: Batch Rename Datablocks is not an addon.
- Small correction: `GEO-house-wooden_plank.023` had inconsistent names
- "Of" relationships should no longer be part of the base name.
Recommended hierarchy based naming using dashes.
- Variants are now a bit more complex, try to explain that properly.
- Pose library poses should also have the asset identifier.
- Animation versions now separated by dash instead of dot.
- Change camera rig prefix from CAM to CA.
- Only one prefix, still separated by dash.
- Make it explicit that if a name includes the full name of the asset,
using the mnemonic is not necessary.
- Add `TMP` name prefix suggestion
- Add more detailed but less wordy explanation about why unique ID names
are important.
A major overhaul of our in-blend naming conventions.
Goals:
- Every asset datablock must have a unique name to avoid Override issues
- Separators could be more consistent and meaningful
- No unnecessary strictness, eg. for Pose Library
