Sub-categorizations in object ID

[dr-dirt]

I'm looking at the consistency of naming across the different types of scenery and I would propose a simpler methodology of placing objects into sub-categories after the type of scenery in the object's ID.

Currently it is:
nedesigns.[scenery_type].[category].[sub-category].[specifiers]

Where:
category falls into essentially what tab on object would fall into and;
sub-category contains a grouping within that (ie, texture-based categorization).

I propose we eliminate the broader category and include it in the naming of the sub-category if necessary.

As an example:
An object is currently: nedesigns.scenery_small.block.castle.quarter_square
However, this could be: nedesigns.scenery_small.castle_block.quarter_square

The reason being this matches the convention that would likely used in the case of walls, where most walls will have a redundant category (ie, plain walls) as this is already in the scenery type name ('scenery_wall'). For example, nedesigns.scenery_wall.wall.marble doesn't make sense but would be consistent in terms of level of organization with small scenery.

[spacek531]

Can you give examples of how this would affect trim object identifiers? I don't remember but I think the current designation system was intended only for small scenery. If it makes sense to not have the category designation from wall scenery then that's fine.

[dr-dirt]

Some examples would look like:
.art_deco_trim.quarter
.art_deco_trim.quarter_diagonal

Some others:
.fence_post.8_quarter_corner (for custom fence objects)
.wood_roof.quarter

as opposed to:
.trim.art_deco.quarter
.trim.fence_post.8_quarter_corner
etc.

Basically, for example, art deco trim is the subset of objects and the next field is specifiers/variations of that in terms of shape, colorability, height, etc.