Duplicated item suffix 01,02,03.. instead of .001,.002,.003..?
Most of the systems in game industry work with 01,02,03 for example the collisions in Unreal or naming conventions most of the projects I worked on is usually like:
doorhandle_01
doorhandle_02
etc..
Would be nice if there was option in blender to change the naming pattern for duplicated objects to follow the 01,02,03 pattern 🤔
9 Comments
Would be nice to have optional naming conventions settings +1
Yes! do you know a software that does have that functionality? For a reference
OBS studio has a similar feature where you can create a file name suffix for recording.
Create a custom suffix in preferences, to match the user preferences will be nice, so user can decide if they want _01 - 01 (01) or anything else.
You can already do this in the Batch Renamer (Ctrl-F2) using regexs: Find: (.*)\.0*(\d+) (click star) Replace: \1_\2 (click star)
or as a 4-line Python script (weirdly the web filter won't let me post the Python!)
This could cause problems for scripts and AddOns where pruning the '.NNN' pattern is a standard way of detecting and cleaning up duplicates.
The '.NNN' convention for numbering duplicates is widely used across Blender, not just for objects and collections, but even for things like shape keys, vertex group and action names. Changing this could break a lot of things.
I think a better idea would be to have an AddOn for the situation OP describes (run on demand, or as a substitute for shift-D) . That's an easy addon to write which doesn't require changing the Blender exe source.
A script that prunes duplicates purely based on the .NNN suffix is pretty sketchy already.
Because you could have Cube.001 and Cube.002, where Cube.001 is just a standard cube, but Cube.002 has had a lot of custom modeling/sculpting work done to it and is no longer just a cube ... but is still named Cube.002 ... and such a simple pruner would then delete Cube.002 because it's a "duplicate" of Cube.001. Not good.
Any duplicates pruner worth its salt would look at the data blocks of each object to check if they're actually identical before pruning. And if you're checking for identical data blocks, then you don't need to worry about naming conventions.
> A script that prunes duplicates purely based on the .NNN suffix is pretty sketchy already.
Well, yes! but I think we're stuck with it... Two ways to use the Blender Python API: (1) Direct manipulation, which is great, but which is missing higher level function. (2) For that you use the ops operators, which are very bad at signaling what changes it has made. Often all you can do is comb through the data looking for something with a prefix added. Join shapekeys is an example of that. In the case of that there is no datablock, and even if there is, there might be other objects using it - that you don't want to operate on.
BTW I'm not a fan of the numbering system. I spend too much time renumbering things as it is. Just pointing out the wider implications of a seemingly minor change like this.
I agree it's cleaner with that suffix, and a change would be nice for this.
ps: Just in case, you can actually change the suffix if you have a lot of objects with the "batch rename" option to the way you said it