I understand, but then one could have the original file name, plus an additional suffix that works as a unique identifier.
Let me take a real example
I have the XForgPlants Europe 1
library. From there, I insert the "Austrian Pine 1
XML data from the library:
<name lang="english">Austrian Pine 1</name>
<name lang="latin">Pinus nigra 1</name>
<family>Tree, evergreen conifer</family>
<description>Also known as European Black Pine, The Austrian Black Pine is often used as pioneer species on wasted areas, because it tolerates arid soils. Although not a mountain tree, it is cold-tolerant. It needs a lot of vertical light, but can stand lateral density, so woods of Black Pine are often dense with trunks. It is called ?black? because of the dark needles.</description>
The mesh name in the original file is EU08a01
When I import the tree from the Forest Pack Library, it names it "Austrian Pine 1" which is correct.
However, I don't know what .MAX file it is if I don't dig in the XML file.
And last, but not least, the name of the mesh is _forest_library_IIZWI2I
and that was the reason of this post. This name does not make any sense. I cannot find a logical link between this name and the XML entry from the library.
In short, my suggestion is that it keeps the original name, EU08a01 and adds whatever it needs, prefixes and suffixes. For example: _forest_lib_EU08a01_IIZWI2