Yeah, that’s a key takeaway. We started standardizing naming using CHAR_ , ENV_ , and UI_ prefixes for everything, plus version tags like _v01 , _final , etc. But the real win came from embedding meta-tags right into asset descriptions—stuff like animation state notes or collision flags.
Problem is, most of that gets lost in the shuffle unless you’ve got a checklist baked into the pipeline. We tried spreadsheets but they age badly. Wondering if plugins can surface that kind of info inside the engine? Would be huge for avoiding logic drift over time.
2 Likes