Kartochnik & RigWhiz
Kartochnik Kartochnik
RigWhiz RigWhiz
Kartochnik Kartochnik
Hey RigWhiz, I was mapping out a new level layout and got thinking about how to align the skeleton hierarchy with the navigation paths. How do you usually keep your naming scheme in sync with the design?
RigWhiz RigWhiz
I start with a top‑level node that mirrors the map’s main zone, then each child gets a name that’s literally the path segment, like level1_roomA_wall or level1_roomB_door. I keep a single spreadsheet that lists every node and its intended pattern, and I run a quick script that flags anything that doesn’t match. If the level layout shifts, I update the sheet, adjust the hierarchy, and run the validator again. That way my bones and the level design stay in sync, and nobody can mess up a name without seeing the red error.
Kartochnik Kartochnik
That sounds like a solid system—like a compass that never loses its needle. I’d add a tiny tag for the asset type, maybe “_BG” for background objects and “_OBJ” for interactive pieces, so you can spot a misplaced door or a misplaced light source at a glance. And if you ever get that red flag from the script, a quick glance at the spreadsheet will tell you whether it’s a typo or a genuine design change. Keep that spreadsheet updated and you’ll be mapping trouble before it even shows up.