Hi y'all! We want to migrate from AssetBundles to Addressables and are trying to get the same behavior. We basically have a scene plugin system that historically has used AssetBundles to do "blind" loading of items based on one of our other processes placing items in a dir on the system. In other words, MainProject is what we ship, and ExportTemplateProject is used to export a scene, distribute it in the community, and other users can dynamically load it, etc. So the scenario is a little similar to the remote sever, except that this is just a local dir that bundles are being placed into. I've been researching and experimenting for days now wrapping my head around figuring out the Addressables equivalent. So far every example I've seen so far is where MainProject has some sort of reference or knowledge of the external scene. My feedback for the Addressables dev team is: way to go on making a badass and capable systems! But perhaps can y'all pretty please add to Addressables-Sample? Basically, enhance the "Scene Loading" example that's already there -- except that, say, the "balls" and "boxes" scene would be moved and would reside in a totally separate Unity sister project. It would this have all the settings and code that demonstrates loading an addressable from a file system pathname, etc. Hopefully this makes sense, and y'all get what a huge value add this would be to the pile of people like us who are in this situation! Or perhaps there a link or a sample project somewhere that contains two separate projects and where the exported addressable bundle is moved to an arbitrary local dir at runtime, and MainProject loads it? I appreciate that Unity offers downloading services from a http URL, but we want the use case where it's all local files, etc. Thanks!