This is still a proposal. It may be a good a idea to differentiate the public model name from our internal one. This’ll work similar to what we already do with objects, i.e. we’ll have a public name and our internal name.

The internal name will be used in the Dropbox folder, rendered files, etc. All internal files in general.

The main reason to do this is that we want to allow clients to rename their models, but it’s a lot of hassle for us to rename all resources related to a model, specially in the late stages of production.

So, in several screens of the platform the internal name will be shown to artists to keep them aware of both names.

If you notice, when the code name is significantly different from the public one, it’ll be highlighted in red.

Similarily, objects internal names will also be shown:

The automatic model categorizer will be affected by this update, as it’ll use the new internal name to associate the uploaded files with the right model.

Once this is in place, it’ll be applied to all newly created models. Existing Dropbox folder names won’t be renamed automatically.