Split off unused assets to separate folder #16
Comments
|
In case this helps with sorting, I've compared the current repository to the latest release package:
|
{{ message }}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As discussed on Discord, the release packages currently undergo some manual stripping of unused assets. Those assets are planned for future use, so we don't want to remove them from the repository, though we would like an easy way to strip unused assets for the purpose of automated release packaging.
One possibility is to manually move unused assets to a separate folder. Perhaps we could add an
unusedAssetsfolder, where future assets can be stored. It probably makes sense to organize such assets into subfolders which mirror the structure of the root folder.When we are ready to use an asset, we can move it back into the normal folder structure. There is one sided safety there, in that an asset would need to be in the normal folder structure to be found by the game. Failure to move the asset should result in failures to load the data during development and testing. That could be made safer by doing eager loads of assets, so we don't run into the case of not finding a packaging bug because we never execute the code that needs to load the asset. The other side of the safety problem is we might potentially include assets that aren't actually used, and just not realize it. As sorting assets into an unused folder is a manual process, it's possible some assets will be missed, and will continue to be included in release packages without being used by the release.
Related issue:
data/assets to release packages OPHD#601The text was updated successfully, but these errors were encountered: