LobbiLobbi
Back to Guidance

Naming Conventions: Saving Your Pipeline from Chaos

Pipelines
March 14, 2026
9 min
Lobbi Support
GuidancePipelinesOrganizationNaming ConventionsAssetsBest Practices

The "FINAL_v3" Problem

Every single veteran game developer has stared in utter horror at a Perforce depot containing a folder with the following files: Sword.fbx, Sword_New.fbx, Sword_FINAL.fbx, Sword_FINAL_Real.fbx, and Sword_v2_FINAL_USE_THIS_ONE.fbx.

This is not a mildly amusing anecdote; it is a critical pipeline failure. When a technical animator writes a script to bulk-import 500 weapon models into Unreal Engine, a single incorrectly named file can shatter the entire automation process, costing hours of manual debugging.

The Golden Rule of Naming

The Golden Rule of pipeline management is that human beings are fundamentally terrible at remembering rules. Therefore, your naming convention must be mathematically rigid, universally documented, and ruthlessly enforced from Day One of production. You cannot retroactively fix naming conventions a year into development without breaking thousands of engine dependencies.

The Anatomy of a Perfect Asset Name

Wep Category
_
Sword Asset Base
_
Fire Variant
_
v04 Version

Result: Wep_Sword_Fire_v04.fbx

Establishing the Prefix System

Modern engines require strict categorization. Establish a mandatory 3-letter prefix system for every single asset type. Env_ for Environment props, Chr_ for Characters, Wep_ for Weapons, Tex_ for Textures, Sfx_ for Sound Effects. This guarantees that if a developer searches the repository simply for "Chr_", they will immediately isolate every character model in the game without scanning multiple nested folders.

CamelCase vs. Snake_Case

You must brutally ban spaces in filenames. Spaces break Python automation scripts and command-line rendering tools. Choose either CamelCase (e.g., RedDragonHelmet) or Snake_Case (e.g., Red_Dragon_Helmet) and aggressively document that choice on the studio's main Wiki page. Our data shows that Snake_Case is generally preferred by technical artists for its immediate readability.

Automated Validation Scripts

Do not rely on humans to verify names. Have your Technical Director write a simple Python script pre-hook for your version control software (e.g., Perforce or Git). If an artist attempts to commit a file named "dragon_final_FINAL.fbx", the script should forcefully reject the commit and display an error linking directly to the naming convention Wiki document.

More from Guidance

View all →

Explore other resources