The same texture is often applied to multiple sides of a Part. This new object would have the usual Texture properties and a boolean for each of the faces of its parent Part.
What’s wrong with using 6 textures? I’m not sure if there would be any significant performance gain from this but maybe I’m wrong.
Explorer spam
If that is all, I would rather see an toggle for Studio that will just say 6 Textures instead of 6x an Texture object.
Deprecate Face, add the property Surface. Add a new enum Surface with the options (Front, Back, Left, Right, Top, Bottom, All, None). Seems like a much better solution as it works for more than just textures.
However as before mentioned, it doesn’t seem to have a good use-case.
Or one could even use something like the faces object.
That said, I’m fine with putting 6 textures on a part. It would make things nicer if we get more properties for a texture (e.g., offset properties) to have them all split apart.