Since AtlasTexture inherits Texture2D the plugin considers it an editable resource. However, due to the way the dictionary associating AtlasTexture with other Texture assets functions, attempting to edit one will produce an error.
I don't think it's a good idea to allow AtlasTexture to be created from AtlasTexture due to the possibility of making the association dictionary unnecessarily bloated for an extremely unlikely scenario in normal gamedev. Instead what should happen is that the plugin should look up AtlasTexture's source texture and edit that, pre-selecting the AtlasTexture from the Filesystem.
Since AtlasTexture inherits Texture2D the plugin considers it an editable resource. However, due to the way the dictionary associating AtlasTexture with other Texture assets functions, attempting to edit one will produce an error.
I don't think it's a good idea to allow AtlasTexture to be created from AtlasTexture due to the possibility of making the association dictionary unnecessarily bloated for an extremely unlikely scenario in normal gamedev. Instead what should happen is that the plugin should look up AtlasTexture's source texture and edit that, pre-selecting the AtlasTexture from the Filesystem.