I use to include some kind of prototypation/placeholder content on every project I start.
Some projects will be just needed to answer some specific question / test and would be probably deleted soon so it’s not that great to migrate lot of content in a project that may never really start.
At the same time If I don’t have enough assets in a new project I cannot make fast and proper testing.
I generally build this content over time as soon as it is required and prefere to have it in a centralized location to make any new or updated content directly available to whatever other project in the workspace both serious and quick tests.
There is any feature that can help me achieve this workflow?
It have to work great with project packaging as in a workspace I may have many files that a specific project doesn’t use ( they will be more and more as project progress as assets are replaced with final ones).
It would be great if in a project I can cache a specific version of a file(es if a project does require an old version of an updated file) and engine look first for the cached versionwhile solving a reference in the shared package.
Plugins with embedded content is something that may unlock this kind of workflow even if not really intended for this?
However a project that saves or updates an asset embedded in a plugin may be an unwanted behaviour and don’t even know if it is possible at moment or will be possible in future.
Another issue with plugins is that they have to be placed in engine or specific project directory.Is it right?
Please suggest me some kind of viable workflow that may be similat to what I’m looking for.