As discussed in this topic, it is not uncommon to encounter map loading issues when adding custom maps
These problems are quite difficult to isolate in order to correct them easily.
To make corrections easier, it might be interesting to:
-
As suggested by gottfriedleibniz: hooking the two archetype registration functions and checking for duplicates (or the unlikely hash collision)? Generating warning messages similar to geometry validation.
-
And/or being able to view in a table format within the developer tools all the archetypes in memory (and possibly the name of the related ytyp/ymap, and a timestamp)