OK. So here's a series of questions I really want to have answered for future use.
Firstly, what exactly does 'ref' mean in the Log Window? Is it how many copies of the file have been saved to RAM? Is it how many objects are using the file? Additionally, is the memory address the RAM memory address
Secondly, how does loading of assets such as sound and images actually work? If you do not load a file with LoadImage or LoadImageInThread, does it load automatically? If so, does RemoveTexture actually purge a loaded file from memory? I ask because purging large files from memory after they have been used for the last time is a reliable way to lower the amount of stress that is placed on ones computer. I ask because I load all of my main images and sounds during a loading phase of the package, and I am experimenting with a way to purge those files until they are needed again. More specifically, I plan to LoadImage in @Loading at the start of the stage for images that have already been loaded (in case the stage is replayed), and then RemoveTexture in @Finalize, so that the files are removed. Doing this, however, leaves references to the file, so I cannot be sure that it has been purged from Danmakufu's memory.
Finally, a question about archive files. I have noticed that archive files do not work based on a directory structure in that if you archive all the contents of a folder called 'img' and leave the archive in the folder img, Danmakufu cannot find it, but if placed outside of the directory 'img', Danmakufu will be able to read the files inside the archive. The path after loading still shows that the folder 'img' is in the file path despite the images' location on the computer not being in img but rather in an archive located one directory above img. How does this affect multiple-archive systems where some filenames are the same, and how does Danmakufu's archive system actually WORK?
Thank you.