You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Assetlists are already usable for ignoring assets inside project definitions as well as loading all assets from an assetlist.
This is particularly useful when you want to build an IPak with all images from a built zone for example.
To enable this workflow Linker should automatically generate assetlists after successfully linking.
These assetlists should be placed in an appropriate source directory in a "assetlist" subfolder.
Would probably also good if creating assetlists could be turned off via cli args.
It should be enabled by default though for now.
The text was updated successfully, but these errors were encountered:
+1 just for CI purposes, i'd love to upload to my artifacts a file like an asset list that confirms the name and type of assets loaded into the built fastfile
Assetlists are already usable for ignoring assets inside project definitions as well as loading all assets from an assetlist.
This is particularly useful when you want to build an IPak with all images from a built zone for example.
To enable this workflow Linker should automatically generate assetlists after successfully linking.
These assetlists should be placed in an appropriate source directory in a "assetlist" subfolder.
Would probably also good if creating assetlists could be turned off via cli args.
It should be enabled by default though for now.
The text was updated successfully, but these errors were encountered: