(2021-03-16, 19:35)Orion Pobursky Wrote: That's not the way it's supposed to work. If stud.dat is embedded in the mpd or located in the same directory as the model file then it should replace all instances of stud.dat for the entire model. This allows, say, a part author to test out a fix on a bunch of different parts simultaneously or a model author to include a custom version of some commonly file (e.g. a stud with a custom logo).You could do that by adding your custom/development library paths in front of the official ones.
The main thing I'm disliking about the global scope thing is the fact an embeded file which happens to have the same name as some official part would break all dependencies.
The 'context' method will only affect its local scope so there will never be problems with duplicate names, it's comparable with local variables in a programming language.