You should look into addressables. You could likely make this work with minimal recoding using addressables.
Hm, I looked into that and what addressables does is forces you to duplicate the entire Resources directory to a Resources_moved folder. I'm guessing at that point the textures are no longer considered resources. Which means PaperDoll wouldn't be able to access them any longer. I'm guessing what you're recommending is rewriting paperdoll to use addressables instead.
I've set up a fresh project and I'll lean into attempting that. If I get it working I'll send the code your way. Do you have an email I should shoot it over to? Consider any of my changes MIT/X so you can integrate and resell it without restrictions.
ĪWell, what you might have is another class, such as your character class unpack the addressable and then pass it to the paper doll using the set texture method. Or build a script whose sole job it is to unpack these and send it to paper doll then just attach that script to everything that needs it. Email address is bluemanafox@gmail.com, would love to see your final solution to the problem!
P.S. not sure if we're talking about the same thing or not. Addressables doesn't use a resource folder at all, instead it prevents an asset from being loaded until it's needed whereas resources load everything and keeps it in memory. It may not work, sounds like there's a potential flaw with the dedicated server design. Depending, it may be worth it to restructure it if that's possible.
Got it working! :) I made a class called PaperDollAddressable. It works just like PaperDoll except you pass in a string name of the addressable you want to use instead of a resource texture. You'll be able to include it in your product without breaking the old PaperDoll and devs can just pick which one they want to use based on their usecase. I'll clean it up and email it over.
Regarding what I meant before about the Resource folder, when you try to convert a Resource texture to an addressable it will demand that you duplicate the folder as Resource_moved because Addressables cannot be in the Resource.
And, regarding my usecase I am trying to use FishNet + Edgegap for hosting, and their containers are 1 hour limit and 250MB memory constrained for evaluation and 2GB limited for pro. I hit the 250MB memory limit of the container very quickly because I own all the Mana Seed packs and had them in the Resources. And, when you build, Unity marks Resources as required and forces them into the dedicated server builds. I kept adding content and testing my network code which was working great up until I added too much content and the dedicated server stopped working because of the constraint. So, I want to move over to addressables to solve it.