Unity 2019.2 added the very useful Client.Embed method. Unfortunately I am working with some people who are still stuck on earlier versions of Unity, but still want to use the embed functionality. I figured it would be easy enough to write a fallback, but I am running into some very strange behavior that I would like some clarity on. There seems to be some sort of mechanism in place to make packages appear to the filesystem as though they are in the Packages folder, even though they are located inside of Library/PackageCache. If I log the results of Directory.GetDirectories("<pathtoproject>/Packages") I see nothing. But if I do Directory.GetFiles("<pathtoproject>/Packages/packagename") I see all of the files that are located in the package, but furthermore, all of the full paths to those files show they are indeed located at <pathtoproject>/Library/PackageCache/packagename/ instead! I am unfamiliar with whatever mechanism is in place that can cause this to happen, but the reason I ran into it is because I am simply trying to move the package contents from the PackageCache folder into the Packages folder, but due to this strange mechanism, the operation fails because it considers it already at the destination location! Is there any way I can get around this behavior, and create an Embed fallback that can function in the same or similar way?