That makes sense, but using it during boot shows only the _base mount. This is where my understanding of it is incorrect. It seems like mounts do not appear until added manually ā and ā only if the resources for the mount donāt exist. Mounts do not persist between sessions - but the mountās resources do.
Correct. It is for example used by those (few) developers that use the auto mount feature.
only if the resources for the mount donāt exist.
Mounting doesnāt involve ācheckingā any missing resources at all. The mounting simply adds the archive to the list of archives to use when the next loading of resources will happen.
Mounts do not persist between sessions - but the mountās resources do.
If the archive is not mounted, its resources cannot be loaded.
If they are, it suggests the resources are found in the default archive.
1 Like
Thank you for explaining it to me. 
I am starting to understand it better.
This says it allows you to ādesigned to simplify the management of Live Update resourcesā, but Iām unsure how to use it properly. If instead of having 50 collection proxies for 50 levels, Iām assuming this allows you to load/unload a collection into a single proxy.
In my project, Iām trying to set this up but since levels 2-50 arenāt collections ā they are files/paths in the project folderā , Iām unable to exclude them. The excluded files I need are not appearing the the graph during a build.
Iām unsure how this works.
Update:
Maybe the solution is the have the default collection include a collection that has all of the levels? I think that would work, but it defeats the purpose if swapping collections.